Skip to content

Update app modal does not display #4537

Closed

Description

@roryabraham

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:

  1. Receive an app-update notification on desktop
  2. Click on the notification.

Expected Result:

An modal is displayed asking if you want to update and restart the app.

Actual Result:

The app is focused, but no modal is displayed. The user must use the app menu to update.

Workaround:

Use the app menu to update:

image

Platform:

  • Desktop App

Version Number: 1.0.83.0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:

View all open jobs on Upwork

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Aug 11, 2021
  2. MelvinBot commented on Aug 11, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @jboniface (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

  3. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Aug 11, 2021
  4. roryabraham commented on Aug 11, 2021

    @roryabraham
    ContributorAuthor

    I believe this regression was most likely caused by #4406, but haven't confirmed.

  5. OSBotify commented on Aug 11, 2021

    @OSBotify
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. MelvinBot commented on Aug 11, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @alex-mechler (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  7. roryabraham commented on Aug 11, 2021

    @roryabraham
    ContributorAuthor

    Shouldn't have included the AutoAssignerTriage label, my bad @jboniface.

  8. 2 remaining items

  9. alex-mechler commented on Aug 11, 2021

    @alex-mechler
    Contributor

    Also going to drop to a daily instead of hourly, but I still think this is quite important

  10. parasharrajat commented on Aug 11, 2021

    @parasharrajat
    Member

    This is caused by a break-in in the Onyx architecture. #4500

  11. alex-mechler commented on Aug 11, 2021

    @alex-mechler
    Contributor

    @parasharrajat Can you explain the connection a little more? I'm not seeing how that causes this, but it might.

  12. parasharrajat commented on Aug 11, 2021

    @parasharrajat
    Member

    ok. @alex-mechler

    1. For users who have once received the update will set the ONYKEYS.UPDATE_AVAILABLE to true.
    2. We have an issue in Onyx where if the value does not change, Onyx will not trigger an update notification to the component.
    3. 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.
    4. 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.
  13. alex-mechler commented on Aug 11, 2021

    @alex-mechler
    Contributor

    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?

  14. parasharrajat commented on Aug 11, 2021

    @parasharrajat
    Member

    Yes

  15. parasharrajat commented on Aug 12, 2021

    @parasharrajat
    Member

    I have added the fix #4604. Please watch out if that fixes it.

  16. alex-mechler commented on Aug 24, 2021

    @alex-mechler
    Contributor

    This has not happened to me again since that PR went out to staging. Thanks @parasharrajat!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions