-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-08-14] [HybridApp] Onyx value miss-match triggering welcome modal #46412
Comments
Commenting to be assigned |
Update: From current investigations it seems like problem lies somewhere in Onyx (probably this is specific of HybridApp). It's hard to verify the real root cause without Jason's logs so I'm gonna need them at some point. I think that since we cannot rely on Onyx in this case we can always fallback to values from OldDot. This should simplify the logic a bit. At the moment we have two sources of |
I should be able to prepare PR today. Actually 2 PRs, because fix changes some logic on OD and ND. Then I assume we can create ad hoc build for Jason to make sure that it fixed the problem on his device. EDIT: |
After verification of Jason's NVP it looks like we can introduce simpler fix. I'll prepare PR tomorrow |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.17-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-08-14. 🎊 For reference, here are some details about the assignees on this issue:
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@mateuuszzzzz Huh... This is 4 days overdue. Who can take care of this? |
Problem
In some cases the Welcome Modal is being displayed due to the NVP not being read from Onyx correctly. It is hard to reproduce.
@JmillsExpensify is experiencing this.
Solution
Mateusz has a plan here.
The text was updated successfully, but these errors were encountered: