[Android] App crash at launch after upgrading to 0.46.3

[valinaga]

Is this a bug report?

Yes.

Have you read the Bugs section of the Contributing to React Native Guide?

Yes.

Environment

Android

1. react-native -v: 0.46.3
2. node -v: 7.7.2
3. npm -v: 5.0.4
4. yarn --version (if you use Yarn): 0.23.4

Then, specify:

• Target Platform: Android

• Development Operating System: macOS

• Build tools: 23.0.1

Steps to Reproduce

(Write your steps here:)

1. react-native-git-upgrade
2. react-native run-android

Expected Behavior

App to launch in emulator

Actual Behavior

App crash at the beginning without opening the window.

Reproducible Demo

07-18 06:36:40.655 4782-4801/com.appcenter.wishbox E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #2
Process: com.appcenter.wishbox, PID: 4782
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.NoClassDefFoundError: com.facebook.react.devsupport.InspectorPackagerConnection$Connection
at com.facebook.react.devsupport.InspectorPackagerConnection.(InspectorPackagerConnection.java:36)
at com.facebook.react.devsupport.DevServerHelper$3.doInBackground(DevServerHelper.java:194)
at com.facebook.react.devsupport.DevServerHelper$3.doInBackground(DevServerHelper.java:191)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) 
at java.lang.Thread.run(Thread.java:818) 

(Paste the link to an example project and exact instructions to reproduce the issue.)

[Jose4gg]

Same Problem @valinaga any updates?

[dorthwein]

Same here ;(

[pull-bot]

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.

[fxhereng]

Setting Overlay permissions in app settings enabled to solve it for me (RN 0.49.3)