My Android app uses Firebase Authentication(Gmail+phone). When I see the new users signed in to Firebase authentication and compare it with Google Play Console 'new User acquisition' then Play console always shows less number than Firebase shows(with registered Gmail or phone number). What is the issue here?
Google Play uses robots to test and review your app. These robots do not show in the Google Play Console but show in Firebase. That is why you see more users in Firebase than Google Play Console.
Related
I have an Expo app that uses react-native-maps. It works well on Expo Go and I would like to deploy it to Google Play Store.
According to Expo documentation, I have to:
deploy the app on Google Play Store to generate app signing credential
copy the SHA-1 certificate fingerprint in Google Play console
create an API key in Google Cloud Credential manager
paste the API key in app.json
rebuild the app and re-submit to Google Play Store
So, to my understanding, the app will be available for users without maps activated. Then I'll have to deploy it again with maps activated. It sounds very counter-intuitive, and puts me at risk to get bad reviews from first users, who will claim the app "doesn't work" (because there is no map of course)
Is there a way to immediately publish a working app? If I need to handle a two step process, will the second build be immediately available in the Play Store, or will it be subject to a 3 days review?
I am trying to integrate firebase analytics on react native app, I have completed all the prerequisites and got a successful build running on Honeywell android Device, but when I open the app it gives above error. There are many such duplicate question but nothing works for me as I can't have play store as the target devices are Handheld android devices and not mobile devices. How to integrate firebase analytics without having to install google play service.
Thanks for Answer #JakeSteam
But I could get firebase integration working without google play service error.
Issue Details:
I was using react native firebase 5.x.x, which works fine but will give a pop up message mentioned in question if your device doesn't have google play service.
Workaround:
Upgrade react native firebase to version 6.x.x, the community has redeveloped this repo and I am not having issues with it now.
NOTE:
Without google play service on your device you can only use few firebase services like analytics, crashlytics etc.
As a Firebaser said:
Firebase as a platform requires Google Play Services, even though some Firebase products may be able to work without it.
If you cannot use Google Play Services, you may want to look into Google Analytics, which does not require it:
Note: Google Analytics can be used and will work on devices that do not have Google Play Services. In this case you still download and use the Google Play Services SDK and Google Analytics will automatically fall back to local dispatching.
I managed to get the code runing to a point where i can upload and download files in my android app from google drive using the api. However i uploaded my app to Google Play and when a user installs it the first time the oauth 2 screen pops up and requires to select account(which is great) but when the user selects Google account the oauth screen just keep appearing and looping.
Did anyone encounter this before?
As stated in this thread, maybe you did not create credentials for your app. As described in this documentation, you must retrieve your SHA-1 keys for both the debug and production environments and add them in your credentials in the Google Developers Console.
I cloned q-municate, went through the q-municate tutorial for Android, build with Android Studio, installed on 2 test devices, logged in both with Facebook (had to setup 2nd user as tester in Facebook dev).
I can't find the other user (in my own app). Quickblox dashboard shows users.
To research Quickblox, I initially downloaded original "q-municate" app from the Google playstore. I installed it on 2 phones, and logged in with phone (twitter digits) and Facebook. It was hard finding someone there too. But once connected, I was able to send messages back and forth. It didn't work great, but I'm guessing with the free tier that Quickblox has for their sample app, there is a limit to msgs and notifications.
I am trying to find the up to date instructions for creating a google android app credentials does not match the google developer console.
https://developers.google.com/youtube/android/player/register
there is no APIs & auth on the sidebar anymore:
In the sidebar on the left, expand APIs & auth. Next, click APIs. In the list of APIs, make sure the status is ON for the YouTube Data API v3.
Please advise.
-Tony
Ok, I figured it out. I was trying to do it from the Google Play Console rather than from the Google Developer Console. But I first needed to tie my Google Play Console to the Google Developer Console using my settings in my Google Play Console.
-Tony