Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Find Installed React Native Android App On Phone and Emulator #19928

Closed
thecodecafe opened this issue Jun 27, 2018 · 11 comments
Closed

Can't Find Installed React Native Android App On Phone and Emulator #19928

thecodecafe opened this issue Jun 27, 2018 · 11 comments
Labels
Platform: Android Android applications. Ran Commands One of our bots successfully processed a command. Resolution: For Stack Overflow A question for Stack Overflow. Applying this label will cause issue to be closed. Resolution: Locked This issue was locked by the bot.

Comments

@thecodecafe
Copy link

thecodecafe commented Jun 27, 2018

So something strange happened, when developing I noticed that my react-native app compiled but wasn't visible (not found on the apps list/tray) on my emulator although the react-native run-android launches it (both debug and release) but when I go to Settings > Apps I can see the app listed there, I thought this was some new thing to react for dev environments, but I noticed that after compiling my app as release I can't find it on the phone until I go to Settings > Apps and even from there I can't launch.

Another thing I first noticed was, that the first time I compile the release, while trying to install a notice appeared on my screen saying, Google play connect rejected my app, and at first I couldn't install the app, but after rerunning the compilation I was able to, but now the app can't be launched.

I have generated a signed apk and have set it up in android > app > build.gradle

Please find below my environment's information.
Environment:
OS: macOS High Sierra 10.13.5
Node: 8.11.3
Yarn: 1.7.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: 3.1 AI-173.4819257

Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4

@thecodecafe thecodecafe changed the title Can't Find Installed React Native App On Phone and Emulator Jun 27, 2018
@react-native-bot
Copy link
Collaborator

It looks like your issue may be missing some necessary information. Can you run react-native info and edit your issue to include these results under the Environment section?

@thecodecafe
Copy link
Author

@react-native-bot have made the modifications.

@hramos hramos added the Resolution: For Stack Overflow A question for Stack Overflow. Applying this label will cause issue to be closed. label Jul 2, 2018
@react-native-bot react-native-bot added the Ran Commands One of our bots successfully processed a command. label Jul 2, 2018
@react-native-bot
Copy link
Collaborator

Please use Stack Overflow for this type of question.

@abtuleshov
Copy link

the same issue, @thecodecafe did you solve this?

@thecodecafe
Copy link
Author

@abtuleshov I couldn't, I simply started a new react-native project, copied my source files and reinstalled my dependencies.

@verybluebot
Copy link

having the same issue, its not a SO question.. app is installed and opens after using react-native run-android but no app icon.
the app is in Installed Apps and its possible to removed. This started happening after deleting the app a couple of times.
@thecodecafe not a solution for me, its a production app :/

@geralddevelop
Copy link

I had this problem and the issue is that i put <data android:scheme="@string/facebook_app_id" /> inside the same intent-filter as action and category.

Just take data out and put it in another intent-filter like:

<intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
            <intent-filter>
                <data android:scheme="@string/facebook_app_id" />
            </intent-filter>

Thats solve the problem for me :)

@kkusanagi
Copy link

@geraldheng Thanks. You are such a savior, you had save my half year problem.

I'm actually have a same problem after doing a setup for Firebase Dynamic Link.
Here is my version of AndroidManifest.xml after fix.

<activity
        android:name=".MainActivity"
        android:label="@string/app_name"
        android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
        android:windowSoftInputMode="adjustResize"
        android:launchMode="singleTop">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
            <action android:name="android.intent.action.DOWNLOAD_COMPLETE"/>
        </intent-filter>
        <intent-filter android:autoVerify="true">
            <action android:name="android.intent.action.VIEW"/>
            <category android:name="android.intent.category.DEFAULT"/>
            <category android:name="android.intent.category.BROWSABLE"/>
            <data android:host="example.page.link" android:scheme="http"/>
            <data android:host="example.page.link" android:scheme="https"/>
        </intent-filter>
</activity>
@dimgrav
Copy link

dimgrav commented May 31, 2019

@geraldheng huge thanks!

@christiangarciareyes
Copy link

Eres grande GeraldHeng Gracias!!!!

@ElixirMike
Copy link

I don't think it would be possible to write react-native apps without folks like you and others sharing these tips. THANK YOU!!

@facebook facebook locked as resolved and limited conversation to collaborators Jul 2, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Platform: Android Android applications. Ran Commands One of our bots successfully processed a command. Resolution: For Stack Overflow A question for Stack Overflow. Applying this label will cause issue to be closed. Resolution: Locked This issue was locked by the bot.
10 participants