Android Application Version Control
Introduction
This document explains the Mobage Native/Unity SDK “optional update function” and “forced update function” provided in Android application settings of the Developer’s Site. Both update functions are used for updating the apk for actual release and can be used after the Application Release Submission is passed.
Optional Update Function
The “optional update function” is provided on the Developer’s Site and supports the Mobage version only. (Click here to find information on the differences between the Mobage version and the Google Play (formerly called Android Market) version)
In the event that the version of apk file launched by the user is older than the most recent version of apk file for actual release, the following update prompt screen will appear instead of the login screen.
Button Actions
- If the “yes" button is tapped, the most recent apk file will be automatically downloaded and the update will be completed when the user installs it through the notification bar.
- If the “no” button is tapped, either the normal login screen will be displayed or automatic login will be performed.
Important Points
- If the “no” button is tapped, the update screen will not be displayed again after 10 minutes or later. If the application is restarted within 10 minutes, either the normal login screen will be displayed or automatic login will be performed.
- By using the Back key on Android devices when the update screen is displayed and calling the onLoginCancel() method, the update screen will not be displayed again as long as over 10 minutes have not passed as above. With the onLoginCancel() method, the normal login screen will be displayed if the application is terminated or restarted.
Forced Update Function
The “forced update function" is provided on the Developer’s Site and supports both the Mobage version and the Google Play version (Click here to find information on the differences between the Mobage version and the Google Play version).
“Forced update function” provides a complete forced update function.
The following items “Version History” and “forced update version selection” can be displayed by selecting [Managge Application] > [Optional Native/Unity applications] > [Android Application Settings] > [To apk management screen] on the Developer's Site. If several apk for actual release are uploaded, multiple versions will be displayed in the Version History as below.
Version History
The following contents are displayed in the Version History:
| Version Number | The VersionName specified in the AndroidManifest.xml is displayed in Version Number. | |
| Registration Date | The date when developers uploaded appropriate version. | |
| Updated Date | The date when actual release version has uploaded. | |
| Forced Update Version | A “○” appears for versions specified in the “Forced Update Version Selection” in the next section. | |
| Actual Release Upload | ||
| “Uploading” | ・“Uploading” status appears from when the apk files for actual release starts uploading from apk file for actual release upload item until the files have set on either Mobage version or Google Play version of distribution server.
・A certain amount of time is required to complete updates because DeNA updates Google Play version on the Google Play manually. |
|
| “Complete” | ・ Both the Mobage version and the Google Play version have been set on the distribution server. (limited to the most recent version) ・ If the status turns “Complete”, the version can be selected as the version for “Forced Update Version Selection” in the next section. |
|
Forced Update Version Selection
The function in Forced Update Version Selection that is used for displaying forced update screen to the users based on the following rules.
- When the version is lower than the forced update version, the forced update screen will appear instead of the login screen.
- When the version is higher than the forced update version, the optional update screen will appear instead of the login screen.
Forced update screen
Button Behaviors
- In the case of the Mobage version, if the “yes" button is tapped, the most recent apk file will be automatically downloaded, and the update will be completed when the user installs it through the notification bar.
- In the case of the Google Play version, if the “yes” button is tapped, the user will be transferred to the appropriate Google Play application distribution page, and the update operation is completed by tapping the “update” button.
Important Points
When using the forced update function, the forced update screen might not be displayed for up to 10 minutes after setting the function.
The reason for this problem is as below.
If a user taps the “No” button on the automatically-displayed optional update screen, the login screen is displayed for 10 minutes instead of the optional update screen. However, if the developer configures the forced update setting on the Developer’s Site during this 10 minutes period, instead of the forced update screen the login screen may be displayed.
1. User taps “No” on the optional update screen.
2. Regular login screen is displayed for 10 minutes.
3. Developer sets the forced update function during this 10 minute period.
4. For this user, the forced update screen is not displayed for 10 minutes.
Please note this when configuring the forced update function.
Revision History
- 11/12/2012
- Revised due to the release of complete forced update function.
- 08/07/2012
- Change "Android Market" to "Google Play".
- 03/14/2012
- Initial Release.