Failure [INSTALL PARSE FAILED MANIFEST MAL FORMED]

Solar2D Android
#21

With pleasure. This is the log console:

Using java version "10.0.2" 2018-07-17 Java(TM) SE Runtime Environment 18.3 (build 10.0.2+13) Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode) Using java version "10.0.2" 2018-07-17 Java(TM) SE Runtime Environment 18.3 (build 10.0.2+13) Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode) Building Android app for solon.corona@phonemas.com with 2018.3378 Using custom build id from app bundle: 00000 (AppSettings.lua) Excluding specified files from build: excluding: LaunchScreen.storyboardc excluding: Icon.png excluding: Icon-\*dpi.png excluding: Images.xcassets BUILD SUCCESSFUL Total time: 2 seconds BuildID: 5bac0cbec573a [echo] "creating unsigned.apk" BUILD SUCCESSFUL Total time: 19 seconds Android build succeeded in 76 seconds Error running /Applications/Corona-3378/Corona Simulator.app/Contents/Resources/android\_sendapp.sh ( "-r", "/Users/scaceresm/Documents/Corona Builds/Risk Hunter.apk" ) adb I 3546 93229 usb\_osx.cpp:259] Found vid=22b8 pid=2e76 serial=TA0930IJ75 adb I 3546 93229 usb\_osx.cpp:259] Installing and running Risk Hunter on MotoE2(4G-LTE) 3298 KB/s (13823093 bytes in 4.092s) ERROR: pkg: /data/local/tmp/CoronaSDK971a94d381da784fb18fbb85a1917224.apk Failure [INSTALL\_PARSE\_FAILED\_MANIFEST\_MALFORMED] Error found during installation!

And the window build say:

Device Installation Problem adb encountered an error installing the app: adb I 3546 93229 usb\_osx.cpp:259] Found vid=22b8 pid=2e76 serial=TA0930IJ75 adb I 3546 93229 usb\_osx.cpp:259] Installing and running Risk Hunter on MotoE2(4G-LTE) 3298 KB/s (13823093 bytes in 4.092s) ERROR: pkg: /data/local/tmp/CoronaSDK971a94d381da784fb18fbb85a1917224.apk Failure [INSTALLPARSEFAILEDMANIFESTMALFORMED] Error found during installation!
#22

Can you try again and make the apk name shorter?

#23

Yes, I shortened the name. I have eliminated the uppercase letters. The result is the same.

The funny thing is that this morning (8am COT) compiled well.

#24

I upgrade to Corona sdk 2018.3381, same result. Fail.

regards

Solón

#25

Can you post your build.settings and a screenshot of your build dialog before you hit the build button? Please do not blur out any of the fields.

Thanks

Rob

#26

build.settings

