MetaMask / MetaMask/metamask-mobile
After Connection establishement in metamask, returned to dapp manually in IPHONE failed to update connected status.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
After connected when manually returned to the dapp, the status not changed still showing the wallet connect page with retry option.
I tried using the watchNetwork and watchAccount functions, nothing triggered for me. In android its working fine.
### Scenario
_No response_
### Design
_No response_
### Technical Details
const unwatch = watchAccount((acco) => {
console.log('acc',acco);
this.isWalletConnected = acco.isConnected;
if (acco.isConnected) {
this.getAsset(acco.address);
} else {
this.asset = null;
}
})
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [X] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified in the issue. Reproduce the connection flow on an iPhone, then inspect the watchAccount and watchNetwork integration; done means the dapp shows the connected status after returning manually from MetaMask, while Android behavior remains working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100