You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 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:
Identify the pull request that introduced this issue and revert it.
For users who have once received the update will set the ONYKEYS.UPDATE_AVAILABLE to true.
We have an issue in Onyx where if the value does not change, Onyx will not trigger an update notification to the component.
Each time you start the app, we ignore (initWithStoredValues: false) the stored value of ONYKEYS.UPDATE_AVAILABLE which is already true as you once received the update.
Now on next time you receive the update, Set ``ONYKEYS.UPDATE_AVAILABLE` to true which will not have any effect as Onyx will not set the notification to UpdateModal component, and thus component will never be shown.
Ah okay that makes more sense! Thanks for the explanation. It looks like we are actively working on that issue then, so does it make sense to wait to see if that Onyx fix fixes this issue?
Activity
MelvinBot commentedon Aug 11, 2021
Triggered auto assignment to @jboniface (
AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.roryabraham commentedon Aug 11, 2021
I believe this regression was most likely caused by #4406, but haven't confirmed.
OSBotify commentedon Aug 11, 2021
👋 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:MelvinBot commentedon Aug 11, 2021
Triggered auto assignment to @alex-mechler (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.roryabraham commentedon Aug 11, 2021
Shouldn't have included the
AutoAssignerTriagelabel, my bad @jboniface.2 remaining items
alex-mechler commentedon Aug 11, 2021
Also going to drop to a daily instead of hourly, but I still think this is quite important
parasharrajat commentedon Aug 11, 2021
This is caused by a break-in in the Onyx architecture. #4500
alex-mechler commentedon Aug 11, 2021
@parasharrajat Can you explain the connection a little more? I'm not seeing how that causes this, but it might.
parasharrajat commentedon Aug 11, 2021
ok. @alex-mechler
ONYKEYS.UPDATE_AVAILABLEtotrue.initWithStoredValues: false) the stored value ofONYKEYS.UPDATE_AVAILABLEwhich is already true as you once received the update.alex-mechler commentedon Aug 11, 2021
Ah okay that makes more sense! Thanks for the explanation. It looks like we are actively working on that issue then, so does it make sense to wait to see if that Onyx fix fixes this issue?
parasharrajat commentedon Aug 11, 2021
Yes
parasharrajat commentedon Aug 12, 2021
I have added the fix #4604. Please watch out if that fixes it.
alex-mechler commentedon Aug 24, 2021
This has not happened to me again since that PR went out to staging. Thanks @parasharrajat!