Android Question Bug when App is on the background for a random amount of time

[German Buchmuller]

Hi, I am experiecing a weird behaviour on my Apps. When they are in the foreground they work great, but once they are minimized and therefore sent to background, after some minutes (may be 10 to more than an hour), the app like bugs out. When you open it again (before it was on the background), the Activity_Create event on the Main activity is raised, as if it had been task killed. This causes the app to crash when, for example, the user was in another activity, so when he opens it again, it crashes and says ...view was not initialized.

To sum up, when an app is in the background for a long time, the system partially "kills" it, making it crash when the user opens it again. Any ideas what to do? Thanks!

 

[Peter Simpson]

@German Buchmuller Have you looked at this Automatic Foreground Mode and also this Background location tracking

Enjoy...

 

[Computersmith64]

Are you using a Starter service? https://www.b4x.com/android/forum/threads/starter-service-consistent-single-entry-point.57599/

- Colin.

 

[German Buchmuller]

@German Buchmuller Have you looked at this Automatic Foreground Mode and also this Background location tracking

Enjoy...

Are you using a Starter service? https://www.b4x.com/android/forum/threads/starter-service-consistent-single-entry-point.57599/

- Colin.

Hi to both of you. Im sure it has nothing to do with starter service and automatic foreground mode. It has to do with memory use. Any app that I make, if I am on an Activity, then minimize the app for a long time and then re open the app, sometimes it starts again from Main activity, and sometimes that Activity that was opened is still open, but when I go back to the previous activity, it starts again. Dont know how to solve this. Any idea? Thanks!

 

[Erel]

Your app should expect activities to be destroyed and recreated. Move all the logic and state that you can to the starter service or to a class that is initialized from the starter service.

 

[German Buchmuller]

Your app should expect activities to be destroyed and recreated. Move all the logic and state that you can to the starter service or to a class that is initialized from the starter service.

I will do that, but many times in the logs it says: Object should be first initialized: (...and a view that was not initialized)
I dont know if it has to do with phone Battery Optimization Permission.

 

[Erel]

I dont know if it has to do with phone Battery Optimization Permission.

It doesn't.

I will do that, but many times in the logs it says: Object should be first initialized: (...and a view that was not initialized)

This means that you have a bug. Watch the life cycle video tutorial: https://www.b4x.com/etp.html?vimeography_gallery=1&vimeography_video=255402345

 

[German Buchmuller]

It doesn't.


This means that you have a bug. Watch the life cycle video tutorial: https://www.b4x.com/etp.html?vimeography_gallery=1&vimeography_video=255402345

I will see it again then. Thanks!