Unable to build app for testing - manifest ERROR

[abanowBUSTfGf]

When trying to test my app on a tethered Android, I get the error:
"Unable to build app for testing: could not generate package manifest"
Any help would be appreciated. Thanks.

[jacque]

Did you alter the original manifest that ships with LiveCode? If you add or remove lines, that error can happen.

[SimpleLife]

I have the same issue.

I haven't changed the manifest.

Where does it live and what should it's contents be?

[jacque]

It lives in Tools/Runtime/Android/manifest.xml, but if you haven't changed it then it's the one that ships with LiveCode. I think it is probably time to write to support@runrev.com and see if they know what the problem is.

[bertBUSIbr8]

Hi,



I'm running into the same error here: "Unable to build app for testing: could not generate package manifest."

Running Mac OSX 10.7.5, Livecode 6.1.2 RC2 [updated today], Android SDK 22.2.1, Java 7 Update 25.

Haven't touched the manifest, didn't know what or where to be honest.

Any ideas?


Many thanks,


Bert

[LCNeil]

Hi Bert,

Does the manifest issue occur for all applications you try to build?

This error can happen if you have icons assigned in your Android standalone application settings that have become unlinked or are not present anymore.

If you have any icons set the best thing to do is remove these and then trying to build again. If the issue persist, please get back in touch and we will attempt to assist further.

Kind Regards,

Neil Roger

--
RunRev Support Team ~ http://www.runrev.com
--

[bertBUSIbr8]

Hi Neil,


Thanks for responding, was away for a while hence the delay here.

Figured out in the meantime what I'd done wrong.

In the standalone application settings I had put:

Version Name: 0.0.1 and Version Code 0.0.1

As soon as I changed the Version Code to 1, it all worked fine.


Regards,


Bert

[LCNeil]

Hi Bert,

Thanks for letting us know your solution! I'm sure this will be helpful for any other users come across a similar issue

Kind Regards,

Neil Roger
--
RunRev Support Team ~ http://www.runrev.com
-

[paoloriz]

Hi guys,

I have the same issue and the settings above are all correct. I didnt specify any icon.
I am simply trying to build an app with a button in it to see if everythign works fine. I followed all the instructions in the tutorials but I have this manifest error.

Any hint?
Thanks
Paolo

[Elia]

Hi to all,
I have just install all SDK 23.0.5, Java 8 update 25, LC 6.6.5. (windows 7 home basic)
In preferences -> mobile support all is recognized, i have an Android Device installed and selected for test, but i have the same error when I run the test
"Unable to build app for testing: could not generate package manifest"

thanks for help

Elia

[rumplestiltskin]

Didn''t work for me. I installed SDK 5, 4.0.3, and 2.2 using the instructions at the appropriate webpage. I created a VM (which does open a window). But I still get the "manifest error" under LiveCode 7 (Stable release) whether the VM is running or not (and I think this has nothing to do with the problem). I set the version numbers to "1" in the Standalone Settings but no luck. My app consists of nothing more than a small stack with a "Hello World" button.

Assistance will be appreciated. Thanks,
Barry

Hi Neil,


Thanks for responding, was away for a while hence the delay here.

Figured out in the meantime what I'd done wrong.

In the standalone application settings I had put:

Version Name: 0.0.1 and Version Code 0.0.1

As soon as I changed the Version Code to 1, it all worked fine.


Regards,


Bert

[LCNeil]

Hi All,

This seems to be an issue with the latest Android SDK and LiveCode. More specifically, having any SDK build tools installed above revision 20 will result in the manifest error. The current solution to this is to remove any build tools 21 or above.

The following screenshot shows my current working Android SDK manager installation-

Kind Regards,

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

[rumplestiltskin]

Neil,

Thanks. I'm closer but now have a different issue. The error I get now is "Missing APK File". Should I have -nothing- in the way of API 21 items?

I find I have to launch the emuiator first (and I used the Nexus 5 as the basis for my emulator as that is the phone I own so, eventually, I can test it right on the hardware device) in order for it to be listed in the Test Target sub-menu. Once I select "Test", it goes through all the motions (I guess) but ends up with the APK error mentioned above.

Again, advice would be appreciated.

Thanks,
Barry

[rumplestiltskin]

Neil,

I have the same items installed in the Tools section as your picture shows. I did not install Android 5.0.

Barry

[rumplestiltskin]

One more piece of info: The emulator seems to be running just fine—works just like a big, on-screen Android phone—but that "Missing APK File" is the issue. Certainly a less than helpful error message. :/