About Packaging

In order to make an ngCore Android app work as a standalone app, it is necessary to create an apk file by combining the zip file that is uploaded on the Developer’s Site and a runtime that serves as the base.

The resulting apk file is then released on Google Play and Mobage.

The Difference between the Baked Version and Runtime Version

There are 2 SDK versions: the ngCore SDK version which has been “baked” (build) and the runtime ngCore SDK version.

As these 2 versions are in a containment relationship, the baked ngCore SDK version cannot be higher than the runtime version. (Baked ngCore SDK version <= Runtime ngCore SDK version)

Since runtime is upward compatible, the runtime selected at the time of release will be the runtime file of the latest SDK version available.

About Applications for SDK Upgrades

After the app goes live, and a new ngCore SDK is released and has become available on the Developer’s Site, the zip file baked with the new ngCore SDK can then be uploaded to the Developer’s Site.

However, the above baked zip file cannot be specified for production.

Since they can be specified for development, apk files become available for download from the download button in the Sandbox app download section. The apk file that can be downloaded here is that which was combined with the runtime of the same version as that of the ngCore SDK used for baking.

Application for SDK upgrade refers to the application to be filed when using a newer runtime version of the apk file than the version being used in the apk file that is currently live on Mobage or Google Play.

Process of Applications for SDK Upgrades

From “SDK version” in the Android Application Settings for the target app, you can check the currently released runtime ngCore SDK version. If the “Upgrade” button appears to the right of “SDK version” as shown in the above image, an upgrade is available.

Clicking the “Upgrade” button will display the “SDK Version Management” screen, as seen below.

When you click the “Upgrade” button to the right of the version you wish to upgrade to, a confirmation dialogue appears. After agreeing to the precautionary notes and clicking the “OK” button, the application for upgrade will be complete. 

Please make sure to read the notes below.

Notes on Application for SDK Upgrade

There are important points to be noted regarding applications for SDK upgrades, including notes on problems that may affect all users. Please file your application after thoroughly reading the following notes.

• Once the SDK upgrade is complete, all users who have obtained the apk file that is live on Google Play and Mobage will be asked to re-download the apk file. For resources included in the secondary manifest, users will be asked to download the difference only.
• While the application for upgrade is in process, version updates of the app for production/development cannot be performed.
• Completing the upgrade may take 3 -4 business days.
• The apk file to be distributed is created and released by combining the zip file with the version number specified for production at that time and the runtime SDK version that you applied for. Please note that the zip file that is currently released in the production is used for combination, even if you uploaded a zip file you baked with a new ngCore SDK version. -Resources in manifest.json will be combined.
• The apk file will be created by referencing the currently registered information (Launcher Icon, Application Label). If you wish you update the registered information, please make the change beforehand.
• During the upgrade application process, the button to the right of “SDK version” changes from “Upgrade” to “Cancel”. Clicking here cancels the application. The “Cancel” button is displayed until a DeNA staff member starts the upgrade process.

Revision History

• 09/24/2012
  • Initial Release.