New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 140854 link

Starred by 72 users

Issue metadata

Status: Fixed
Closed: Apr 2013
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

Adobe AIR not supported in Pepper Flash

Reported by, Aug 6 2012

Issue description

Chrome Version: Google Chrome 21.0.1180.60
Chrome OS Version: 
Chrome OS Platform: Windows 7 Enterprise
Network info: 

Please specify Area-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
1. Go to and click "Install BBC iPlayer Desktop" or and click "Import your music"

Expected Result:
For bbc, I am able to install the iPlayer. For amazon, I am able to run the importer.
This is the case for Safari, IE, Firefox.

Actual Result:
For bbc, AIR does not install. for amazon, it does not run, and re-clicking the import button asks me to reinstall

How frequently does this problem reproduce? Always

What is the impact to the user, and is there a workaround? If so, what is it?
User cannot use native AIR apps started from browser. Workaround is to disable Pepper Flash and use the NPAPI Flash plugins.

Comment 1 by, Aug 6 2012

Labels: -Area-Undefined -OS-Chrome Area-UI OS-Windows Mstone-21 Feature-Flash

Comment 2 by, Aug 6 2012

 Issue 140800  has been merged into this issue.

Comment 3 by, Aug 6 2012

Status: Assigned
-> jschuh (have fun)
We've been working with Adobe for some time on adding support for AIR apps in a way that doesn't undermine Chrome's sandbox. We will update this bug when more information becomes available.

Comment 6 by, Aug 8 2012

 Issue 141246  has been merged into this issue.

Comment 7 by, Aug 9 2012

Yes, this is a real problem, please visit here to see the issue:

Comment 8 by Deleted ...@, Aug 9 2012

This bug also affects our app. This is a significant break. 

Comment 9 by, Aug 9 2012

Please fix ASAP!!!! This is crazy, we are losing customers as the first impression of our company is the install AIR app and now fails in all Google Chrome browsers.

See here:

Google / Adobe, please reply when this show stopper can be resolved?



Comment 11 by, Aug 9 2012

 Issue 141645  has been merged into this issue.
Please fix asap we just spent 12 months working on huge project that is now broken in chrome, but works in all other browsers even IE7. It seems like the new sandbox breaks air.swf ability to detect if the Air runtime is installed.

Comment 14 by, Aug 10 2012

 Issue 141773  has been merged into this issue.

Comment 15 by, Aug 10 2012

this issue should really be a Pri-1. basically all air apps are broken on chrome now! 

we have to tell chrome users to launch IE to make things work. this must be the first time something like this has happened on the web! nobody wants to do this.

Comment 16 by Deleted ...@, Aug 10 2012

With the current market share of Chrome, and the sheer number of AIR applications out there, this is an embarrassment. Please fix ASAP!!! 

Comment 17 by Deleted ...@, Aug 10 2012

This is a real problem for us. A lot of our customers are using Chrome and they are not able to install our AIR applications. PLEASE FIX THIS!!! 

Comment 18 by, Aug 10 2012

Google, why aren't you at least responding? Does someone know someone at google? I don't think Google Dev are aware of this... GOOGLE!!!!!

Comment 19 by, Aug 10 2012

Adobe / Google, can you please let us know if you are aware of this MAJOR MAJOR show stopper.
AIR Badge is broken in all Chrome in ALL THE WEB!!!
Is someone from Adobe working on this with Google?
Was this h

Comment 20 Deleted

Comment 21 by, Aug 10 2012

I just want to reiterate that this is a serious problem.  It embarrasses us and everyone else who distributes AIR apps, and damages the platform as a whole.  The nonchalant attitude from both Google and Adobe smacks of corporate arrogance.  This is about creating a good experience for web users as a whole.  Please make this a priority.

Comment 22 by, Aug 10 2012

I second that!!!!

Comment 23 by Deleted ...@, Aug 10 2012

Huge problem - updates please?

Comment 24 by, Aug 10 2012

Does anyone have a contact at Google? We need to make NOISE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I am investigating. Please don't shout.

Comment 26 by, Aug 10 2012

Thanks for the update, Jeffrey.  I really appreciate the communication.

Comment 27 by, Aug 10 2012

THANK YOU!!! You are the man!
You can go here:
and install SignageStudio Desktop version (AIR APP).
It will try and install AIR (even if it's already installed) and fail.
This is due to the new security box implementation of Flash Player in release 21 of Chrome / Papper plugin. If you disable Pepper, it will work ok with native Adobe plugin, bug of course no one wants this is not a valid workaround as everyone uses chrome with the default pepper plugin.

THANKS AGAIN, go make some noise :-) for us

Comment 28 by, Aug 10 2012

Adobe replied, with very unpromising news... 
See here:

