I recently had a lot of problems with the Adobe AIR framework so I thought I’d share that information with you.
Then in November last year Adobe released version 1.5 of the Adobe AIR framework and eventually, during the beginning of this year, I looked into it to see if any of the problems and annoyances I had encountered previously had been solved.
However, when I installed version 1.5 on my Mac, no Adobe AIR application would work. No matter which one I tried, they just froze on me when I started them, and I had to force-quit them.
The support experience
January 23rd I contacted Adobe support through its web site, and heard back from them within a few days. And, even though they gave me polite and fairly swift replies, it took all the time to March 3rd to solve the problem (to be honest, the last week there my replies weren’t that fast either). However, that’s a total of six weeks to make any AIR app running on my computer!
The Swedish support, where my journey started, failed to solve my problem (I didn’t choose Sweden, I got directed to them through IP or something), so eventually I got a direct e-mail from a Adobe person in the UK with the solution. Interestingly enough, he didn’t write the solution in the e-mail itself, but rather linked to a comment in a blog post from Mike Chambers, who’s one of the people on the Adobe AIR team.
The problem itself
It seems that Adobe AIR, since it’s based on the WebKit rendering engine, has a severe problems with InputManagers, such as SIMBL, on Mac computers (note, this does not apply to any computers running Windows or Linux).
The solution is to completely empty any Input Managers you have installed on your Mac, located under
~/Library/InputManagers (the Library folder located under your user folder). If you do that, the problem magically disappears!
The downside with this, though, is since the Safari web browser basically has a non-existent plugin/extension structure, smart developers have used SIMBL to extend Safari with all sorts of nice features. A quick look at something like Pimp My Safari shows just how important this approach is.
I will leave it unsaid if Safari should totally change its extendability or not, but this means that if you want Adobe AIR 1.5 to work on your Mac, you basically can’t extend Safari. And even if I’m mainly a Firefox users, for me it’s a pretty easy decision whether I want to be able to extend Safari or run Adobe AIR (let’s just say Adobe isn’t close to winning that one).
Adobe has to make sure Adobe AIR works even though people have InputManagers like SIMBL installed. Nothing else is even an option to consider.
My general take on all this is three-fold:
- Shouldn’t this information be on a notice board for all Adobe staff to check when issues arise with Macs and Adobe AIR 1.5? And, in a better location than a blog post comment?
- Adobe AIR has to be completely independent from any settings that will affect Safari on a Mac, and vice versa.
- Being egoistic, and perhaps a bit shitty, now: before Adobe AIR Marketplace changed its design, it was possible to see that actual number of times a software had been downloaded. Comparing the numbers there to the number of GMDesk downloads, GMDesk was, as far as I could see, amongst the highest 20 or so installed AIR applications available. With that in mind, if it takes Adobe six weeks to help out a developer behind one of the most popular installs, can you imagine the developer motivation just sipping out, and getting tired of that platform?