[Release] Element Android v1.3.15 - Corrective release

[bmarty]

Release checklist

This is a corrective release and it will contain:

• Crash fixed in Timeline : fix 4959 #4966
• Crash fixed in Fix crash on API <24 and make sure this error will not occur again. #4962
• A fix for Crash when viewing source which contains an emoji #4796 - jitpack is confused again, we will import the source in a module in this project. -> @bmarty
• A fix for App crashes on attempt to log in to SAML-only homeserver #4969 -> @ouchadam
• Other?

Please base your PRs on branch hotfix/1.3.15

The App the SDK and the sample will be released. Only the app will be released, no change in the SDK.

Before the release

No Weblate sync

Do the release

• Create hotfix with gitflow, branch name hotfix/1.3.15
• Change version to 1.3.15 (app and SDK)
• Check the crashes from the PlayStore
• Check the rageshake with the current dev version: https://github.com/matrix-org/element-android-rageshakes/labels/1.3.15-dev
• Run the integration test, and especially UiAllScreensSanityTest.allScreensTest()
• Create an account on matrix.org
• Run towncrier: towncrier --version v1.3.15 --draft (remove --draft do write the file CHANGES.md)
• Add file for fastlane under ./fastlane/metadata/android/en-US/changelogs
• Push the branch and start a draft PR (will not be merged), to check that the CI is happy with all the changes.
• Finish release with gitflow, delete the draft PR
• Push main and the new tag v1.3.15 to origin
• Checkout develop
• Increase version in ./vector/build.gradle
• Change the value of SDK_VERSION in the file ./matrix-sdk-android/build.gradle
• Commit and push develop
• Wait for Buildkite to build the main branch.
• Run the script ~/scripts/releaseElement.sh. It will download the APKs from Buildkite check them and sign them.
• Install the APK on your phone to check that the upgrade went well (no init sync, etc.)
• Create a new beta release on the GooglePlay console and upload the 4 signed Apks.
• Check that the version codes are correct
• Copy the fastlane change to the GooglePlay console in the section en-GB.
• Push to beta release to 100% of the users
• Create the release on gitHub from the tag, copy paste the block from the file CHANGES.md
• Add the 4 signed APKs to the GitHub release
• Ping the Android Internal room
• Add an entry in the internal diary

Once Live on PlayStore

• Ping the Android public room and update its topic

After at least 2 days

• Check the rageshakes
• Check the crash reports on the GooglePlay console
• Check the Android Element room for any reported issues on the new version
• If all is OK, push to production and notify Markus (Bubu) to release the F-Droid version
• Ping the Android public room and update its topic with the new available version

[bmarty]

I had an init sync on my device (installing with adb) :/

EDIT
From the rageshake:

2022-01-18T15:21:57*249GMT+00:00Z 468810 E/ /Tag: ************************************************************
2022-01-18T15:21:57*250GMT+00:00Z 468810 E/ /Tag: The realm file session was corrupted and couldn't be loaded.
2022-01-18T15:21:57*251GMT+00:00Z 468810 E/ /Tag: The file has been deleted to recover.
2022-01-18T15:21:57*252GMT+00:00Z 468810 E/ /Tag: ************************************************************

It happens sometimes when installing from ADB