How to fix the errors that occur when creating the APK package for Android mobile device
Posted by Nico Wang on 12 February 2014 02:40 PM

Phenomenon: You experience the following errors when creating the APK package file.

15:40:11 Start packaging the native mobile app
15:40:12 Copying files to the temporary folder...
15:40:13 Configuring the native mobile app settings...
15:40:13 Start building the native mobile app...

subst A: "C:\Program Files (x86)\Appeon\Developer2013R2\AppTemplate\Android\Adt"
subst B: "C:\Program Files (x86)\Appeon\Developer2013R2\Java\jdk1.6.0_24"
subst G: "C:\Program Files (x86)\Appeon\Developer2013R2\AppTemplate\Android\NativeConfig\TmpDir"
A:\sdk\tools\android update project --name "appeontest" --target 1 --path G:\AndroidNativeApp
set ANT_HOME=B:\ant
set PATH=B:\bin;B:\ant\bin
cd G:\AndroidNativeApp
B:\ant\bin\ant -f buildnative.xml
Buildfile: G:\AndroidNativeApp\buildnative.xml



[echo] proguard.config is ${proguard.config}


[checkenv] Android SDK Tools Revision 22.3.0
[checkenv] Installed at A:\sdk

[echo] Project Name: AwsEx
[gettype] Project Type: Application

[getbuildtools] Using latest Build Tools: 19.0.0
[echo] Resolving Build Target for AwsEx...
[gettarget] Project Target: Android 4.4
[gettarget] API level: 19
subst A: /d
subst B: /d
subst G: /d

15:40:14 Failed to build the native mobile app!


Step 1- Please check and make sure the App Identifier (Appeon Developer > Appeon toolset > Tool > Package) is set by using something like the domain name format e.g. (see below).

Step2- Both the Alias and Alias Password under the App Signing should match with the keystore file that you are using. If you are using the default keystore file provided by Appeon, the values of Alias and Alias Password should be appeon/appeon.

Step3- If the information above are correct, then the JDK under the Appeon developer directory is possibly destroyed, which causes these errors.

At this point, please run the command below in the cmd to check if the JDK is working.

cd C:\Program Files\Appeon\Developer2013R2\Java\Jdk1.6.0_24\bin


If the information you would get isn’t similar to the one included in the following figure then it indicates the JDK maybe has been destroyed. In this case, we would recommend you to reinstall the Appeon developer or copy a valid JDK into the directory “C:\Program Files\Appeon\Developer2013R2\Java\Jdk1.6.0_24”.


#1- If you choose to copy the JDK then please make sure the directory structure should keep consistent with the previous directory structure, otherwise the Appeon developer cannot call JDK properly.

#2- The version of the JDK cannot be lower than 1.6.0_24, as shown below, you can execute the command “java –version” under the bin folder of the related JDK to check its version information.

#3- The Display name should be characters in lower case. Please do not use any special numeric/symbols.

#4- Please do not use the default value com.appeon.appname as the App Identifier. Please specify a distinctive one for it, for example: mycom.myappeon.myapp.






(1 votes)
This article was helpful
This article was not helpful

Comments (0)
Post a new comment 

Please login if you wish to leave a comment about this article.

Help Desk Software by Kayako Fusion