Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- calsign March 2014
Faulty .apk file - "There is a problem parsing the package"
Hi,
I've programmed simple audio demo skecth for showing audio signal in time and frequency domains. Sketch works perfectly from processing using Android mode and "run on a device". Then I've exported sketch as Android project.
With ADT bundle (Eclipse) I did : - created new project from existing code - made everything according to this info: http://forum.processing.org/one/topic/why-signing-unknown-sources-and-how-to-sign.html and exported signed and unsigned apk files.
But none of them work on my Samsug Tab2 (Android 4.2.2). I get "Parse error: There is a problem parsing the package"
I've checked target and it is API10, have done everything in Eclipse and got no error in return. But both (signed and unsigned don't work - have tried to install them from web page and SD card). I've digged up the apk that is produced when running "on device" from PDE and it works and install normally (but is unsigned).
Any advice what to do or what have I done wrong ? Is there any tool to check produced apk ?
Thanks in advance, regards, Bulek.
Answers
This seems to be a fairly generic error message. There is a list of potential solutions on StackOverflow (but you may have seen this already...).
A possibility stands out: What is the name of your exported APK file? Does it differ from the name of your unsigned APK? If so, try changing it back (or to something else).