I'm developing an app recording with a background service your position and sending it to a server, every second. As many other users, we have to deal with battery saver to make sure the background service works properly. And we have to thanks daily dontkillmyapp.co/ for their outstanding work.
However, I got a issue reported with Crashlytics countless time
KotlinExtensions.kt line 53 retrofit2.KotlinExtensions$await$2$2.onResponse
This error is reported as non fatal, but usually it match with the exact time the background service is being killed by the system, silently.
Our app is being generally used with poor network conditions. Still, is it normal to have such reports? Or definitively this error should not be triggered by Crashlytics if the app was handling well his network latencies or reliability?
Thanks
from KotlinExtensions.kt line XX retrofit2.KotlinExtensions$await$2$2.onResponse got this countless time with Crashlytics
No comments:
Post a Comment