metamask-mobile
metamask-mobile copied to clipboard
When attempting to Swap bluetooth is said to be off, when it's actually on
Describe the bug A clear and concise description of what the bug is When attempting to Swap with a Ledger account, I'm told that the bluetooth on my phone is off, when it's actually on Screenshots If applicable, add screenshots or links to help explain your problem
https://user-images.githubusercontent.com/7900773/178520872-1d1069a7-5b57-447d-9af4-d40d8492398c.MP4
To Reproduce Steps to reproduce the behavior
- Go to 'Swaps with your Ledger account'
- Click on 'Swipe to Swap'
Expected behavior A clear and concise description of what you expected to happen If bluetooth Smartphone (please complete the following information): Device: [e.g. iPhone6] iPhone 13 pro OS: [e.g. iOS8.1] iOS 15.5 App Version [e.g. 1.0.0] - find version number in app from Settings > About MetaMask 5.3.1 Ledger version 2.0.2
to be added after bug submission by internal support / PM Severity
- How critical is the impact of this bug on a user?
- Add stats if available on % of customers impacted
- Is this visible to all users?
- Is this tech debt?
Okay I just tried this again and didn't encounter the above problem. https://user-images.githubusercontent.com/7900773/181001773-797ff5b9-f496-419a-8839-a372971dfcb0.MP4
Perhaps this just happens on first install? Due to the importance of Swaps I'd like to keep this issue open for now. At least until @plasmacorral has done his official QA.
I just tried this again, with bluetooth off for MetaMask, and I saw this:
https://user-images.githubusercontent.com/7900773/181023262-fe037008-0264-486b-b47a-0be2e1c31614.MP4
https://user-images.githubusercontent.com/7900773/181023280-66e558e3-2b75-4eb4-835b-7ec6d34e6b35.MP4
The user should be sent to MetaMask iOS settings if bluetooth is disabled specifically for MetaMask. To global settings if the phone's bluetooth settings is turned off.
A check by either @zoltanarvai or @gummygod would be good here. There seems to be multiple minor problems with the bluetooth connectivity here that could be ironed out. cc. @rickledge
The message here has been fixed. Sending the user to the app settings is under investigation.
The original error I could not reproduce
Did not encounter this in build 952 with swaps of native tokens