Thanks, Chris. It's good to know there aren't many issues. Roughly what percentage of installs are affected?
Let's assume that the issue you mentioned can be replicated under the right conditions (which are still unknown by Adobe.) Although not ideal, it seems that IT installation staff could notice and correct the problem during roll-out campaigns, before the installer causes user-facing issues. But we already force a silent AIR install, so the potential problem won't be triggered / found until days after their installation, when staff and classroom students first run our AIR-dependent program. That would be a difficult burden for our clients.
What can be done to protect an installer against that situation?
Thanks
cpiDeveloper.
This occurs on a miniscule number of machines. Since I've been monitoring for it, I think I've seen this popup maybe 4 or 5 times tops.
I haven't tried the scenario you mention (you do a silent install, the EULA appears later when the user first launches the app.) However, you can bypass the EULA by creating a text file with the contents "2" and the name eulaAccepted and save it to the user's ~/Library/Application Support/Adobe/AIR folder. This will bypass the EULA dialog.
If you ever run accross this case, please have someone post here or email me directly. I'd be willing to help troubleshoot and I'd like to take a look at the system.
Thanks,
Chris