Develop Reference

React native android apk installation error

I install my create signed apk in some other device, it gets installed once only. After I uninstall it and install again the same apk, then it shows error 'app not installed'.
Also, the user login work only on localhost but not on development server/apk.
I have tried cleaning the gradlew every time and regenerating new apk, but nothing works.
Kindly help to resolve the issue.

Installation fails if you try the same file if it is not an app added to Google Store in Android
The first option is to re-install the APK with the same code under a different name,
or
Your device is protected from harmful apps with Google Play Protection. This is why you must release the check.
Open the Google Play Store app Google Play on your Android device.
Next to Menu, Play Protect tab the following settings:
Disables the scanning feature for security threats on the device.

You should use your computer's ip address instead of using 10.0.2.2 if you are running on local device. PS: the codes are still running native in the end. There is a better explanation here. [explained][1]Android Localhost?
About the installation failing, I have not experienced. But maybe it's was already published in Google Play as hong described?

GoogleSignInClient connects only when app's installed from Google Store

I am developing an Android game and currently trying to integrate with Google Play Game Services. I got stuck at the sign-on feature.
I use GoogleSignIn, getIntent, startActivityForResult etc. - all as described in Google manual. I think all's setup correctly, because when I build the app, deploy to Google Store (Internal Tests), and then I install it from there, all looks good: onActivityResult is called with result.isSuccess()==true and GoogleSignIn.getLastSignedInAccount returns != null.
The problem is when I try to run the app from Android Studio (or install APK manually). In this case, onActivityResult is called with SIGN_IN_REQUIRED and getLastSignedInAccount is always null. I am pretty sure all's setup fine (APK is signed, Android Studio is configured to sign the APKs etc.).
To ensure it's not about my Android Studio setup, I have installed manually exactly the same APK which I uploaded to Google Store but again - result is the same. When installed from Google Store, it's OK, when installed manually it's not (again: exactly the same APK binary).
Can you please help me? Theoretically I could continue development, but each I'd like to test something I'd need to upload new version to Google Store...
Thank you

Hmmm...its usual DEVELOPER ERROR, what you can do it..add your SHA1 code on firebase console, and it will work, it is showing this behaviour caus your signed key SHA1 is already added, that why it is working on release build and not on debug build, add your systems SHA1
How to get SHA1?
usually right side of android studio have a bar which says gradle click on it, expand it got to app>Tasks>android>signing report double click it...it will give you your SHA1, paste it on firebase console, wait for 1-2 minutes and check. It will work.

How do I view Android LogCat output from an exported APK running on a physical device?

When I run my Android app using the Run -> Run menu option in Eclipse, the app launches on my phone and while it's running I'm able to view the log output in LogCat within Eclipse.
When I export my app, copy the .APK onto the phone, install it from the APK, and run the installed app, I don't see any output in LogCat.
Is there a way to view that log output?
Context:
I'm in the process of implementing in-app purchases. I think I have it working, and when I try using the in-app purchases from within the app if it's being launched on the phone via Eclipse's Run menu, it activates the Google Play store but I get an error that says "This version of the application is not configured for billing through Google Play".
After some googling I found that this error gets thrown because the APK needs to have a signature that matches the APK I've uploaded to the developer console in order for the in-app billing to work, and running from Eclipse's Run menu doesn't provide that signature.
So I've tried installing the signed APK that matches the one I've uploaded to the developer console and now when I try to use the in-app billing from within the app, nothing happens at all. It doesn't seem to even try to launch the Google Play store like it does when run through Eclipse's Run menu.
So basically I need to see what kind of error messages it's outputting when I try to use the in-app billing specifically from the exported, signed APK.

Try adb logcat from the console or cmd, which will give you all the logs of the device.
Here's a small tutorial: http://forum.xda-developers.com/showthread.php?t=1726238
and official docs: http://developer.android.com/tools/help/logcat.html
If your device is rooted, you can also try this one: https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

Install the app https://play.google.com/store/apps/details?id=org.jtb.alogcat to view the log directly in your phone.
Use adb logcat
Use DDMS and click on your app thread.

It's a common practice that exported app should not contain any log statements.
Try downloading the app manually from google play store to ensure that the in-app billing is working perfectly.
And also to check what error messages are displayed on screen

Re-installation failed (YES) Package already exists

So, I have an app which I am running on real device. When running the app the following dialog is shown.
Clicking Yes is followed by error in Console
- google-play-services_lib] Installation error! The package already exists.
- Launch failed on device:
I have tried uninstalling app from my phone but didn't work.
Any idea how to fix it?

You dont need to reinstall google-play-services. It's updating automatically by Play Market.
I had problems like yours and let me guess:
when you debuging app from eclipse - google play services doesnt sign in, but when u release it and download from play market - it works fine.
If its true, so mark your google-services as a library and delete from "java build path" in your app.
right click on project-> Properties -> Java Build Path -> Projects
Delete google-play-services from there
Now, you have to obtain debug certificate SHA1
in Eclipse go to Window->Preferences
Andoid->Build
(there you can find debug certificate SHA1 for debuging)
Go to Android Developper Console https://play.google.com/apps/publish
Select your game in Play service
Go to "linked applications"
Create a NEW linked application android and put it your debug certificate SHA1
Wait a few to changes be deployed
You will get two similar links, but with different SHA1 ( one for debugging, second for releasing)
Now, you need to clear the Android Application cache before trying to connect
Clear cache of your application
Launch your app
I solved my problem like this

That's caused by attempting to install an apk maybe from the ide with debug keystore on a device that has the production apk with the production keystore. Just go into the phones app settings and uninstall the app. I get a few of these after I test the upgrade path from the beta store and then go back to developing with the ide.

try doing it through command prompt use:
adb uninstall PACKAGE_NAME
and see if it works
also try renaming the package name just to be sure.
I feel you are trying to install google-play-services.You don't need to update google play services.From the docs:
The Google Play services APK
The Google Play services APK contains the individual Google services
and runs as a background service in the Android OS. You interact with
the background service through the client library and the service
carries out the actions on your behalf. An easy-to-use authorization
flow is also provided to gain access to the each Google service, which
provides consistency for both you and your users.
The Google Play services APK is delivered through the Google Play
Store, so updates to the services are not dependent on carrier or OEM
system image updates. In general, devices running Android 2.3
(Gingerbread) or later and have the Google Play Store app installed
receive updates within a few days. This allows you to use the newest
APIs in Google Play services and reach most of the devices in the
Android ecosystem (devices older than Android 2.3 or devices without
the Google Play Store app are not supporte

Android In-app Billing Error Message

I was having problems earlier implementing in-app billing for android. I have fixed that issue, but following that is another issue. When I run the application on my phone and another test account phone, I get the error: "This version of the application is not configured for Market billing." I have installed the new version of the app to the Android market as an APK and added the items. When it opens the in-app billing, it shows the name of the item to purchase from the Android market, but gives me the error. When I tried the static example from Google, that worked.
Thanks

To get this to work you need to sign the package with your release key/certificate, upload to the Market and save it (without activating). Then install the release APK to your device to be able to test. The APK you install on the phone has to have the same version and be signed with the same certificate for IAB testing to work. Details here.