My app, when downloaded from Google Play, is showing some errors that I couldn't simulate with eclipse, even debugging directly at the device.
I've posted this issue with more details here: Facebook Connect works different on emulator/device, but not on Google Play
But i want to know if I can debug my app if I downloaded it from Play, i.e., without installing the apk from Eclipse. If not debug, at least could I see the log messages in LogCat?
Thanks!
Yes. It's the same as debugging with the eclipse debug apk. You can see log messages, take screenshots. Not sure about breakpoints, but the rest is the same.
Keep in mind that if you use ProGuard or similar tools, the stacktraces will need to be run through their tool again to make sense.
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!
Deploying a Kivy app to Google Play Store is a true pain. I spent over a week now trying to deploying the app to the Play Store, whereas I spent only 5 days developing it.
After managing to overcome all problems during the build process with buildozer, I'm facing now another problem when I want to deploy my app to google store. This is the warning I'm getting:
Unoptimised APK
Warning:
This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimising your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower installation success rates and take up storage on users' devices.
Resolution:
Use the Android App Bundle to automatically optimise for device configurations, or manage it yourself with multiple APKs.
I know It's just a warning, I can ignore it right? I thought so too, but google store is not allowing me to deploy my app. So I must somehow solve this issue so that I can finally deploy my app in peace.
Here are the steps I'm making to build my app:
I followed all these steps (signed the app with key etc...)
I even tried using jarsigner as an extra step since the steps above didn't work
I also tried using zipalign to "optimize" my app
But none of that worked. Still google store is saying I need to make a bundle android app. But I'm using kivy/python so I can't use android studio to make a bundle and I can't find in buildozer docs how I can do this or if it is supported.
My app size is 28 MB, I even tried to remove some necessary stuff just to see whether it will work. So I reduced the size to 14 MB but that didn't work either. It's really frustrating. Building apps is fun while coding but the deployment process is real headache.
Here is a link to my app in case you want to play with the code or see the buildozer.spec file. I lost hope of uploading it to Play Store, hence I open sourced it.
Edit
here is how the google play console looks in my case:
This is the first tab, where I upload the app:
This is the second tab, where I should review and then release (notice here that I can't press the roll out to production button):
As you guessed, the message you're seeing about using AAB is just a warning, it doesn't prevent you from releasing the app. You're far from the first person to be confused by it though, the google interface is quite unclear.
The actual problem is that you need to make sure all the essential information is filled in on every page of the app store configuration. In your screenshot above, pages that have been completed are marked by a green circle with a check mark. In contrast, the "Store Listing" page only has a greyed-out check mark, indicating that you need to add something there before you can release the APK.
As discussed in comments, it turned out that the missing thing was screenshots of the app, and after adding them it could be released successfully despite the warning message.
Recently I updated my app by adding a couple of functions. In addition, I recreated the project since I had problems with app support for Android devices below Lollipop. After update and upload on Google Play, I update the app over Google Play on my separate real device (non test device) and it just keeps crashing (by opening it closes right away) without any errors on device. Google Play Console reports under "Crashes" IllegalStateException at
package.d.a (Unknown Source:73). However, the d.a package name is totally unknown for me, because I do not have that in my entire project.
package.MainActivity.onResume (Unknown Source:8). At this 8th I have an Import which would never cause an exception.
I guess that not only me, but some another users, who already updated the app, have also the save problem. However, I just generated a signed apk of my app and installed it on my real device (non test device), but for this step I needed to remove the app downloaded from Google Play before manual installing. This approach worked and the app does not crashes any more and works properly without problems.
I think, for users who download the app for the first time ever, this problem does not occur for them. How can I find out the cause of the problem?
Here is my app. If the app works for those who downloaded it after reading this post, please send me some short feedback using the built in Send Feedback in the app just to ensure the app functionality.
If you use proguard you need to add the mapping file to your console
If you use ProGuard to optimize and obfuscate your APK files, you can upload a ProGuard mapping file for each version of your app on the Play Console to deobfuscate your crash stack traces and help you better analyze your app's crashes.
Important: Only ProGuard mapping files are supported for deobfuscation.
Do you use any kind of testing with your app? You can try testing it on Firebase Test Lab, especially the Robo Tests, which try to crawl and use all app interactions.
They can help in detecting any faults or issues early on before releasing the app to the market.
You can also use Firebase's Crashlytics to detect crashes and get more details on the crashes.
Hope this helps.
I found the solution. In my case, I just needed to clear the cash of the app in the device settings. It helped to run the app again. However, there could be another solutions or even problems with such kind of app crash.
I uploaded an app I developed to google play. Since the app isn't free, google doesn't allow me to download it to my device.
The first users who tried to download my app claimed they got the 505 error (by leaving their comments on google play).
I read some threads about this error here on stackoverflow and made some changes that hopefully fix the problem, but how can I check it myself? Do I need to use other people's devices and pay each time I want to check if my app is downloadable or is there a better option ?
thanks
edit: just to be clear - I'm looking for a way to see whether people can download and install my app without getting any error messages. Preferably by going to the google play and downloading it myself.
The app itself works great once it's downloaded and installed. The problem was that people couldn't download/install it on their device.
You can use Google Administration to check erros and statistics for your apps.
Login to your Google Account on this page:
https://play.google.com/apps/publish
There you'll find all your uploaded apps. You'll also find crash reports, etc. Just for better administration of your apps.
To test your app the best way is to use the debug or Run 'app' option in Android Studio. If you want to test the signed apk you can also build it inside Android Stuido with the Build -> Generate Signed APK option.
Or you use the console commands if you don't use an IDE.
Check the documentation of the ADB (Android Debug Bridge)
http://developer.android.com/tools/help/adb.html
I hope this helps.
the way i prepare my app for deployment is by using the Eclipse and exporting the signed APK (as described here).
However, I've gotten reports that my app is not searcheable on the Market with devices that have test/development/unofficial ROM flashed.
Does anyone know how i can make the app visible for all android devices (production and development)?
Thx
Is this what you mean http://developer.android.com/guide/publishing/publishing.html
Alternatively, if you don't want to put it on the market, you can also put it on a website for anyone to download.