After doing some more research on the issue, I have found other users encountering the same issue we are:
In the second thread, it says:
“My issue seems to be specifically related to the use of "Silent Install". My client has a distribution license for the AIR runtime and is bundling the AIR installer with their installer. When Silent Install is used to install the AIR Runtime, Adobe's air.swf reports that the runtime is not installed. This happens until the user initiates an air app, at which point air.swf is able to detect the runtime installation.””
This seems to suggest there is a bug with the Silent Installer or with the air.swf getStatus function. I tried the steps above and was able to recreated and resolve the issue. Does anyone else know of a different workaround?
I seem to be having the same problem. Though in my case it's presenting after installing AIR using the downloaded installer, not an AIR badge. I'm still searching for a work-around but not having much luck with anything consistant.
It is the same for me Aaron V, I am installing using the downloaded AIR runtime installer, not the badge.
Did you try opening a .air file after installing? In the situation described above, the AIR runtime is shown as not installed, until I open a .air file, at which point it shows as installed.
I tried your suggestion, but my version of the button didn't change it's behavior.
I've been using http://shifd.com/tools as a baseline test. They have an AIR app and an install badge. Their install badge also fails to see that AIR is installed (from the downloaded installer) until I let the badge do it's thing and install AIR that way. Then the badge sees AIR, however, my app launcher still fails to see that AIR is installed.
I would guess I'm using a different technique to detect AIR than they are. Their badge is probably using getStatus, while I'm using getApplicationVersion() only. (I treat any error as AIR not being installed) I'll probably refactor that to be more typical soon.