Skip to content

Deploy Checklist: New Expensify 2024-04-10 #40026

Closed

Description

@github-actions

Release Version: 1.4.62-17
Compare Changes: production...staging

This release contains changes from the following pull requests:

Deploy Blockers:

Deployer verifications:

  • I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
  • I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
  • I checked GitHub Status and verified there is no reported incident with Actions.

cc @Expensify/applauseleads

Activity

  1. kavimuru commented on Apr 10, 2024

    @kavimuru

    Checking off the PROD PRs (help.expensify.com)
    #39387
    #39664
    #39666
    #39667
    #39669
    #39826

  2. blimpich commented on Apr 10, 2024

    @blimpich
    Contributor

    Demoting #40027

  3. roryabraham commented on Apr 10, 2024

    @roryabraham
    Contributor

    #40050 is intended behavior

  4. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    #40082 is not a blocker
    #39982 is not a blocker
    #40052 is not a blocker

  5. twisterdotcom commented on Apr 11, 2024

    @twisterdotcom
    Contributor

    Closed #40093

  6. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    #40053 is minor and related to a new feature (live-markdown)
    #40086 is a console log, demoted

  7. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    #40085 demoted as not critical

  8. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    #40067
    and #40029 fixed by this CP: #40079

  9. Julesssss commented on Apr 11, 2024

    @Julesssss
    Contributor

    #40036 fixed by #40049

  10. 6 remaining items

  11. kavimuru commented on Apr 11, 2024

    @kavimuru

    Regression is completed.
    Unchecked PRs:
    #39394 we need more details about the QA steps and not sure it is internal. Comment
    #38730 failing with #40103
    #38947 failing with #40048
    #39190 failing with #40029
    #39239 failing with #40043
    #39372 failing with #40041
    #39454 failing with #40108
    #39562 failing with #40036
    #39788 failing with #40052
    Open Blockers:
    #40034
    #40037
    #40040
    #40041
    #40048
    #40057
    #40076
    #40077
    #40078
    #40084
    #40087
    #40105
    #40107
    #40108
    #40123
    #40124

  12. rlinoz commented on Apr 11, 2024

    @rlinoz
    Contributor

    Demoting #40105

  13. Beamanator commented on Apr 12, 2024

    @Beamanator
    Contributor

    This CP'd PR fixed #40080, both are checked off the list now

  14. roryabraham commented on Apr 16, 2024

    @roryabraham
    Contributor

    confirmed #40077 is fixed, checking it off

  15. roryabraham commented on Apr 18, 2024

    @roryabraham
    Contributor

    ok, so we've been talking through this checklist in #fireroom-2024-04-17-app-deploy. Ultimately it has not gone very smoothly, and that's largely due to inconsistently reproducible but critical issues that have happened in concert with enabling the new architecture.

    Our plan is to ship this release on all platforms except Android, where we're aware of a number of unresolved critical issues. This will allow us to continue shipping code on all other platforms and prevent the monster release that will follow this one from growing any more cumbersome than it already promises to be.

  16. roryabraham commented on Apr 18, 2024

    @roryabraham
    Contributor

    #40360 is fixed by #40383 in 1.4.62-15 (without re-introducing #40077)

  17. roryabraham commented on Apr 18, 2024

    @roryabraham
    Contributor

    #40048 and #40108 share the same root cause, and remain unresolved. These are Android-only issues, and as mentioned above I'm going to check them off. They will continue to have the deploy blocker label, so should appear as deploy blockers in the next checklist

  18. thienlnam commented on Apr 18, 2024

    @thienlnam
    Contributor

    There's only one fresh crash
    SensorSetter.sensorSetter

    Fatal Exception: com.facebook.jni.CppException
    Exception in HostFunction: Error: Exception in HostFunction: at _maybeFlushUIUpdatesQueue (native) at anonymous (JavaScript:1:405) at callMicrotasksOnUIThread (JavaScript:1:61) at anonymous (JavaScript:1:406)

    com.swmansion.reanimated.nativeProxy.SensorSetter.sensorSetter (SensorSetter.java)

    It's only happened to a single user on 1.4.62-7 so I think we're okay here -

  19. thienlnam commented on Apr 18, 2024

    @thienlnam
    Contributor

    :shipit:

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