Repository navigation
Android - Settings - Blank page is displayed after tapping the profile icon for a newly created account #10100
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
- Open the test app
- In the email field, enter a Gmail email address for a new account and Continue
- Navigate to the email inbox of the account and open the validation email
- Tap the validation link and set a password that follows the password requirements
- Tap the profile icon at the right top
Expected Result:
The setting page is displayed after tapping the profile icon for the newly created account
Actual Result:
The blank page is displayed after tapping the profile icon for the newly created account
Workaround:
Unknown
Platform:
Where is this issue occurring?
- Android
Version Number: 1.1.86-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5662889_Screen-20220726-040210.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Activity
OSBotify commentedon Jul 26, 2022
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:marcaaron commentedon Jul 26, 2022
FWIW wasn't able to reproduce this on a hardware device Galaxy S8 running latest beta version of the app.
luacmartins commentedon Jul 26, 2022
I couldn't repro this on the simulator. @kavimuru can you please test this again?
kavimuru commentedon Jul 26, 2022
@luacmartins We will retest and confirm.
mvtglobally commentedon Jul 27, 2022
@luacmartins Issue is still repro on the original build, we will recheck once Android build is updated and available
Screen-20220726-215458.mp4
luacmartins commentedon Jul 27, 2022
It seems like we can't reproduce this internally. I'll remove it from the blocker list and keep it open to investigate further.
9 remaining items
neil-marcellini commentedon Aug 12, 2022
@luacmartins I'm going to drop these Android issues to you because I'm really busy currently.
Julesssss commentedon Aug 16, 2022
I built to a physical device today to try to help debug the issue but I'm unable to reproduce currently. While these logs are useful, I think the Android logs might help reveal the true error.
If anyone is able to reproduce, could they use Android Studio's Logcat window to get the native logs which should show the native stack trace.
Julesssss commentedon Aug 17, 2022
I think this should be kept as a deploy blocker actually. While I haven't been able to reproduce it locally, I've been seeing this on the staging build for over a week now.
luacmartins commentedon Aug 17, 2022
I have a feeling that this is already on prod, since we have had deploys since.
luacmartins commentedon Aug 22, 2022
@kavimuru can we still reproduce this? I think this has been fixed here.
kavimuru commentedon Aug 22, 2022
@luacmartins Checking with the team.
kavimuru commentedon Aug 22, 2022
Issue is not reproduced.
screen-20220822-162055.mov
luacmartins commentedon Aug 22, 2022
Thanks for confirming. Similar to the other android specific issues, I think we solved it in https://github.com/Expensify/Web-Expensify/pull/34497. Closing this issue.