How does one go about debugging an error after release of the application to the public. I am not far enough in my experience to know how this works. I am older and retired and if I decide to release my application to the public I want to know what effort it will take to fix bugs. My experience in programming was mostly with IBM 370 Assembler and could quit easily read a dump and fix the application. But this was internal to the companies that I worked for. Before releasing an application to the public it becomes a huge responsibility to provide service to the customer but again I do not know how this would work. If it is a hassle I won't think about selling it since originally I am writing this for my own consumption.
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Android Question Debug Application after Release
- Thread starter bocker77
- Start date
- Similar Threads Similar Threads
Login to your Google developers console, then click on the name of your app. On the left have side click on Android vitals, click on ANRs & Crashes. Where is says Last 7 days, change that to last 60 days (centre of the screen). Click on any of the crash reports then scroll down the screen to view the crash logs for the selected report.
You should also look at this post by Erel, watch the video https://www.b4x.com/android/forum/threads/uncaught-exceptions.59805/#content
You should also look at this post by Erel, watch the video https://www.b4x.com/android/forum/threads/uncaught-exceptions.59805/#content
Upvote
0
Thanks again Peter as you assisted me on anther post. So when an app is in the field and not bought through Google Play and an error occurs does the customer contact the company that developed the app? Or do you always sell an app through Google Play so that you have a way of debugging it? This is all new to me and again thanks for your help!
Upvote
0
That completely depends on the situation. On apps published through the play store you can just use my first suggestion above. If you are creating bespoke solution for clients, what I tend to do is use the second method that I suggested which is for the app to send a crash report to the developer via an email.
Upvote
0
My limited experience with Released versions is that I get an error that reads something like "Sorry the app has ended" which you can only ask where the user was at in the app. I would assume a crash report is produced that explains the error. I know I probably need to read more on the net that would probably explain all of this to me but since we have experienced developers, as you sound like you are, on this forum I thought I would pose the question here. The crash report if one is produced I think would be more geared to a Java programmer and not B4A. Any information would be greatly appreciated.
As a side note what scares me is the number and releases of Android devices that one needs to deal with. In my old world it was in a closed environment. I know that the Emulator in the Designer would be of some help with this and also a lot of QA is needed.
As a side note what scares me is the number and releases of Android devices that one needs to deal with. In my old world it was in a closed environment. I know that the Emulator in the Designer would be of some help with this and also a lot of QA is needed.
Upvote
0
@bocker77 you should implement this solution into your app and send any crash reports directly to your email address. https://www.b4x.com/android/forum/threads/uncaught-exceptions.59805/#content
Upvote
0
Similar Threads
- Question
Android Question
DirInternal files not getting over written in Release version
