Got a bugreport from a tester of my newgame: Android Version 4.0.3 he cant install my game.
Error message: “Parse error There is a problem parsing the package.”
On my HTC Sensation also Android 4.0 its working latest daily build: CoronaSDK 2012.819
Please fix this i can release my game with that!!!
Anybody got also this error message?
[import]uid: 86417 topic_id: 26632 reply_id: 326632[/import]
On 818 is working it seems to be the last daily build… [import]uid: 86417 topic_id: 26632 reply_id: 107980[/import]
On 818 is working it seems to be the last daily build… [import]uid: 86417 topic_id: 26632 reply_id: 107981[/import]
Hello Martin,
I’ve noticed that you have flagged this issue as resolved. Just to confirm is it solved? Would you mind sharing with what you did to resolve it? [import]uid: 32256 topic_id: 26632 reply_id: 108347[/import]
i just changed my daily build to 818. But i found also out that it can happend with erros in the build settings.
The mainproblem is that on my test phone i get no errors. I just let it try a other tester.
I hope that others also report it, because it seems difficult to reproduce again… [import]uid: 86417 topic_id: 26632 reply_id: 108351[/import]
So far there is no known issues with build 819 or higher. That said, several things can cause parse errors upon installing an APK. One major cause of this error is if the target Android device does not meet the app’s feature requirements such as ARMv7 or meets your build.settings file’s “usesFeatures” or “supportsScreens” requirements. We haven’t changed the default requirements on our end in build 819.
Perhaps the issue is that the APK file that you sent to your tester got corrupted upon transit? Maybe you just need to resend it? [import]uid: 32256 topic_id: 26632 reply_id: 108356[/import]
Joshua Quick: it was not the apk file, i send and test alot of build from my games.
And it was not corrupted before.
When will be a new stable version? [import]uid: 86417 topic_id: 26632 reply_id: 108376[/import]
A stable release will be coming soon… sometime next month. Possibly the first half of the month if all goes well.
So, if you can provide any other clues of what you might think have caused the parse error, then that would be a big help. The sooner the better. Since you are the only person to mention this issue, it doesn’t sound like an issue with build 819… so far. But I’m willing to listen. Thanks. [import]uid: 32256 topic_id: 26632 reply_id: 108391[/import]