Comment 29 by Deleted ...@, Aug 11 2012

Dear Google,

we are really loosing businesses because of this bug. Please, don't forget - with great power comes great responsibility! Your browser is the most popular now. Please, fix the AIR installation!

Comment 30 by, Aug 12 2012

any news? :(
Also caught out by the AIR badge issue - like everyone else we'd love to see a fix ASP, thanks in advance :-)

Comment 32 by Deleted ...@, Aug 13 2012

The reply given in the is not a good solution. You cannot expect users to be able to turn off Pepper Flash. Surely Google can make a change in the sandbox make sure Adobe Air installed. 
I'm also interested in a fix for this issue.

Comment 34 by Deleted ...@, Aug 13 2012

Please fix this as soon as possible since it's breaking lots of applications out there.

Thanks in advance.
Labels: -Mstone-21
Status: ExternalDependency
Thanks for your patience as I chased down the details.

Background: Google and Adobe collaborated over the last couple years to build Flash on top of Pepper (aka PPAPI), a next-gen browser plugin architecture which provides *much* better security and protection from malware for Chrome users. See for more details. In a nutshell, it enables us to run Flash inside a "sandbox" that is as strong as the Chrome native sandbox that's used for HTML pages.

Unfortunately, the functionality being requested cannot be supported directly from within Chrome's sandbox. Adobe AIR applications run outside the sandbox, so if we were to enable this functionality directly, it would open Chrome up to potential Flash exploits/attacks.

We have discussed this with Adobe in the past, and it is possible for Adobe to implement this functionality in a different way by integrating it with a Pepper "broker" that Chrome has provided. We are willing to support their efforts to do this if they wish.

I hope that all makes sense. We apologize for the unexpected inconvenience, but there is no way to do what is described within Chrome and Flash's current plugin architecture without compromising the security of our users.

I see that Adobe has responded on the forum post from comment #28, so please feel free to follow up with them there, and/or point them to this bug.

Comment 36 by, Aug 13 2012

ok, so it seems that the ball is in Adobe's court... let's see what they say!
Thanks Jeffrey.

I have filed a bug with Adobe about this issue here:

Please upvote!

Comment 38 by, Aug 19 2012

Does anyone know if this blog from Adobe means the issue is being fixed in September:  

Just to highlight is again: not only the AIR Badge is not working in Chrome 21, any LocalConnection communication between Flash in Chrome and Adobe AIR is also not working!!! So it's impossible to communicate between Chrome and AIR.
@39 and anyone else looking for LocalConnection between swfs in Chrome and external processes 
 issue 140000 

Comment 41 by, Sep 27 2012

If it's helpful to anyone, Amazon has used an interesting approach for this: detect which Flash is in play, and if it's Pepper, let the user know to either use another browser, or to disable Pepper provisionally (letting the NPAPI flash work instead).

Comment 42 by Deleted ...@, Oct 8 2012

Just to say as an end user trying to access BBC iPlayer.... I am off to use Internet Explorer. 

This is not an "oh dear Adobe cocked up". If this was not going to work v senior Google people should have been talking to v senior Adobe people to make it work BEFORE release. 

Sorry, this is about two pieces of S/W working together for an end user experience. I do not care which one of you will not throw your tools out of the sandbox what matters is I have wasted an hour or two of my life. 

Chrome is/was my browser. I am not so sure now. High time to have another look at IE which seems to be getting better and better. You should have stuck to search - you were good at that once.

Ex Tech Journalist and Computer Scientist
I can't emphasise how serious this is and how unprofessional it makes google appear. Over 3 months months in and still no fix for a bug which makes the BBC iPlayer, an application used by millions, unuseable.

Comment 44 by, Oct 26 2012

I completely agree... this is a joke!
I can appreciate the security vulnerabilities this functionality permits and understand why, as Jeffrey explained on 18 August, it was necessary for Google to close this hole.  What I don't understand is why, if Google was collaborating with Adobe on the Pepper API as stated, Adobe has so far failed to update Flash Player to make use of the Pepper broker, explain why this broker is insufficient to make functionality such as the one-click install badges work, or issue any official guidance, beyond the occasional speculation of an employee, to customers and stakeholders dependent on their product (such as myself) stating when we can reasonably expect this functionality to work again.

It's the responsibility of the VM's vendor (in this case, Abobe) to ensure cross-platform compatibility; this is the value proposition that causes firms such as my own to build on products such as the flash player in the first place.  Implicit in this responsibility is an obligation to stay abreast of each respective OS and browser manufacturer's roadmap.  The Pepper API has been in the works for a long time.  In the absence of some alternative explanation from Adobe, I can only deduce that they dropped the ball and left their customers to pay the price.

Until there's a more forthcoming explanation, the best information we have is the most recent bugbase post stating that "this issue will be fixed in near recent".

Consequently, I've used the 2.5 months that have elapsed since my badge installers stopped working to move my application to a different platform.
This issue is no longer Windows only with the latest update also MacOS is affected by it.

Comment 47 by, Nov 9 2012

Google/Adobe, thanks for letting us know ahead of time that the problem was going to be spreading to the Mac platform... oh, wait, I guess you forgot about that.

Seriously, guys, as we've hashed and rehashed, we'd really like some advance warning before you break stuff.  At least give us a chance to be proactive instead of always on the defensive.  Letting us know about these changes in advance would help us prevent having customers yelling at us, and in turn, us wanting to yell at you.

Thanks... we all really hope you're listening :-)
I think I probably speak for most users who are affected by this... We don't care if it's your problem or adobe's, it's OUR problem now and we want it fixed. If you cared about your users you would put top priority on communicating with Adobe and getting it squared away.
This is indeed one of our top priorities. We have in fact been communicating with Adobe regularly (weekly, if not daily) over the last several months, and Justin is working on a solution with Adobe's engineers (code reviews are in progress). I can't promise an exact ETA yet, but rest assured that soon as we finish designing and implementing a solution that still respects Chrome's security model, we will test it and ship it to the Chrome Dev, Beta, and Stable channels as quickly as possible.

Comment 50 by, Dec 10 2012

Jeffery thanks for the update. It sounds like the fix will be available for the stable channel until January of next year? Since the fix still has to make it through code review, Chrome Dev, Beta and then Stable channels. Is this a reasonable assumption?
Instead of using the broken connection, has anyone try the Flash cookie setting/polling trick?  1. Use setInterval on browser to write/read Flash cookie 2. Use setInterval on Air to write/read Flash cookie.

Both can communicate via some sort of seqId and request/reponse. 
The problem with the flash cookie setting/polling trick is that it assumes the Air app is already launched.  One of the features of Flash is that you can install/launch Air apps from the browser and then communicate with them.

Comment 53 by, Jan 8 2013

Jeffrey any update on the progress of the fix?
The bulk of the code has been written, and is currently going through security review.

Comment 55 by Deleted ...@, Feb 1 2013

Has the security review been completed?
Hi, the security review has been completed. You should be able to test out the code on the Chrome Dev channel now.

Please see this forum post for updates: (see replies #85 and #91 by Bob_Goldberg).

Comment 57 by Deleted ...@, Mar 8 2013

any update? the fix has been included in latest version? thanks.
Project Member

Comment 58 by, Mar 10 2013

Labels: -Area-UI -Feature-Flash Cr-Content-Plugins-Flash Cr-UI

Comment 59 by Deleted ...@, Mar 24 2013

How can I get this running in Chromebook (Samsung Chromebook)?

Comment 60 by, Mar 25 2013

Adobe AIR is not supported on Chromebooks.
Project Member

Comment 61 by, Apr 6 2013

Labels: Cr-Blink
Project Member

Comment 62 by, Apr 6 2013

Labels: -Cr-Content-Plugins-Flash Cr-Internals-Plugins-Flash

Comment 63 by Deleted ...@, Apr 15 2013

Status: Fixed
Yep. Everything should be hooked up at this point so the user will be asked if they want to launch AIR outside the sandbox.
@64 in which Chrome version (Pepper version) is the fix included?

I have tested the BBC Player page with Chrome Canary "28.0.1479.0 canary" and Pepper 11.7.700.169 and my installed AIR is not recognized by Chrome on my Mac.
@65 It seems that the fix only in versions for windows
The  Issue 169243  is a duplicate of this issue.

Just to be clear, Mac 10.8 is also effected by this issue and currently not fixed on Mac!

Do I have to create a new issue with the same content for OS Mac or can someone please reopen this issue and change the effected OS to Win AND Mac?!

I don't want to wait another 8 month for a fix on Mac OS X! 
"How can I get this running in Chromebook (Samsung Chromebook)?" 

same question?

Comment 69 by, Jul 24 2013


Comment 70 by Deleted ...@, Oct 14 2013

I still run into problem on IE10, Window 8.
I am unable to use the AIR app installer in Chrome on some domains. I am using the exact same barebones code on multiple domains and I it works on some domains and not on others. If I disable pepper on the domains it doesn't work on, it begins to work. Does anybody have a fix for this?

Comment 72 by, Apr 10 2017

Confirming that this is not yet fixed for linux.

Same problem on MacOSX 10.12.4 (16E195), Chrome 58.0.3029.110 (64-bit) and Flash

Corresponding issue @ Adobe :

Sign in to add a comment