Skip to content

Deploy Checklist: New Expensify 2024-01-04 #33973

Closed

Description

@github-actions

Release Version: 1.4.22-6
Compare Changes: production...staging

This release contains changes from the following pull requests:

Internal QA:

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. OSBotify commented on Jan 4, 2024

    @OSBotify
    Contributor

    🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.4.22-0 🚀

  2. jasperhuangg commented on Jan 5, 2024

    @jasperhuangg
    Contributor

    Checking off #34003 this appears to be a back-end issue.

  3. youssef-lr commented on Jan 5, 2024

    @youssef-lr
    Contributor

    Demoting #34018

  4. kbecciv commented on Jan 5, 2024

    @kbecciv

    Regression is 1% left

    #29730 failing #33986, repro in prod, Checking Off
    #32562 - Validation pending
    #32594 - Validation pending
    #32792 - Validation pending
    #32799 - Validation pending
    #32902 failing #34018
    #33242 - Validation pending
    #33421 - Validation pending
    #33730 - Validation pending
    #33744 - Validation pending
    #33791 - Validation pending
    #33829 is blocked in Desktop with #25790 (comment), checking Off

    Deploy Blockers:

    #33984
    #33985
    #33989
    #34004
    #34016
    #34017

  5. Beamanator commented on Jan 5, 2024

    @Beamanator
    Contributor

    testing #33730 myself, i meant to make it internal QA 😳

    • Looking good! Also super small note: There's this follow-up to fix the case where special characters are not showing up perfectly in NewDot, and there's already a PR for it - so NAB
  6. blimpich commented on Jan 5, 2024

    @blimpich
    Contributor

    Checked off #34050 as I don't think its a blocker.

  7. rlinoz commented on Jan 5, 2024

    @rlinoz
    Contributor

    Checking off #34053 as I don't think it is a blocker.

  8. kbecciv commented on Jan 5, 2024

    @kbecciv

    Regression is completed!

    #29730 failing #33986, repro in prod, Checking Off
    #32562 failing in Android app and Android/Chrome #34068, repro in Prod, checking Off
    #32902 failing #34018
    #33791 failing #34054, repro on prod, Checking Off

    Blockers:
    #33984
    #33985
    #33989
    #34004
    #34016
    #34017
    #34043
    #34045
    #34047
    #34051
    #34063
    #34052
    #34055
    #34058

  9. amyevans commented on Jan 5, 2024

    @amyevans
    Contributor

    Checked off #34058 as NAB

  10. marcaaron commented on Jan 5, 2024

    @marcaaron
    Contributor

    Checking off #33989. Does not seem related to any new changes and is not a serious problem AFAICT.

  11. marcaaron commented on Jan 5, 2024

    @marcaaron
    Contributor

    Checking off #34004 as it is the expected behavior.

  12. marcaaron commented on Jan 5, 2024

    @marcaaron
    Contributor

    Closed #34017 as it looks like a dupe.

  13. roryabraham commented on Jan 6, 2024

    @roryabraham
    Contributor

    #34006 was only CP'd on all platforms about an hour ago. I haven't looked closely at the deploy blockers, but I suspect that some of them may have been caused by that. Maybe it's worth it to just ask Applause to retest all of them and see which have been fixed?

  14. situchan commented on Jan 6, 2024

    @situchan
    Contributor

    #34006 was only CP'd on all platforms about an hour ago. I haven't looked closely at the deploy blockers, but I suspect that some of them may have been caused by that. Maybe it's worth it to just ask Applause to retest all of them and see which have been fixed?

    #34039 has the same root cause but interesting that it was marked as reproducible in production

  15. marcaaron commented on Jan 6, 2024

    @marcaaron
    Contributor

    Sounds good @roryabraham. Not gonna deploy today so there's no rush.

  16. marcaaron commented on Jan 6, 2024

    @marcaaron
    Contributor

    Checking off #34063

  17. thienlnam commented on Jan 8, 2024

    @thienlnam
    Contributor

    Marked off #33730 for #33730 (comment)

  18. kbecciv commented on Jan 8, 2024

    @kbecciv

    @thienlnam We verified PR #34030 on Web, mWeb and Desktop, the build is not ready for IOS and Android apps.

  19. thienlnam commented on Jan 9, 2024

    @thienlnam
    Contributor

    We're currently working on fixing the iOS and Android broken builds - I can manually QA the rest of these for the deploy

  20. thienlnam commented on Jan 9, 2024

    @thienlnam
    Contributor

    There's quite a few crashes this time from 1.4.17-7

    com.google.mlkit.vision.face.internal.FaceRegistrar.getComponents
    java.lang.NullPointerException - Attempt to invoke virtual method 'int java.util.AbstractCollection.size()' on a null object reference

    MessageSchema.reflectField
    java.lang.RuntimeException - Field packageName_ for wg.a not found. Known fields are [private int wg.a.A00, private java.lang.String wg.a.A01, priva

    The user impact is limited, and I believe these are related to the issue we fixed here since these are all android crashes #34030

  21. thienlnam commented on Jan 9, 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