I have found a couple of things but the numbers are pretty low. I¹m a big Air fan.
Every once in a while, we would get a user that got an incorrect language version. For example, a US computer ended up with a Portugese version of the Air runtime. The numbers were small but in 45,000 users, it probably happened 5 times. It had also happened prior to 1.5 with a Japanese version being installed. Localized Air runtimes isn¹t something you can determine as the installed takes care of it. Likewise, and infrequently, an Air upgrade ended up displaying Black Boxes or return an Error Code: 0 in the upgrade UI. Again low in population but you need to be ready for this one as the only way to completely clean Air out was to uninstall AIR, blow off the ELS/TLS directory (encrypted local store), and reinstall. I could never reliably repro this. My biggest critisizm about the Air installer/updater is the lack of effective installation logging. Although you can configure Air to do some rudimentary logging, you have to put a configuration file in a directory that a Vista user doesn¹t have access to (see below). It should be an installer option rather than what feels like a hack. Corporate IT environments aren¹t crazy about the distribution of a RIA anyway (unless it has a business purpose) and asking IT to troubleshoot an Air install typically made for less than happy people. Tight access privileges really weren¹t much of an issue other than testing and user access of the filesystem. The Vista user, for example, can¹t even get interactive access to their own ³Application Storage Directory² Air alias. We made a mistake by using that directory (who knew) to download into. Air could put files there, but we had a bunch of users that we downloaded music to who couldn¹t end up finding it. We ended up moving our storage outside of the Air aliases. Likewise the encrypted local store. We bailed on using it (only an administrator can see it) and built our own encrypted file structure. K
