When replacing the original Home Screen with another screen, where the original contains On Start actions, the app continues to reference the original Home Screen for the App.OnStart function. In fact, if the original Home Screen is deleted and the new Home Screen contains the same On Start actions, they are not executed and any variables or collections are blank/empty.
This is definitely a bug.
Thanks for the feedback.
It seems the OnStart property will not work consistently with the screen action, like duplicate, delete or move up/down.
Please consider switch to Onvisible property as a temporary workaround.
I will send the feedback regarding the OnStart property from my side, and update here if I have got any response back.
Have seen this as well.
The most common "work around" to things like this is to Save the app in studio, exit, and reload.
Unfortunately I find myself doing this several times a day to work around some of the quirks like this (and there are a number of them) where things that did work suddenly don't. But a reload of studio often seems to resolve many of them.
Thanks @BrianR for the reminder. The symptom should be fixed after a reload. So it is recommended to take re-check the configured formula after a reload.
The OnStart property has the following explanation documented:
OnStart – The behavior of the app when the user opens the app.
Keep your eyes open for our upcoming T-shirt design contest!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020