Android Question B4A 3.2, the IDE and the FirstTime Variable

The thread title should summarize the question. Please update it.

Without seeing any code we can only guess. I guess that it is related to the FirstTime variable somehow.

OK, I inserted Log("a,b,c...") lines into Activity_Create, and here is what I'm seeing:

Everytime that I press the play button to start my app from the B4A IDE, statements inside the "FirstTime = True" are getting properly executed.

However, when I start the app by pressing the phone icon on its screen, the "if FirstTime = True" statements are only getting properly executed every other time...or a better way to say it may be only after a hard stop from the Android OS.

So when my app is run by pressing its phone screen icon button, it will run correctly that one time, but it won't run correctly on subsequent times until after the Android OS shuts the app down hard. If the user just exits the app by hitting the backspace key, then the app won't process the "if FirstTime = True" statements the next time that the app icon is pressed on the phone's screen.


This is probably embarassing. I suspect that I'm missing some newbie fine point on how to insure that the first time the app is run from the icon, the "if FirstTime = True" statements are properly executed.


Right now, with my lack of understanding, my app is behaving as though the user is merely pausing the app instead of terminating the app, and when the user presses the app's icon a subsequent time, my app is behaving as though it is being resumed instead of started anew.

I solved the problem for my app. The issue is that the Android OS isn't reliably resetting the FirstTime variable.

No big deal, I created a synthetic First Time global variable to deprecate the B4A FirstTime variable.



You will not see the Android FirstTime problem when testing your app from the B4A IDE because the IDE is resetting the FirstTime variable correctly.

However, you *will* see the Android OS causing havoc with the proper setting of the FirstTime variable when you run your app by hitting its icon on a smartphone...unless you use something similar to my solution above by creating and setting a Synthetic FirstTime (SynFirstTime) boolean for your activity_create sub.

Have a read of this: http://www.b4x.com/android/forum/threads/android-process-and-activities-life-cycle.6487/#content

Particularly this line:

If the user launches your program again and the process was not killed yet the same process will be reused.

Click to expand...

The reason it runs perfectly every second time is that when the error occurs and you select No to the continue question, the app is killed and therefore does restart next time.

stevel05 said:

Have a read of this: http://www.b4x.com/android/forum/threads/android-process-and-activities-life-cycle.6487/#content

Particularly this line:



The reason it runs perfectly every second time is that when the error occurs and you select No to the continue question, the app is killed and therefore does restart next time.

Click to expand...

Thanks. That makes sense. And since users are unpredictable, my Synthetic First Time solution above will work either way for all of us, whether the process was killed or re-used.

You should work within the android framework the way you describe the first time variable working within activity create is correct.

Without knowing what you are putting within your synfirsttime section, It is not possible to say what problems it will create. But it will create some down the line.