-
Notifications
You must be signed in to change notification settings - Fork 985
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
Router clean up #21235
Router clean up #21235
Conversation
Jenkins BuildsClick to see older builds (12)
|
@alwx I am working on a PR that has api change https://github.com/status-im/status-go/pull/5564/files basically removed
and added I wanted to check if the removed params are being used in the mobile client already? cause if not I'll merge my PR to Sales PR directly. fyi @saledjenic |
@alwx for testing this branch could you make it to point to statusgo commit |
@alwx what about Khushboo's question? Do you use those properties or not? If not we can merge here changes in the same go. |
@saledjenic will do in a sec |
@churik please let us know when is the right time to merge statusgo PR? |
when we'll test it, I'll ping you @saledjenic |
hi @alwx thank you for PR. Take a look at the found issue. This issue happen consistently, but unfortunately there are no exact steps to reproduce it. Hopefully, the logs will help ISSUE 1: [Android] 'Undefined not a function' error is constantly shown after attempt to build the routeSteps:
Actual result:'Undefined not a function' error is constantly shown wallet_new_route.mp4Expected result:no errors are shown Devices:
Logs |
PR_ISSUE 2: Endless 'edit' button is shownSteps:
Actual Result:The "Edit" button is displayed repeatedly editbutton.mp4Expected result:The "Edit" button should be displayed only once OS:IOS, Android Devices:
Logs |
The edit button issue has been logged here already: #21043 I don't think it should be a scope of this PR. |
@alwx Can you check the logs and confirm or deny that this issue is because of the changes you made ? |
@shivekkhurana Yes, the first issue and the current one seem similar, but this one appears to be easier to reproduce. Additionally, the endless button keeps appearing even without tapping the 'try again' button, so it might have a different cause. |
Here are some additional steps to reproduce this issue, which does not happen in the Develop. Steps:
routes.mp4 |
PR_ISSUE 3: Wrong UI is shown after changing the token on the routes generation pageSteps:
Actual result:The previous route is still shown asset_route.mp4Expected result:The previous route is not shown when asset is changed OS:IOS, Android Devices:
|
PR_ISSUE 4: The Confirmation Keyboard Auto-Closes After Entering the PasswordSteps:
Actual Result:The confirmation keyboard constantly auto-closes, preventing the user from entering the password properly. Pixel 7a, Android 13 androidkeybaord.mp4iPhone 11 Pro Max, IOS 17 ioskeyboard.mp4Expected Result:The keyboard should remain open, allowing the user to enter the password without interruptions Logs: |
PR_ISSUE 5: "eq() not a number: <0.01" Error shown after transaction confirmationSteps:
Actual result:The user is redirected to the activity page, where the error message "eq() not a number: <0.01" is displayed. Expected result:The transaction should be confirmed without showing any error messages OS:IOS, Android Devices:
Logs |
@VolodLytvynenko @alwx I'm wondering if all those issues come from the updated statusgo or they were in the mobile app even before statusgo changes? |
Regarding additional steps posted in #21235 (comment), The routes are not supposed to be fetched if the user enters 0 or 0.000000. It's fixed here: #21209 (regression from #21136)
This issue is fixed here: #21201 |
@saledjenic I don't think this issues have to do something with the It's hard for me to imagine how |
@churik @VolodLytvynenko @alwx can we merge then the statusgo changes, cause we've been waiting for them 3 weeks already? Then you can merge this PR that handles endpoint names changes for the mobile app, and you can address all those above-mentioned issues (since they were here even before statusgo changes) through other PRs and don't block the desktop app by waiting for them to be fixed in this PR? |
Hey @saledjenic, I need some additional time to finish testing. Just 2-3 more hours |
PR_ISSUE 7: "Not enough native balance, token ETH, chain id " Toast Shown When There Is Insufficient ETH to Cover the FeeSteps:
Actual Result:A toast message is displayed: "Not enough native balance, token ETH, chain id ." Expected Result:The toast message is not shown Devices:
|
@saledjenic Thank you for your work and patience. I've finished testing. If issue 6 isn't Status Go-related, then the status go PR can be merged. I agree with @alwx that the other issues don't seem to be related to status go |
@alwx
I understand that it will be not working without new router calls but we should decide how to deal with issues before merging the PR. |
@churik my mistake, sorry — I somehow read the comment from @VolodLytvynenko above as an invitation to merge this one |
status-im/status-go@81cfce7...81cfce7 This reverts commit 72a02df.
status-im/status-go@81cfce7...81cfce7 This reverts commit 72a02df.
Works together with status-im/status-go#5778
Summary
Updates router calls to work with changes made in status-im/status-go#5778