React-native: Android Kit Kat version 4.4.4 Crashes on App Launch

Created on 20 Apr 2017  路  4Comments  路  Source: facebook/react-native

Description

react-native run-android or installing a official release .apk crashes when the app loads. It does work for android version 5.0 and greater

Errors are below

Could not run adb reverse: Command failed: /usr/local/opt/android-sdk/platform-tools/adb -s TA431097MJ reverse tcp:8081 tcp:8081

Unable to install /Users/username/stardust-app/android/app/build/outputs/apk/app-release.apk
com.android.ddmlib.InstallException: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES

Additional Information

  • React Native version: 0.42
  • Platform: Android 4.4.4 (KitKat)
  • Development Operating System:
  • Dev tools: Android sdk 23
Locked

Most helpful comment

Adb is not supported by versions of android < 5. # SOLUTION:## with your app open press on the button menu of your device, dev settings, Debug server host & port for device, enter the ip of your pc and port 8081 ex: 192.168.1.1:8081

All 4 comments

maybe you are using touchableNativeFeedback with ripple effect that will crash your app under android 5.0

Adb is not supported by versions of android < 5. # SOLUTION:## with your app open press on the button menu of your device, dev settings, Debug server host & port for device, enter the ip of your pc and port 8081 ex: 192.168.1.1:8081

The error info is very clear, this is not crash. The log indicate apk install is failed. It's likely that the phone has previously installed the same app, but the signature is different. You can resolve this by simply uninstall the old app.

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

Was this page helpful?
0 / 5 - 0 ratings