I setup Google Analytics for my Android app. When I test it with the Android Studio emulator everything works fine and I can see the events in real time on the Google Analytics web console.
If I put the app on my phone (debug or signed with keystore) and I watch the log I can see that the hit are created and sent just fine but I can't see them on the web console. I tried to wait 2-3 days and I tried to submit the app to see if other users' devices would work but the only results I see are the ones from my local emulator and the ones from Google's pre-launch reports (so emulators again).
The same thing happens when I try with the sample app available on the developer guide (Here), so it's definitely not my code. What am I missing?
Related
We have had our app published to Play Store for a very long time. but recently we got this issue in Android 12.
Image showing Google Play Console
There are two types of APK in Play Console
Original File
Distribution APK
this problem is happening in the distribution app
I checked the logcat with adb but it's only showing WINDEATH and there is no other crash
I have checked all over Google and StackOverflow but there is no such question asked that I came across
After opening the app it's showing it like this
App Crash Screenshot
Also, we are using Firebase but there is nothing captured related to this
Use a crash reporting service such as Firebase
or Sentry.io.
These will help you log the crash, get some data about when it happened, why it happened etc. Flutter apps are not meant to crash, so check out your interactions with 3rd party plugins that are initiated on app start. Also, check your signing keys, maybe there is a mismatch between the debug ones and the production ones.
Good luck!
I recently uploaded an app bundle to Internal App Sharing, and was surprised to see that on my backend, there were 7 new users of this new app version just a few seconds later. I was especially surprised because I am the only person with access to the app on Internal App Sharing, and I hadn't even installed the update yet.
So I guess Google is running something similar to pre-launch testing when uploading to Internal App Sharing. This is annoying, because it fills up my servers user table with irrelevant noise.
Can I detect these devices reliably somehow? I tried detecting the presence of firebase.test.lab in Settings.System, as suggested in this answer, but it didn't work.
As a developer och you can disable tests-reports in Google Play Console. Pre-launch tests, config (or something, I get the UI in Swedish so I currently don't see the English names of them.)
NOTE: I have not tested myself (as I want the testing) and I think they will still do some tests when you want to launch things.
I have implemented a SafetyNet attest check when launching the app. It works fine when I run the release version from Android studio and detects (for eg.) the emulator from the device correctly. However when I download the same version from the Play store, it fires the failure listener every time, on a lot of legit devices.
It is a restricted API and works fine when run locally on those same devices.
If you check the image, the 33.75% error rate is when I have used this from the play store.
Any idea what could be happening different with the same code when running in app downloaded from the Play store?
Found my issue!
For anyone using 'App signing by Google Play', make sure you add the SHA-1 provided by Google Play to the API restrictions in the API Console.
You should find this in 'App Signing' in the app on the Play Developer Console.
I integrated pushwoosh functionality inside my android app. I tested it, installing apk from eclipse, and was able to receive notifications, everything was fine. But, after uploading apk to google play and after many downloads, subscribers in pushwoosh control panel is still 1 after 24h (the same one since when I installed the app from eclipse).
I copied paste code from official guide, and added a little function to check if com.google.android.gsk is installed, just to let emulator run the app without crash but again, it was working in a real device when installing apk directly from my pc.
Is there something to set up to let pushwoosh work from googleplay? Or maybe some known issue I'm missing?
I don't think the problem is due to pushwoosh control panel updating latency, since the one subscriber (me) was counted just after installation, and now 24h are passed.
I recently made an update to an existing (paid) app I have had published on Google Play for a while. While I was working on the new version, I thought I'd implement the Google Licensing Verification Library. I followed the instructions from Google at http://developer.android.com/guide/market/licensing/adding-licensing.html . Had things working pretty well at this point - when I changed the test response in the Google Play Developer Console I got a different result in my app. Great!
Then I published this new version.
I installed the signed APK (it's a paid app so I didn't want to download it from Google Play) on my phone (had been testing it on that very same device all along). Now things didn't work at all. I got the "Retry" result from the licensing service all the time. I mean for hours. I went back and fiddled with the source code, changed all kinds of things, nothing worked. The Licensing library always timed out (got a "Check timed out." in from the library in LogCat).
I searched everywhere for an answer, but it wasn't until I ran across this discussion ( http://forum.xda-developers.com/showthread.php?t=1566770 ) and read it to it's very final post that I found the solution.
From the above mentioned post:
"I have just had this issue too & deleting the Google Play Application
data (Settings, Applications, choose Google Play & press Clear Data )
fixed it for me. Clearing Cache is not sufficient. Ihe only impact I
saw of doing this (apart from my App now working again) is that you
have to re-accept Google Play T&C etc when you next use that app and
my search history had gone."
I did it, it worked, and now everything is back to working!
I had the same issue with an app downloaded from google Play Store. In my case the problem was not the storage or cache as in the other answer. I had the Google Play Store Background-Data-Usage restricted, which prevented this API from working. After enabling background data usage, everything worked just fine.