there was a problem parsing the package-no solutions ?

[sphere]

Hello,

searching the forum and google there are a lot issues about the---- there was a problem parsing the package---- but no working solutions unfortunately.

Does anybody know what the main reason is this is happening? it happens on emulator and on real devices.

Is'nt android backwards compatible?

Having some builds installed, which build is actually used to create the apk? the one you say as minimum in the Standalone settings?

I use the LC 7.0.1 RC2, JDK 8 update 25, android SDK builds 17 till 21, SDK Platform 4.4.2 (ApI19), 4.1.2(API16), 2.3.3 (API10), 2.2 (API8), Support Library 21.0.2

Does the builds have to match the SDK Platform ?

Yes i have followed the lessons, but still these questions are bugging me.

***edit*** Catlog on my Galaxy S2 gives 2 faults
- Parse error when parsing manifest. Discontinuing installion
and
- blabla.apk (at Binary XML file line #2): <manifest> specifies bad package name "blablabla": must at least have one '.' separator

There is nothing changed to the Livecode manifest in the Android folder under LC installation.


Thanks for any help on this .

[Ray@LinkIt.Com]

I'm working on Windows 8.1 using Livecode 7.0.2(rc2) and I've discovered that if I set the Standalone Application settings to the following I get rid of the "parsing" error:
Signing: Sign for Development Only
Minimum Android version: 3.1
Install Location: Internal Storage Only
Write External Storage: checked
Some of these probably don't matter like the storage options. Give them a try and you should be able to clear this up.

[sphere]

Hi Ray,

this issue was already solved by a newer version of livecode. It was not mentioned here.
Livecode 7.0.5 is the latest stable.

[JustinW42]

I am having this same problem at the moment.... I got past the first steps (generating the key, setting up Livecode to deploy the app to Android, etc) - now I transfer the successful APK file to my device (I simply e-mail it to myself) but when I try to open it I get the "problem parsing the package" ERROR.

Here are my details:

- App Contents: The app is a brand new stack with only one element - a label field.
- Livecode Version: 7.0.6
- Android SDK: r22
- Java Development Kit: 1.8.0 - 45
- Platform: PC running Windows 8
- Android Device: LG G Pad 7.0 running Android 4.4.2

I went into the settings on my tablet and enabled the use of apps from all sources..... This did not help.

Any suggestions?

[sphere]

Hi Justin,

i know it's not caused by lC7.0.6 as i use it too and have no problems at all on Android.
So probably it is the Android SDK which is causing problems. You could try to remove r22 and use r21 see if that helps.

To send an APK to my Android(my usb is only working to charge, no data anymore) i use MyphoneExplorer, it's a 2 piece software, one part on your phone/tablet and the other piece on windows (google for it) then you can just send the APK to any folder you like on your phone via Wifi.

[LCNeil]

Hi Justing,

This could be caused by emailing your APK to your devices. Doing so, in some cases, can corrupt the APK. Further discussions on this can be found here-

http://androidforums.com/threads/parse- ... age.13772/

I would recommend sending your APK to device via other means (e.g. directly via USB or via cloud storage(e.g.dropbox) or directly connecting your phone to your computer and then using the "test target" mode from within LiveCode.

Kind Regards,

Neil Roger
--
LiveCode Support Team ~ http://www.livecode.com
-

[JustinW42]

I downloaded and installed MyPhoneExplorer and transferred the file over WiFi directly to my device, but the same error persists. I guess tomorrow I will uninstall my Android SDK and install r21, to see if that makes a difference.

[sphere]

check this link maybe it will help you setting up Android sdk
https://www.youtube.com/watch?v=83qrKr9bR3M
for this post http://forums.livecode.com/viewtopic.php?f=53&t=22244

there are more posts on this forum concerning the issue you have, but i know it was solved since lc701 or lc702 i believe

[JustinW42]

Ok so I was able to work through this problem by updating my Android SDK to the most recent version...... I opted to go this route instead of downgrading, since the recent fixes in Livecode probably made a difference in the way it interfaced with the Android SDK.

The problem I have now is that I am unable to add an application icon in the Standalone Application Settings, without encountering a Manifest error when I try to build the standalone app..... I will create a new thread for this issue, as I have been searching around and haven't been able to determine the cause of the problem.

[JustinW42]

Ok so I was able to work through this problem by updating my Android SDK to the most recent version...... I opted to go this route instead of downgrading, since the recent fixes in Livecode probably made a difference in the way it interfaced with the Android SDK.

The problem I have now is that I am unable to add an application icon in the Standalone Application Settings, without encountering a Manifest error when I try to build the standalone app..... I will create a new thread for this issue, as I have been searching around and haven't been able to determine the cause of the problem.

[sphere]

So now i run into the same problem here.....

I had to reinstall my windows because something was not working anymore whatever i tried, tried every trick there is.
Finally i had to reinstall and use a backup for my stuff.
I reinstalled livecode, Java sdk and android sdk.

Opened my test livecode file and it said "could not build blablabla classes"
updated and installed some things in the android sdk, but still no luck
then opened a new mainstack and just chose Android in standalone settings.
Now i could create an APK

So there must be something saved in the previous test livecode file that prevents the build.
so have to test some things why this is happening.

edit ****** uuuhhhmm euhhh oooops oh yeah i forgot......the identifier does not like - in the naming......easy to forget.

[jim1001]

I'm working on Windows 8.1 using Livecode 7.0.2(rc2) and I've discovered that if I set the Standalone Application settings to the following I get rid of the "parsing" error:
Signing: Sign for Development Only
Minimum Android version: 3.1
Install Location: Internal Storage Only
Write External Storage: checked
Some of these probably don't matter like the storage options. Give them a try and you should be able to clear this up.

Thanks Ray for your post. I'm on Win 7 with LiveCode 7.1.2 installing onto Samsung Galaxy Tab S2. I was getting the parse error. I found the only one of these I needed was "Sign for development only" (from "Do not sign) - with this it worked . Hope this helps someone.