docs: add Base Account provider capabilities troubleshooting#1571
Open
tung39838 wants to merge 1 commit into
Open
docs: add Base Account provider capabilities troubleshooting#1571tung39838 wants to merge 1 commit into
tung39838 wants to merge 1 commit into
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Many integration issues are not caused by incorrect Base Account usage, but by:
Wallets that do not implement the required methods.
Missing capability detection before execution.
Incorrect provider initialization.
Unsupported RPC method assumptions.
A dedicated troubleshooting page reduces repetitive support questions and improves developer onboarding.
This aligns with the project's emphasis on helping developers reach the "happy path" quickly while still documenting alternative paths.
Notes to reviewers
No new top-level documentation sections are introduced.
The page follows the existing troubleshooting pattern.
Examples use capability detection rather than wallet-specific behavior.
The content is intentionally focused on the most common provider capability failures to avoid overlap with the Reference section.