It would be nice, but no, that's not an option. You need to make you own at app start and probably read a local variable at startup to check if it has been presented. That's how I do mine.
I'd put in a feature request. I'd think it would be easy to point to a EULA in a meta-file somewhere and have AIR installer present it before installation with an ACCEPT or REJECT button.
Nothing was available regarding that on the internet.
I think that is the only option we have to date and am thinking of doing the same as you said you do.
To prompt for the terms and conditions, I had a local file to check if the app is being used for the first time but there is a problem. When the user installs and runs the app for the first time, it prompts for terms and conditions... if user agrees, he/she can use it else the app shuts down.
However, if the user installs an app, agrees to terms and conditions and then uses the software and then uninstalls it, since the file marking the first use remains in the local machine, the next time user installs the software and uses it for the first time, there will be no prompt as the flag for first time use is set or marked false by earlier agreement. How do you solve this problem, Tedalde2?
Is there a good solution to this issue? I was hoping for some sort of boolean property that we could access that would indicate if the user was installing the app for the first time.
This is the only thing I could find from Adobe regarding the issue:
It still doesn't cover what happens if the 'firstRun' file remains after an uninstall.
The link you provided and what I did to solve my problem looks similar except for the update part.
However the install - uninstall - reinstall issue remains unsolved!
Did you try store your firstRun flag in the EncryptedLocalStore (ELS)?
You could try saving the current time date to the "first run" sentinel file when you create it. If that date is older than the creation date of an installed application file, then you know that the sentinel file is from a previous install. I'm not sure that this is 100% robust given the vagaries of various operating systems -- when I tried uninstalling and reinstalling a test AIR app, for example, the EXE file generated by the AIR installer for the application retained the old date, while the rest of the files had a new creation date. But it may be good enough for this purpose.