-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Fabric] iOS - Login - App crashed when try to login. #14089
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
NOTE: this issue is specific to #13767 (comment) CC @WoLewicki |
@mvtglobally, do you mean this is happening on the branch from that PR? |
@Luke9389, correct! It is NOT a staging app issue |
Given that the linked PR is a draft, should we delete this issue? |
@Luke9389 Dont delete it pls. There is a special request for this. Tagged you in Slack. |
Oh ok cool, thanks @mvtglobally! |
@roryabraham @AndrewGable Let us know if any special tagging required for this issue. |
Just spoke with @mvtglobally 1:1 on slack, and the context for this issue is here: https://expensify.slack.com/archives/C9YU7BX5M/p1672784184899339 Looks like we're performing regression tests for a build on the branch of the linked PR. For that reason I don't think this is a deploy blocker. |
@WoLewicki - Please comment so I can assign you, this is the crash for Fabric. |
I'll be working on the issue. |
I will be working alongside @WoLewicki. |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This issue should be fixed by WoLewicki@6e6f84f which updates the commit The issue was coming from the fact that |
@j-piasecki, @WoLewicki Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
This issue has not been updated in over 14 days. @j-piasecki, @WoLewicki eroding to Weekly issue. |
Looks like all that's left here is to circle back and make sure that this bug is fixed on a new fabric build |
This issue has not been updated in over 15 days. @j-piasecki, @WoLewicki eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@j-piasecki, @WoLewicki, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
@j-piasecki, @WoLewicki, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
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:
User able to log in
Actual Result:
App crashed when try to login.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.49.0 Thu, 5 Jan 2023 18:02 PM
Reproducible in staging?: Yes
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5887387_RPReplay_Final1673042074.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: