Mobile release 1.20

[churik]

Issue to manage mobile release 1.20

Scope

https://github.com/status-im/status-mobile/milestone/59

• release notes: https://github.com/status-im/status-mobile/blob/327d456f696d817663259636cedaed50513cd28d/RELEASES.md 1.20;
• release branch: https://github.com/status-im/status-mobile/tree/release/1.20.x
• release build: https://ci.infra.status.im/job/status-mobile/job/release/job/release%252F1.20.x/

Testing info

Main test suite: https://ethstatus.testrail.net/index.php?/runs/view/9921

Builds in TestFlight and PlayStore to push as a release

Process

1) Kick-off

• 1. Translation PRs is merged before cutting branch (Jinho) Update translation for 1.20 #13729
• 2. Prepare scope of visible changes based on commits history, started from previous release branch cut (guide)
• 3. Update RELEASES.md with release notes (make PR based on previous step)
• 4. Create release branch using this guide, bump VERSION (merge created PR (example ) to develop) and get successful release builds (so, testing can be started)
• 5. Based on release scope, ask for comms (Jonny)
• 6. Make sure that assets (screenshots, video) in stores are up-to-date, more info here

2) Testing

• Dogfooding (add notes, if it was held)
• Regression testing for release candidate build
• Upgrade tests
• Fix known blocker(s) found during regression testing

Blockers

• Stickerpacks installed on 1.19 are not usable on 1.20 #13887
• Group chats, created from 1.19 are shown with no icon on 1.20 #13889
• No icon for ETH in 1-1 transaction messages #13891
• Adding/removing user from contacts duplicating their messages in profile #13892
• Long/heavy audio messages are not sent #13914
• Sometimes images of HEIF and HEIC formats are not sent from iOS #13916
• Opposite from actual status of contact request in activity center on paired device after sync #13956
• Tenor gif preview is not shown on status mobile #13955
• Group chat history unavailable for newly added member until some action is taken (some messages can be lost) #13957
• Alert "failed to send message {message: not implemented} when sending first message in community channel #14009

============================================================================================

Fixes (cherry-pick)

• fix old stickers #13901
• fix Adding/removing user from contacts duplicating their messages in … #13897
• fix no icon for ETH in 1-1 transaction messages #13898
• Group chats, created from 1.19 are shown with no icon on 1.20 #13889 fix in 896ce95
• IOS fixes in 1e37ff9 and 5487868
• [#13855] Sync last contact request decisions on Sync All #13881 (not a blocker, but relevant fix)
• [#13894] Update activity indicator on removed contact request #13902 (not a blocker, but relevant fix)
• fix ios keycard recovery pin error #13924 (not a blocker, but relevant fix)
• Implemented more comprehensive file compression to handle large files status-go#2837 fix for Sometimes images of HEIF and HEIC formats are not sent from iOS #13916
• Update translation #13938
• Reduce recording time to 1 minute #13944

============================================================================================

• Verify fix(es) on new release candidate build
• Retest
• Keep release build forever (button in Jenkins)

3) Submission

• 1. Prepare PR for F-droid build (instruction)
• 2. Release notes written and added (500 character limit for updates (Android) and PR for RELEASES.md is ready to be merged (from 1.3 step)
• 3. Submit beta version for Android (Open Testing in Play Store)
• 4. Submit iOS build to Apple review (instruction, be careful - low quality of audio)
• 5. Play store content reviewed and updated
• 6. Privacy policy reviewed and updated (ask in channel)
• 7. Countries to be excluded (ask in channel)
• 8. Changes to our FAQ made (should be checked and if any changes needed, ask Jakub to made them)

4) Before publishing

• 1. Translations for comms available (marketing, ask in the channel)
• 2. Promotional content ready (marketing, ask in channel)
• 3. Upload builds for DO store, https://dev.status.im/ (Jakub)

5) At time of publishing

• 1. Notify marketing to push comms and blog post (Jonny + get review on blog from QA team)
• 2. Publish release to app store and playstore
• 3. Final push to update prod site https://status.im/, instructions (Jakub - requires credentials to upload)
• 4. Add the link to the post about the release and publish the release: https://github.com/status-im/status-mobile/releases (Jakub)
• 5. Merge PR for updating RELEASES.md (from 1.3 step)

[flexsurfer]

Fdroid PR: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11770