Closed kavimuru closed 2 years ago
:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash
deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
FWIW wasn't able to reproduce this on a hardware device Galaxy S8 running latest beta version of the app.
I couldn't repro this on the simulator. @kavimuru can you please test this again?
@luacmartins We will retest and confirm.
@luacmartins Issue is still repro on the original build, we will recheck once Android build is updated and available
It seems like we can't reproduce this internally. I'll remove it from the blocker list and keep it open to investigate further.
@kavimuru can we add this to the KI tests?
I'm now able to reproduce this internally on dev for both the staging and main branches. I'll work on this one too since it seems very much related to https://github.com/Expensify/App/issues/10099
Action performed:
../script/clitools.sh generator:account
Note, I'm also able to reproduce with an \@expensifail domain.
I did a lot of debugging on this today and my conclusion is that for some reason the OpenApp
network request is failing on Android. I can see other requests succeeding, but not this one. Since it works fine on iOS, I'm guessing something about the Android http client doesn't like the request we are sending.
I'm also a bit suspicious of the json_decode
line here. I'll look into it more later.
Thanks for looking into this @neil-marcellini! It's weird that the call is failing on android, I'll try to join this investigation tomorrow!
@luacmartins I'm going to drop these Android issues to you because I'm really busy currently.
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.
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.
I have a feeling that this is already on prod, since we have had deploys since.
@kavimuru can we still reproduce this? I think this has been fixed here.
@luacmartins Checking with the team.
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.
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:
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?
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:
https://user-images.githubusercontent.com/43996225/180902822-ba03eae1-965c-449e-8d39-2a31ccece9b1.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub