• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Flash plugin from labs site is 13.0.0.168, not 13.0.0.191

New Here ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

The new flash plugin available for download from Adobe labs is not 13.0.0.191, it's the old 13.0.0.168.

I've tried downloading both of them several times for IE and "Others".

Views

1.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Apr 14, 2014 Apr 14, 2014

This is typically caused by the files not being released from the cache correctly on an Akamai node.  I'll ask someone to force-flush the cache.  That usually resolves the issue.  Please give it a couple hours to let the changes propagate through the network.

Votes

Translate

Translate
LEGEND ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

This often happens with Flash Player and AIR, right after a version has been released. The one in labs is the last beta, the release one is most likely more recent than the last beta. Labs will overtake the release one again when they post a new beta.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

Flash plugin 13.0.0.168 is from the 28. march. The latest release version is 13.0.0.182 and the release note states that the latest beta is 13.0.0.191.

That's why I wonder why the labs download isn't 13.0.0.191,

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

I just installed the debug version of the plugin here:

http://labs.adobe.com/downloads/flashplayer.html

and it shows as being build 191. Any chance you tried to install it on April 8th? Sometimes it takes a while for the latest file to propagate.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 14, 2014 Apr 14, 2014

Copy link to clipboard

Copied

This is typically caused by the files not being released from the cache correctly on an Akamai node.  I'll ask someone to force-flush the cache.  That usually resolves the issue.  Please give it a couple hours to let the changes propagate through the network.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 17, 2014 Apr 17, 2014

Copy link to clipboard

Copied

Eventually I ended up downloading the correct version (as I expected) and today .199 came down nicelly.

But since the release was 8. april and I still got an old version 5 days later, I had to ask.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 17, 2014 Apr 17, 2014

Copy link to clipboard

Copied

LATEST

Not a problem at all.  It's usually an issue with an individual Akamai node, and the activity on a single node is way below the noise floor when looking at the data in aggregate.  If it continues to be an issue for you in future releases, I'll collect some network data from you and open a support case.  My experience is that it happens on random nodes, which makes it harder to point an engineer to something actionable.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines