-
Notifications
You must be signed in to change notification settings - Fork 34
App Deployment
This page of the Wiki describes how deployment works and the steps required to deploy the app.
The way deployment is set up is very simple.
Note: When you push changes into develop
or master
, Travis will automatically set the versionCode
or buildNumber
to be that of the travis build. This ensures that the build numbers always increase.
All changes to the app must first occur in the develop
branch, by default this is also where all the PRs are merged into. Once a change occurs in develop
, Travis is triggered and it will Build alpha
versions and submit.
NOTE: Alpha builds are basically builds which get sent out to a closed group of people. If you want to submit to a larger group of people then you need to make a Beta release. Beta releases will have to be submitted manually for both platforms and that can be done in TestFlight or Google Play console.
This is the final step in the process. Any changes here WILL be pushed to the store as a Release, so be very careful. The only way this branch should change is by merging the develop
branch into it. Travis will build final versions and submit.
NOTE: There are a few extra steps that need to be done, which are listed below, to ensure that the app is released properly. Any kind of change (hot fixes, release) should follow those steps.
There is only 1 thing that needs to be changed before we can merge everything into master
for release, The app version.
The app version is the string that will be displayed when users visit the store. Once everything has been changed/tested, you can decide on what the next version will be (i.e 1.0 -> 1.1 or 1.0 -> 1.0.1).
After changing the version, you should make a PR into the develop
branch and follow the deployment process above to get the changes in.
- Open
android/app/build.gradle
. - Replace
versionName
with the new code. DO NOT touchversionCode
.
There are 2 ways to change version in iOS, pick the one that you prefer.
- Go to
ios/
and openkitsu_mobile.xcodeproj
. - Click
kitsu_mobile
at the very top of the left file panel. - Click the
general
tab. - Change the version listed under
Version
.
- Go to
ios/kitsu_mobile
. - Open
Info.plist
. - Find
CFBundleShortVersionString
. - Replace the string value below it with the version string.
<key>CFBundleShortVersionString</key>
<string>**Version String Here**</string>
Once all the changes have been merged into master the following has to be done:
- Go to iTunes Connect and create a new version release, set the meta data and submit for review.
- Go to Google play console and click on the app.
- Follow https://support.google.com/googleplay/android-developer/answer/7159011 from Step 3 onwards.
- Make sure the Prerequisite section is done.
- Create a new GitHub release with the tag that is incremented from previous version.
- In the notes include what iOS and Android version was released as well as the release notes.