-- -- For more information on build.settings, see the Project Build Settings guide at: -- https://docs.coronalabs.com/guide/distribution/buildSettings -- settings = { -- corona\_sdk\_simulator\_path = "/Applications/Corona-3238/Corona Simulator.app", -- Usando suspensión del splash de Corona splashScreen = { enable = false }, orientation = { -- Supported values for orientation: -- portrait, portraitUpsideDown, landscapeLeft, landscapeRight default = "portrait", supported = { "portrait", }, }, -- -- Android section -- android = { largeHeap = true, -- más RAM para corregir el java.lang.OutOfMemory -- hardwareAccelerated = true, -- para corregir el java.lang.OutOfMemory quizá sea false -\> WARNING: unrecognized key -- coronaWindowMovesWhenKeyboardAppears = true, usesPermissions = { "android.permission.INTERNET", "android.permission.RECEIVE\_BOOT\_COMPLETED", -- Para que las notificaciones permanezcan si hay un reboot -- Camera "android.permission.CAMERA", "android.permission.WRITE\_EXTERNAL\_STORAGE", -- GPS -- Permission to retrieve current location from the GPS "android.permission.ACCESS\_FINE\_LOCATION", -- Permission to retrieve current location from WiFi or cellular service "android.permission.ACCESS\_COARSE\_LOCATION", }, usesFeatures = { { name = "android.hardware.camera", required = true }, { name = "android.hardware.camera.front", required = false }, { name="android.hardware.location", required=false }, { name="android.hardware.location.gps", required=false }, }, }, -- -- iOS section -- iphone = { xcassets = "Images.xcassets", plist = { UIStatusBarHidden = false, --UIPrerenderedIcon = true, -- set to false for "shine" overlay NSCameraUsageDescription = "You must grant permission to access the camera or otherwise you can not report risks in this system", NSPhotoLibraryUsageDescription = "You must grant permissions to access the image or photos library of this device. Otherwise you will have limited functionality in this system..", UILaunchStoryboardName = "LaunchScreen", CoronaWindowMovesWhenKeyboardAppears = true, CFBundleVersion = "ALPHA 8.59", -- Versión para IOS --UIApplicationExitsOnSuspend = true, -- uncomment to quit app on suspend ITSAppUsesNonExemptEncryption = false, -- This sample doesn't use custom encryption (OJO!!!) --UIRequiredDeviceCapabilities = {"location-services", "gps", "magnetometer" }, --UIRequiredDeviceCapabilities = {"location-services", "gps" }, NSLocationWhenInUseUsageDescription = "You must grant permissions to access the location (GPS) of this device. Otherwise you will have limited functionality in this system.", }, }, -- -- Plugins section -- plugins = { ['plugin.toast'] = {publisherId = 'com.spiralcodestudio'}, ["plugin.notifications.v2"] = { publisherId = "com.coronalabs" }, ["plugin.chatterbox"] = { publisherId = "com.develephant" }, ["plugin.OneSignal"] = {publisherId = "com.onesignal"}, ["plugin.nanosvg"] = { publisherId = "com.coronalabs"}, ["plugin.imageCrop"] = { publisherId = "tech.scotth", }, }, -- -- Project section -- excludeFiles = { -- Exclude unnecessary files for each platform all = { "Icon.png", "Icon-\*dpi.png", "Images.xcassets", }, android = { "LaunchScreen.storyboardc", }, }, }

screenshot before [build]:

ScreenShot2018-09-26at7.09.31PM.png

#27

I’ve never seen anyone use a “Version Name” that wasn’t numeric, like 1.0 or 3.5. It does say “Name”, so perhaps it’s valid, but it might be worth trying.

Secondly make sure your “Safe to Folder” is not the same folder as the “Project Path”.

I saw a complaint about Package names and mixed case, like Com.Yourname.yourProject causing problems, but I know that com.yourname.YourProject is fie, so your Package Name seems to be okay.

I don’t see any keys in build.settings that would cause issues.

Rob 

#28

Having the same issue but noticed solca is also using the One Signal plugin. Removing that lets me at least build and install the apk without the parse error

Was the One Signal plugin updated recently?

#29

It is correct !!.  Thank you very much for your response.

I commented on the OneSIgnal plugin line in the build.settings and the build is generated.

(but the app is without the push functionality of One Signal) :frowning:

Question:

Any update of the build server could be affecting the build process ?

Regards,

Solón

#30

OneSignal was updated today.

I’ll share this thread with the developer.

Rob

#31

Thanks Rob.

we will be awaiting the response of the developer.

Regards,

Solón

#32

Hello @solca, OneSignal made a recent Android SDK update for Android Oreo compatibility. We also changed the package name of our classes which for Android from “com.onesignal” to “OneSignal” which cased the INSTALL_PARSE_FAILED_MANIFEST_MALFORMED on older Android devices. We were able to reproduce the issue on an Android 4.4 device but this changed worked fine on Android 8.0.

We just pushed a new updated to put our package name back to “com.onesignal” which will fix this issue. I believe it will take a few hours to get synced to Corona’s build server before you will see the update take effect.

#33

Right now I’m getting a “module ‘OneSignal’ not found” error with every build made with a OneSignal plugin (on android 7, can’t test 8 currently). Is that still because the onesignal plugin has not been synced to Corona’s build server? Thanks

#34

Sorry for the issue, it was due to a bad update. We have push an update and it should be available in the next few hours.

https://forums.coronalabs.com/topic/72988-onesignal-with-targetsdkversion26-getting-error-background-start-not-allowed-service-intent-cmpcomonesignalgcmintentservicehas-extras/?p=389433

#35

Solved!!

Thanks a lot

Solón Cáceres