marcel Active Member Licensed User Longtime User Jan 18, 2016 #1 Hi, Even though I have implemented the Starter Service I got sometimes the error message dialog "<name application> Stopped" The normal error handler seems to work correctly but in the case the dialog appears it doesn't work. How can I find the error causing this? It is not reproducible and I get this also from users. Often when they play with another application and my app is running in the background. Could this be a Service? I have a Location Monitor Service and a Update Servers that pushes the GPS location to a server. Any suggestions?
Hi, Even though I have implemented the Starter Service I got sometimes the error message dialog "<name application> Stopped" The normal error handler seems to work correctly but in the case the dialog appears it doesn't work. How can I find the error causing this? It is not reproducible and I get this also from users. Often when they play with another application and my app is running in the background. Could this be a Service? I have a Location Monitor Service and a Update Servers that pushes the GPS location to a server. Any suggestions?
KMatle Expert Licensed User Longtime User Jan 18, 2016 #2 Hard to say without seeing any logs. Aren't there any reports (Play Store)? In one case we had a Problem caused by another app using the same Service Name by Chance. Try to change it to a unique one at a first step (better: get the logs). https://www.b4x.com/android/forum/threads/other-widget-stopped-my-widget.47192/#content Upvote 0
Hard to say without seeing any logs. Aren't there any reports (Play Store)? In one case we had a Problem caused by another app using the same Service Name by Chance. Try to change it to a unique one at a first step (better: get the logs). https://www.b4x.com/android/forum/threads/other-widget-stopped-my-widget.47192/#content
marcel Active Member Licensed User Longtime User Jan 18, 2016 #3 No, there is no logging in the play store?!? I hoped the general error handler picked it up. Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Jan 18, 2016 #4 If you are able to reproduce it locally then you can check the logs. There must be an error message there. Upvote 0
If you are able to reproduce it locally then you can check the logs. There must be an error message there.
marcel Active Member Licensed User Longtime User Jan 18, 2016 #5 What is the best way to check the logs? Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Jan 19, 2016 #6 Enable USB debug mode and connect to the device with a usb cable (without B4A-Bridge). Upvote 0
marcel Active Member Licensed User Longtime User Jan 20, 2016 #7 Ok, Done this but I do not see the error back on the B4A Logs window? Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Jan 21, 2016 #8 Are you able to see the logs at all? There must be an error message if the application crashes. Check the unfiltered logs as well. Upvote 0
Are you able to see the logs at all? There must be an error message if the application crashes. Check the unfiltered logs as well.
marcel Active Member Licensed User Longtime User Jan 22, 2016 #9 Yes, but i didn't check the unfiltered one. Will do that, but it is hard to reproduce. It just happend sometimes... Upvote 0
Yes, but i didn't check the unfiltered one. Will do that, but it is hard to reproduce. It just happend sometimes...
marcel Active Member Licensed User Longtime User Jan 31, 2016 #10 This is the error I found in the logging: Timeout executing service: ServiceRecord{3273b309 u0 com.yazula.android/.update} Crashing app skipping ANR: ProcessRecord{d97cba9 24224:com.yazula.android/u0a217} Executing service com.yazula.android/.update The only thing I understand that the Service Timeout? Upvote 0
This is the error I found in the logging: Timeout executing service: ServiceRecord{3273b309 u0 com.yazula.android/.update} Crashing app skipping ANR: ProcessRecord{d97cba9 24224:com.yazula.android/u0a217} Executing service com.yazula.android/.update The only thing I understand that the Service Timeout?
Erel B4X founder Staff member Licensed User Longtime User Feb 1, 2016 #11 Is 'update' a service in your app? Can you post its code? Upvote 0
marcel Active Member Licensed User Longtime User Feb 1, 2016 #12 Yeah and I also find the code that causes the problem and fixed it. I had a relation to another activity the already closed was. I should move some code to the starter service as this one is always active correct? If all activities and services will close then the starter will closed as last? Upvote 0
Yeah and I also find the code that causes the problem and fixed it. I had a relation to another activity the already closed was. I should move some code to the starter service as this one is always active correct? If all activities and services will close then the starter will closed as last?
Erel B4X founder Staff member Licensed User Longtime User Feb 2, 2016 #13 marcel said: I should move some code to the starter service as this one is always active correct? Click to expand... Yes. marcel said: If all activities and services will close then the starter will closed as last? Click to expand... The process with the service will be killed at some point when your app is in the background. Upvote 0
marcel said: I should move some code to the starter service as this one is always active correct? Click to expand... Yes. marcel said: If all activities and services will close then the starter will closed as last? Click to expand... The process with the service will be killed at some point when your app is in the background.
