CODEWITHSUNDEEP
androiddebugging
Ashwani kumar
Ashwani kumar

Reputation: 53

Android Application Debugging - How to handle issue 'App has stopped. open App again'?

My Android App is going through End user testing. It is being used in the moving bus. Sometimes while running we get error:

AppName has stopped Open App again.

Is there way to capture the stack trace / error whenever this issue comes so that it is easier to debug and fix?

One way I can think of is to run the App while connected with the Computer and then check the error. Is there any other way?

Thanks in advance.

I have tried to release the memory by making the variables null when User moves to different screen. If the function is called again then also I am initialising the variables.

Upvotes: 0

Views: 159

Answers (2)

gromyk
gromyk

Reputation: 610

For such "surprises" it'd be good if you'd use something like Firebase Crashlytics. Firebase Crashlytics is just a crash-reporter. I'd not offer you to use Crashlytics from Fabric, 'cause they will support it until 31 March 2020, after that only Firebase will be used.

You'll be notified each time when something went wrong on the devices of your users and for you will be available the stacktrace for occurred error.

Upvotes: 1

Asif Patel
Asif Patel

Reputation: 1764

You can use Fabric/Firebase Crashlytics. When your app crashes, it will give you crash information with device details.

https://fabric.io/kits/ios/crashlytics

https://firebase.google.com/docs/crashlytics

Upvotes: 0

Related Questions