Reputation: 343
I wrote a simple swf to set and get shared objects. When I set data to it through FF and try to get the same object through IE it works fine. But, when I'm trying to get it through Chrome, it doesn't work - like Chrome has it's own place for the local storage.
I used the below url to see if the shared object is saved: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html
I don't work at oovoo, but I see that they have the same issue :) You can simulate it by browsing to www.oovoo.com in FF and open the below link in IE and Chrome - you will see that oovoo.com shared object only in IE.
Any idea why it happens ?
10x,
Upvotes: 9
Views: 7929
Reputation: 11
The issue is with the flash plugin that chrome uses.
If you type: "about:plugins" in your chrome address bar, you can see the plugins that chrome is currently using. If the current enabled flash player is "pepperflash", your shared objects aren't going to be stored.
What you need to do, is download a new version of flash from Adobe's site.
After you have a new version of flash, go back into your Chrome plugins, disable the "pepperflash" version of flash, and enable the other one.
After doing this, I've been able to use shared objects just fine with Chrome.
Upvotes: 1
Reputation: 71
I recently ran into this issue as well. It seems Chrome is not using the Shared Objects you would expect it to (%APPDATA%\Macromedia\Flash Player\#SharedObjects\). Chrome seems to be keeping its own in: %APPDATA%\..\Local\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\WritableRoot\#SharedObjects\
I don't know if this is a bug or intentional, but it certainly is annoying.
Upvotes: 7