-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile - Unified account - Bug related to Connect dApp #1839
Comments
Still getting the error when retest ConnectDApp.mp4 |
Version test: SubWallet v1.1.84(440)b-v11
Reproduce the step:
Actual:
Click_Cancel_1.mp4Click_Cancel_2.mp4
Click_Connect.mp4
Frozen.mp4Expect: Navigate to the dApp screen and displays the account being connected |
This bug is currently still reproducing on the Extension. It needs to be resolved on the extension first, this bug should be created as a separate issue and the current issue should be closed. @ThaoNguyen998 @giangtth17 |
Device test:
Validation passed:
IOS_correctStatus.movandroid_correctStatus.mp4
IOS_CorrectListAccount.movAndroid_CorrectListAccount.mp4
WalletConnect
|
Describe the task
Show incorrect status when connected dapp
Actual: Show incorrect status connect
ScreenRecording_11-19-2024.16-25-31_1.MP4
Expect: Display correct status
Show incorrect list account on popup connect account
Hide address on list account connect on dApp details
Actual: Show address
Expect: Hide address
Show incorrect number account connected => Related to issue: Mobile - Unified account - Bug related to Connect & Manage dApp #1857
Actual :
Expect : Show correct number
Re-check padding
WalletConnect
Improve UI on Select account modal
Actual : Show duplicate unified account ( substrate and ton type)
Expect :Show account name
Improve UI on walletconnect details screen
Actual : Show duplicate unified account ( substrate and ton type)
Expect : Show account name
Update content 's' for some screen
Error show TON address when connect Ethereum and Polkadot network
Actual
Expect : Show correct address
The text was updated successfully, but these errors were encountered: