Skip to main content
T
Timur_Valishev
New Participant
August 7, 2012
Question

Problem with badge installation in Chrome on Windows

  • August 7, 2012
  • 8 replies
  • 48194 views

Dear Adobe,

The badge installation stopped working recently, probably after last Google Chrome update. Problem look like this: after clicking "install now" badge the confirmation window to install Adobe AIR appears ("Would you like to install adobe AIR?"). I click yes, download progress bar goes from 0 to 100%, and then error message appears ("Download error. Try again?"). Click yes - everything repeats.

Also, in Chrome on Windows there is text under the badge: "In order to run <app name>, this installer will also set up Adobe AIR" - but latest AIR is already installed. We used standard installation badge, provided with the SDK.

OS Windows 7 ver 6.1 (build 7600)

Browser Google Chrome 21.0.1180.60 m

Flash Player 11.3.31.222

AIR 3.3.0.3670

The problem appears only in Google Chrome, and only on Windows. In IE and FF everything seems to work fine. In Chrome 21.0.1180.57 on Mac OS X 10.7.2 it works fine as well.

You can look at the error here: http://www.jivosite.ru/install_application

This topic has been closed for replies.

8 replies

UMHDubai
UMHDubai
New Participant
October 19, 2019

Sometimes it occurs when we install chrome extension of adobe also. Hope Google and adobe recognize this thread. 

 

G
godrma
New Participant
April 15, 2013

why does not fix this simple bugs? i don't understand about adobe and google.

V
Vince_HM
New Participant
November 13, 2012

I'm having the same issue now in Google Chrome on Mac.

Can someone verify this?

Chrome version: Version 23.0.1271.64

Mac Os X: 10.7.5

I
Inspiring_Phoenix1549
Participating Frequently
November 13, 2012

Hi Vince,

Yes -- Chrome version 23, released last week, introduced this issue on Mac as well. 

Chris, as I mentioned last week on the Chrome tracker, we really would have appreciated a heads-up that the problem was going to be spreading.  It's not realistic to expect developers to always be playing reactive catch-up; if we had been given advance notice, at least we could have proactively warned users and updated code. 

(I would have posted this message last week, but the Adobe forums were broken as well and login didn't work...)

Thanks,

Nathan

E
elder_soares
Participating Frequently
November 13, 2012

the same here, chrome on mac not working... things get worse...

C
CWBenccw
Inspiring
September 18, 2012

Oh, I am encountering the same problem,  it really affect the user experience, please help.

Thanks.

chris.campbell
Community Manager
chris.campbellCommunity Manager
Community Manager
September 18, 2012

We're working on it.  I'll see if there any update that I can post.

Chris

K
kharganpl
Known Participant
February 19, 2013

What's likely going wrong for you is that your AIR app was installed from another browser and Chrome is unaware of the install.

Please try this: uninstall your AIR Application, uninstall AIR, and then you should be able to install your AIR Application via its badge installer from Chrome.

(Alternate way to demonstrate an AIR application installation working in Chrome:  install a previously uninstalled AIR app.)

Technical Details

Security Requirement: 

In order for Badge Installs to work the Chrome broker must be running and starting up this broker requires that the  user accept a security prompt, the infobar.

Implementation:

AIR Badge Installers depend on AIR.SWF, which uses the the ActionScript class ProductManager to download and launch the "AIR Application Installer", a native executable which installs an AIR application on behalf of FP.

ProductManager was originally omitted from Chrome Pepper FP because it depends on functionality that Google considers a security risk: save to local disk and launch a native executable. Pepper FP 11.6 implements this code in a broker -- a separate process running outside of these security restrictions.

As Google considers this code insecure, Chrome will only launch this broker after the user has accepted the infobar from the domain. Chrome records a setting when the user allows the broker, so the user won't see the infobar again for that domain unless they delete the corresponding setting.

Google also wants the infobar to be shown only in response to a user interaction, such as a mouse or keyboard click. Thus, when a domain is not yet allowed Pepper FP will only start the broker after the user accepts the infobar prompt shown in response to ProductManager.download().

This restriction explains why we don't expect Chrome to detect an application installed by another browser -- until you've accepted the infobar as part of download(), the broker won't be running, and unbrokered ProductManager methods fail -- such as detecting the installed version of the "AIR Application Installer" or launching it. Once the broker is running ProductManager methods will be brokered and work as they do in any other browser. In subsequent sessions the broker will be started before the script begins execution, because Chrome remembers the domain in its settings.

At the moment, AIR.SWF is the only SWF flagged as requiring the broker, so it's also important that your AIR Badge Installer follow best practices and depend on AIR.SWF to help install you AIR application.


Any reaction ?

paleozogt
paleozogt
Participating Frequently
August 17, 2012

Looks like Chrome 21's sandboxing broke more things than just Air.swf.  It seems that Adobe Connect (which is based on a Flash Add-In?) is also broken:

     http://helpx.adobe.com/adobe-connect/kb/google-chrome-21-browser-incompatibility.html

The workaround (disabling the PPAPI) is the same.

I'm somewhat baffled that Adobe didn't see this coming.

chris.campbell
Community Manager
chris.campbellCommunity Manager
Community Manager
August 18, 2012

Last I heard we had at least one developer investigating this issue.  I'll ask for an update on Monday.

Chris

Ps. Yes, Connect was affected too.

B
Born2code
Known Participant
August 18, 2012

Thanks for the update, we are all crossing our fingers over here !!!!!!!!

C
Carlos_Rovira
Known Participant
August 13, 2012

If what Erik says is true (discontinue this feature)...I think is a new bad action from Adobe that will continue to maintain the perception that Adobe is driving things really bad and is not taking care of customers.

This is other drop that will make people continue to shift from Adobe to other vendors taking into account that products are left in the cold from one day to another.

What happen to Adobe?

B
Born2code
Known Participant
August 13, 2012

Another bad publication from Adobe, and I think no one would it use it even for Video or games, people will be scared of committing to the platform.

Adobe said they are "Doubling down on Adobe AIR", after more than a week, still no fix, sure seems like a bet to me

S
SpecialK
Participating Frequently
August 9, 2012

This bug has also affected our app. All Chrome users cannot install our AIR app using the badge installer.

B
Born2code
Known Participant
August 9, 2012

Adobe and Google, come on? You can't just break the AIR Badge and leave it like that for days....

People are coming to our site and can't install our AIR app, this has to be fixed ASAP!!!!

We are losing business because of this bug.

FIX ASAP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Adobe, please reply....

See issue here: http://mediasignage.com/html/get_started.html

A
Anonymous
August 7, 2012

I have exactly the same problem. It works on IE and FireFox. But in chrome I can't install AIR.

chris.campbell
Community Manager
chris.campbellCommunity Manager
Community Manager
August 7, 2012

Thanks for bringing this up.  When you have a chance, please visit this bug and add a comment:

http://code.google.com/p/chromium/issues/detail?id=140854&q=air&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20OS%20Area%20Feature%20Status%20Owner%20Summary

I'm going to talk with the Chrome team to find out the status.

chris.campbell
Community Manager
chris.campbellCommunity Manager
Community Manager
August 7, 2012

I was able to work around this by doing the following, I realize it's a cumbersome workaround but it does clearly show that this is a PPAPI (pepper) related issue.

  1. Navigate to "about:plugins" in the Chrome address bar
  2. Click the Details link in the upper right part of the page to expand all items
  3. Locate the "Shockwave Flash" entries (there will be 2 or 3 of these)
  4. Click "Disable" for the PPAPI copy (most likely the first one listed), which has a version number of 11.3.31.222
  5. Restart Chrome for good measure and try again
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices