React-native release apk refuses to install - android

I have encounter a problem I am unable to solve, I have followed all steps from:
Unable to install signed apk from React Native but the ones in Android Studio since I am not using it and the steps needed to sign the apk from https://facebook.github.io/react-native/docs/signed-apk-android, I still get the error:
There was a problem parsing the package
In logcat I get the error:
05-23 09:44:23.964 3613 3613 W PackageInstaller: Parse error when parsing manifest. Discontinuing installation
This error make me thing the error cannot be with signature but there is no manifest file, I searched for it and debug build works.
It only happens with release builds. I hope some of you can help me since I am lost.

I have recreated the project and repeated the steps, that solved the problem.

Related

React Native: Generate Signed APK: Errors while building APK

I have just completed my 1st react native project and now I am trying to generate its APK file by generating a signed APK using Android Studio but I am getting an error and I don't know why I am getting this.
The Gradle build starts running and after that in event log I get an error:
Generate Signed APK: Errors while building APK. You can find the errors in the 'Messages' view.
In the message view the error that I get is:
Type io.invertase.firebase.BuildConfig is defined multiple times: F:\Salvador\node_modules#react-native-firebase\app\android\build.transforms\201acb16e5bf3be0b3bc4a9933889ad1\classes\classes.dex, F:\Salvador\node_modules\react-native-firebase\android\build.transforms\9affd011dae86c883f20504c5a21ffef\classes\classes.dex
This is a problem I have been solving in my projects last days. And I think I have some good (not perfect) solution so far.
Implementation in android/app/build.gradle
def enableSeparateBuildPerCPUArchitecture = false

Import error while uploading app bundle to Play Console

I have refactored my app by splitting into modules (:app, core and features). It works correctly on emulator so I decided to upload to the internal test track on Play Console but it shows an error during importation :
The screencap is in french but it says basically "An error occurred during importation of Android App Bundle package. Please try again later. If the problem persists, contact Google Play assistance service for developers"
This message doesn't give any clue about what the problem is !
The previous uploaded version of this app was already an App Bundle and is currently released successfully.
The big difference between both versions is that the new one is split into modules (but no dynamic features or anything). I have added android:hasCode=true to :app module manifest.
I have retried after invalidate, restart, clean, rebuild and regenerate bundle. I have retried on another day.
I have downgraded from Android Studio 3.4 to 3.3.2 (and Gradle as well) to be sure that R8 is disabled.
No luck... Any idea ?
After many tries, it occurred to me that maybe I would get a more explicit message by uploading an APK instead of a Bundle.
And I did !
Failed to run aapt dump badging:
AndroidManifest.xml:63: error: ERROR getting 'android:name' attribute: attribute is not a string value
Because I had an #string for a intent name instead of an hardcoded string (-shame-)
Anyway, to be remembered : When Bundle importation doesn't work, try uploading a simple APK to get a more explicit error message !

Android studio How to resolve Error in png files of library added

I have no Idea what is happening, last time when I finished my app I build its release apk and all was working just fine as expected but now today when I tried to make that pproject again and to make another apk I am getting the following error.
Error:Execution failed for task ':app:mergeDebugResources'.
Crunching Cruncher common_signin_btn_icon_pressed_light.9.png failed, see logs
I have no idea how to resolve it I have serached and found restarting Android studio and clean the project would remove it , doing this many times has no effect on this error. I have even restarted my machine but the condition of error in same.
In the logs I have seen that this png file is from the library I added , so just for testing I removed that library and tried to build then it started to give me same error with different png file name in other library. So how to fix this issue ?
My Questions are :
How can this issue be Solved ?
Have some one faced this problem too ?
Is this problem has been reported to google ?
Why in android we do not have any stable platform for development as IOS have ?
Try to remove "builds" folders and do rebuild. But soon, the whole thing in a long file name. Read this answer. By the way, you looked logs? Maybe this is not the PNG? You have not sent the log and did not specify the version Gradle.
Believe me, iOS developers have own problems.

Android: Class Not Found runtime exception - release build only

We have an app that has had several version on Google Play and has been working fine. The latest updated causes a runtime error "Class not found" for our main activity. The activity is called 'Home'.
The runtime error does NOT occur on a debug build, only as release build.
The activity has not changed for several updates, but suddenly has started raising these runtime errors on start-up.
Cheers,
Peter
Try do a clean on your project and export of ECLIPSE
This way: project > android tools > export as signed application package.

Phonegap - Hello Cordova error

I followed the first tutorial of Phonegap - getting started with Android. I wrote the example "HelloCordova" as showed here. But when I click "run as Android application" Eclipse displays your project contains error(s), please fix them before running your applications. No error is pointed! I can't understand where's the problem (my file matches the example)!
Problems:
Error generating final archive: Debug Certificate expired on 07/04/12 0.34
Location: Unknown
Type: Android Packaging Problem
Any advice? Thanks!
This problem is not related with Phonegap ...
You should delete the debug file at "%USERPROFILE%/.android/debug.keystore", so then eclipse will gerenate a new debug file
Check the android manifest file for any errors. Even the manifest file must be free of errors. You may have overlooked it as it is the last third file. Check with that for errors.

Categories

Resources