[SOLVED] Android apk Parse Error

[Kekipen]

SOLUTION:// Make sure the package name containing no numbers only A - Z . _ characters can be used.


Hi. I'm new to AGK 2 (and developing mobile apps)
I'm trying to install a package exported from AGK 2 on my Android device running Android 4.2.2

When I try it, I get Parse Error message. I was searching the web whole day but unable to find any useful solution out there. Most people say, we get this error mostly if the package is corrupted or the package is not compatible with the actual version of the Android OS. Also some people say that, it may caused by permission problems but there is no useful infromation how to solve any of these problems.

Corruption:
-repack
-reupload
-redownload
Done several times, I don't think it would be a problem

Compatibility:
- my Android version is 4.2.2, not sure if it a problem, would be nice to get some thoughts on this from the devs of AGK 2

Permission:
-no real solution, some people mentioning by using different apps such as Astro, Google Drive..etc helped to install the app but as far as I understand, by end of the day, all of the apps using the same package installer. Even if I install an "apk package installer", I end up with the same dialog asking me to open the package using "Package Installer" and I get this Parse Error message. Also some people mentioning by uploading to Google Play, it solves the problem, but I just don't want to pay 25 dollar registration cost just yet only to test this.
In the settings, install apps from unknown sources is enabled.

At the moment I'm really disappointed as I have purchased AGK 2 in first place for mobile development, and becasue it is advertised as "code once and deploy to multiple platforms" I was expecting a really easy, fully compatible solution offered by AGK 2 but it is not the case but I'm still hoping maybe I overlook something or it a bug somewhere so can be solved, but I can't find a solution.

I can stream (broadcast) the app from my PC to my android device using AGK 2 Player, but I don't think it is a real solution. AGK 2 Player is a good way to quickly test changes without need to exporting, uploading, downloading and installing the app every single time somehting is changed but by end of the day I would like to see the actual app running natively on the actual device and OS.

Anybody could help me with this?

Thanks

[Matt [Linux]]

Im assuming the app your having issues with is one you have made yourself in AGKv2.

If so, can you just open one of the examples which came with AGKv2 and export that to an APK and see if that works on your device?

lets figure out if its your app thats the issue, or the export of any app from the editor thats the issue.

also do you have another android device to try this on, to see if its your device thats the issue.

Lets try and isolate whats causing this.

:)

[Kekipen]

Hi, thanks for the reply.

Yes I made this app my self, just a very basic calculator to Learn AGK 2 and test android export so I don't mind to share the project file if it helps.

But I have also exported an example comes wiith AGK2 (GasCloud) and I get the same error :(

Unfortunately I don't have any other Android device around here but I've used HTML5 to APK build services before such as IntelXDK and Crosswalk, not directly but tools using these services to provide cross-platform development and the apk's from these tools did work on my device.

[Matt [Linux]]

ok, so at least we know its not your AGK project thats the issue :)

Have you tried uninstalling and re installing AGKv2 on Steam?

[Kekipen]

Yes I have uninstalled and re installed AGK and re exported the GasCloud example, but didn' t solved the problem :(

Maybe I can get my hands on an other android device later today so I can test if it something with my device or not, but would be nice if someone with access to AGK 2 and an android device could test it with the GasCloud example :) If it fail to install also on other devices, it should be a problem with AGK 2...

[Matt [Linux]]

Ive just compiled GasCloud and put it on my Nexus 7 and my Nexus 4, which are both running Android 5.1 Lollipop and it works fine on both.

How are you getting the APK onto your device?

Are you using a USB cable or some kind of file sharing like google Drive?

Did ou manage to get another android device to test this on?

[Kekipen]

I'm using google drive.

No, I did not managed to get one, maybe tomorrow but in case the export works for you it can be a compatibility problem with my Android 4.2
This is a cheap "AllWinner" tablet. I don't know if the version of the OS or the origin/manufacturer of the tablet do anything with the error but at least seems like it not complatly broken, other devices (probably the most popular ones running updated versions of Android) can run the exported apps :)

Thanks.

[Matt [Linux]]

Ive got an old device running Android 4.0 (i think its 4.0), ill try it on that later if i can find it.

When you export the project to an APK, there are two versions of the Android SDK to choose from, SDK 2.3.1 and SDK 3.2.

Have you tried both to see if they both give this error?

[Kekipen]

Yes I have tried both, I have also tried Google, Amazon and Ouya APK type, I have also tried to add keystore file, icon image, also with no keystore file and icon image, nothing helps.

Some places mentioning, such error can be caused also by the AndroidManifest.xml inside the pack. I don't know if it actually do anything with the error I get, but basically, during installation, the OS is reading this file to see what is the name and version of the app, what permissions are required, what Android version is recommended and what locations are used in the internal memory by the app and if the OS can't read the file or there is a typo in the file (lower case, upper case letters, spaces, dots) it can cause parse error.

If it is a compatibility problem with my Android version, maybe it because of the format or encoding of the Manifest file. I'm going to look at the manifest file of the other apk's later I have from other tools (and can install and run on this device) to see if I can get it to work by making my own manifest file.

[Kekipen]

Managed to get my hands on the other Android device running Android 4.0 and I get the same parse error :(

I have also tried to install the AGK 2 player.apk comes with AGK 2 (not from the store), and I can install that with no problems but not the apps exported from AGK 2.

I think I leave it as is until a developer come around with some thoughts on this.
At the momnet I could afford to buy Android devces running Android v4.4 KitKat, but if I get the same error it would be just waste of money as I don't need new android device for personal use, but I would buy one for development. I think TGC should officially highlight what Android versions are actually supported out of the box by using Tier1 (Basic).
v4.0 and v4.2 clearly not supported to install exported apk's as "non Market apps", maybe can be solved by uploading them to a Market but I'm not in tha situation to be able to do that.

But at least the AGK 2 Player works flawlessly so I can still test my apps even on this old versions until I can afford a new android device running newest version of android or find a solution to install and run AGK 2 apps on this old versions :)

[Matt [Linux]]

Im going to try an my old Nexus 7, i think thats on 4.0. Could you upload your APK to dropbox or somewhere i could download it and try it.

[Sku;Te]

Have you checked to make sure the transfer to the Android device isn't corrupt (check the file size on the Android device)? Do you have enough space to install the APK ? Can you make it available ?

[Kekipen]

Finally, I have solved the problem!
You not gonna believe it XD

When I was enter the package name, a message box did come up and saying I need to use at least one dot (.) in my package name, and so I decided to go with "name_1.0" and the Android system didn't like this but I never thought it could be a problem as have been told I need to use a dot, so there you go, you have a dot right there, have a nice day. And I was doing this every single time. But now I have noticed the hint "A-Z. and underscore only, should be in the format com.mycompany.my_app" I was follow the hint and named my package using only A-Z._ and guess what? IT WORKS! I spent my whole weekend looking for a solution because of "1.0" in the package name....
I can't believe it.

So here is the solution:
NEVER USE NUMBERS IN YOUR PACKAGE NAME!!

Thanks for all the help :)

[Matt [Linux]]

lol, Thats crazy :)

Glad it all worked out for you buddy