- test the build on a real device. It is imperative that you run selftest and it gives you OK
- if necessary, up version number in all relevant files (you can use
./edit-version-number.sh
) - run
./scripts/release-notes.sh
- it prints changelog between latest tag and now, put this output under new version in fileios/fastlane/metadata/en-US/release_notes.txt
(on top); if file got too big delete the oldest version from the bottom of the file - now is a good time to commit a ver bump and release notes changes
- create this release version in App Store Connect (iTunes) and attach appropriate build. note last 4 digits of the build and announce it - this is now a RC. no need to fill release notes yet
cd ios/
and then runDELIVER_USERNAME="[email protected]" DELIVER_PASSWORD="my_itunes_password" fastlane deliver --force --skip_binary_upload --skip_screenshots --ignore_language_directory_validation -a org.doichain.doiwallet --app_version "6.6.6"
but replace6.6.6
with your version number - this will upload release notes to all locales in itunes- go back to App Store Connect and press
Submit for Review
. choose Yes, we use identifiers - for installs tracking - once its approved and released it is safe to cut a release tag: run
git tag -m "REL v6.6.6: 76ed479" v6.6.6
where76ed479
is a latest commit in this version. replace the version as well. then rungit push origin --tags
- you are awesome!
- do android after ios usually
- test the build on a real device. We hace accounts with browserstack where you can do so.
- its imperative that you run selftest and it gives you OK. note which build you are testing
- go to appcenter.ms, find this exact build under
master
builds, and pressDistribute
->Store
->Production
. inRelease notes
write the release, this field is to smaller than iOS, so you need to keep it bellow 500 characters. - now just wait till appcenter displays a message that it is succesfully distributed
- noice!