Skip navigation
Currently Being Moderated

Problem with badge installation in Chrome on Windows

Aug 7, 2012 3:02 AM

Tags: #air #installation #badge

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

 
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Aug 7, 2012 7:29 AM   in reply to Timur Valishev

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

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 7, 2012 1:13 PM   in reply to Kodji_76

    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&colspe c=ID%20Pri%20Mstone%20ReleaseBlock%20OS%20Area%20Feature%20Status%20Ow ner%20Summary

     

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

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 7, 2012 3:46 PM   in reply to Chris Campbell

    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
     
    |
    Mark as:
  • Currently Being Moderated
    Aug 8, 2012 5:24 PM   in reply to Timur Valishev

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

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 6:55 AM   in reply to SpecialK

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 6:56 AM   in reply to Chris Campbell

    Chris,

    You can't expect every visitor from the thousands of visitors we have to go and disable the plugin, this is crazy!!!!

    Please reply back when this can be fixed....

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 7:00 AM   in reply to Born2code

    Adobe, 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?

     

    Sean.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 10:08 AM   in reply to Chris Campbell

    Chris, asking average users to poke around in the Chrome plugin config just isn't reasonable.  We need a fix (not just a workaround) for this bug ASAP.  These bugs (and the lack of collaboration between you and Google) only damage the platform, hurting you guys in the long run. 

     

    Please at least give us status updates if something is happening.  Communication goes a long way.

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 10:14 AM   in reply to DWUser.com

    Also, I wanted to note that we're repeatedly seeing the following in log files:

     

    [time] Starting runtime background update check

    [time] Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.3.0. 3670/update
    [time] Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.3.0. 3670/update to C:\Users\<username>\AppData\Roaming\Adobe\AIR\Updater\Background

    [time] Runtime update not available

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 10:15 AM   in reply to DWUser.com

    Chris,

    this is crazy... we need you or google to give us an ETA, we are losing businsess becuase of this.

    Still no reply from anyone....

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 10, 2012 1:18 PM   in reply to Born2code

    I'm sorry for the delay, I've been waiting to hear back from the parties involved.  Unfortunately, I don't have a good story to tell you.  We're aware of this issue but neither Adobe nor Google have a solution planned at this time.  The workaround that I provided, is as you've noted, not scalable nor something that you'd want to recommend to all of your customers.  That leaves us without the badge install on Chrome, and instead suggesting that you include manual steps for the user to download the AIR runtime and your .air installer.

     

    I'm sorry I don't have a better solution to give you at this time.  I'm going to continue to escalate this and see what we can do.

     

    Thanks,

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 1:34 PM   in reply to Chris Campbell

    Thanks for the reply...

    Adobe has to pressure Google to fix this.

    Adobe had said they are "Doubling down" on Adobe AIR. And not supporing Badge install in Chrome is a MAJOR issue.

     

    Please push Adobe management to pressure Google for a workaround, this is not acceptable.

     

     

    Thanks for updating, Sean.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 4:35 AM   in reply to Chris Campbell

    Chris,

     

    Thanks for the update, but I'm sure you realise that this absolutely won't do. Breaking a feature with an update is one thing, but in that case I'm sure a fix is coming. However, if either Adobe or Google decided to discontinue this feature (you make it sound like they did), upon which so many companies rely for distributing their software, I would think that a public statement and a viable workaround would be presented...

     

    Can you please ask for clarification higher up in your foodchain and tell us either if this is a bug, soon to be fixed, or a discontinuation for which an explanation is forthcoming?

     

    Thanks,

     

    Erik de Bruin

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 5:03 AM   in reply to Timur Valishev

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 7:27 AM   in reply to Carlos_Rovira

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 1:10 PM   in reply to Chris Campbell

    Chris,

     

    It look like there is a solution possible, and Google is willing to work with Adobe to make it happen. From "http://code.google.com/p/chromium/issues/detail?id=140854#c35":

     

    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.

     

    The ball seems to be in Adobe's court...

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 1:21 PM   in reply to Erik de Bruin

    So now the ball is in Adobe's hat.

     

    Hope someone could respond to it and let us now if Adobe will fight for AIR as they promised or we will see another fail like the ones we used to see from the past 2 years...

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 1:38 PM   in reply to Carlos_Rovira

    Ok Google has replied, and so it seems the Ball is in your Court Adobe.

    As per Jeffrey C of Google and I quote: "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."

     

    See here:  http://code.google.com/p/chromium/issues/detail?id=140854

     

    So Chris, please relay this to management that it is now up to Adobe to fix this using the Pepper "Broker" feature that is built onto Chrome 21.

     

    Please let us know what Adobe has decided,

     

    Regards,

     

    Sean - http://MediaSignage.com

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 14, 2012 12:26 AM   in reply to Born2code

    I wanted to let you know that I hear you and I've relayed the sentiment along.  I'm working on getting additional information from my management team.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 14, 2012 6:48 AM   in reply to Chris Campbell

    THANK YOU!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 9:37 AM   in reply to Born2code

    Has anyone filed a bug with adobe about this yet?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 10:15 AM   in reply to paleozogt

    I've filed a bug with Adobe here: https://bugbase.adobe.com/index.cfm?event=bug&id=3310921

     

    Please upvote!

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 15, 2012 12:33 PM   in reply to paleozogt

    Thank you for adding the bug report.  I encourage everyone to vote, but be assured that we are very aware of this problem and are in the process of investigation.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 17, 2012 7:11 AM   in reply to Chris Campbell

    Any updates Chris?

    This is taking a long time and we are losing business in the meanwhile...

     

    regards.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 17, 2012 8:08 AM   in reply to Timur Valishev

    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-incom patibility.html

     

    The workaround (disabling the PPAPI) is the same.

     

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

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 17, 2012 5:22 PM   in reply to paleozogt

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 17, 2012 5:45 PM   in reply to Chris Campbell

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

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 19, 2012 8:00 AM   in reply to Born2code

    Does anyone know if this blog post from Adobe means the issue is being fixed in September: http://blogs.adobe.com/connectsupport/screenshot-does-not-work-in-chro me/ 

     

    Anyone?

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 21, 2012 4:10 PM   in reply to Born2code

    Quick update.  I talked with the engineering manager in charge of the Chrome effort yesterday and learned that we are working on fixing this bug.  I don't have a firm date for when this will be resolved, but given the effort and coordination required we suspect it will be up to a few months.  Please understand that everyone involved is aware of the impact this bug has on you and your customers and we will do our best to resolve this as quickly as possible.

     

     

    In the interim, our recommendation for Chrome users continues to be to include links to the runtime (http://get.adobe.com/air) and your .air installer.  I'll update this thread when I have new information, but feel free to post back or email ccampbel@adobe.com if you'd like an update.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:25 PM   in reply to Chris Campbell

    Thanks for the update, and the sooner the better...

     

    Regards...

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 24, 2012 1:52 PM   in reply to Chris Campbell

    A new Chrome 21 problem with AIR has come up:

         http://code.google.com/p/chromium/issues/detail?id=140000

     

    Specifically, it seems that LocalConnection between Flash and AIR is broken.  In my case, the whole point of being able to launch the installed AIR application is so that my SWF can communicate with it via LocalConnection.

     

    Is this problem also going to be fixed along with the rest of the AIR issues?  If the badge installation / AIR  launching features were fixed it would be meaningless without LocalConnection.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 24, 2012 3:49 PM   in reply to paleozogt

    I have exactly the same problem, but I think Adobe and Google are working very hard to fix this problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 24, 2012 4:18 PM   in reply to Marcus Fritze

    Marcus Fritze wrote:

     

    I have exactly the same problem, but I think Adobe and Google are working very hard to fix this problem.

     

    I'm not sure...  In the Chrome ticket, the first comment is "This is intended behavior as we consider this functionality to be deprecated in Chrome."  This comment makes me wonder if it is going to be fixed at all.

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Aug 24, 2012 4:21 PM   in reply to paleozogt

    I've brought this new issue up with the team, and I've also entered a internal bug for us to investigate (3313029).  My hope is we'd be able to address both issues simultaneously.  I'll let you know what I find out.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 24, 2012 4:24 PM   in reply to Chris Campbell

    Thank you, Chris. 

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 6:40 AM   in reply to paleozogt

    Hi, chrome to AIR local connection is crucial. Please let us know how this issue evolves over time.

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 28, 2012 9:41 AM   in reply to Chris Campbell

    Hi Chris,

     

    Both the AIR badge install and Chrome/AIR LocalConnection are essential to our browser/AIR hybrid applications, which we built for our partners on the assumption that Adobe APIs would remain supported and stable. Please let us know when this breakdown in the integrity of the Flash Platform will be addressed.

     

    Thank you.

     

    ...Joe

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 9, 2012 5:16 AM   in reply to JoeBerkovitz1

    Hi

     

    We encounter the same issue. We use Air Badge for our application install. Given the fact that most of our users use Chrome, this is really embarrassing (for us, for Adobe, for Chrome).

    Here is a short screencast that shows the bad unfortunate user-experience:

     

    http://screencast.com/t/61pV6pDGnjSL

     

    Thanks

     
    |
    Mark as:
1 2 3 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (3)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points