Skip to main content
Participant
September 13, 2011
Answered

SharedObject; delete doing app update?

  • September 13, 2011
  • 2 replies
  • 951 views

Hi,

I am using a SharedObject as highscore list in my Andoid/IOS game, and every time I deploy to a device the SO/highscore is deleted;

Will this allso happen if I make an update to my game in App Store/App market? and is there a way to avoid this?

Would incrementing version number help?

Brian

This topic has been closed for replies.
Correct answer KerrDoubleTake

When you debug/run, make sure you uncheck the "clear data on each launch" checkbox.  If this is checked, the shareObject gets cleared each time.

When your app is updated via the market, the sharedObject will still persist after update, since the app's install path and sharedObject name has not changed.

Version number has no impact on this.

Don

2 replies

KerrDoubleTakeCorrect answer
Inspiring
September 14, 2011

When you debug/run, make sure you uncheck the "clear data on each launch" checkbox.  If this is checked, the shareObject gets cleared each time.

When your app is updated via the market, the sharedObject will still persist after update, since the app's install path and sharedObject name has not changed.

Version number has no impact on this.

Don

fiduzenAuthor
Participant
September 14, 2011

Hi Don,

Thanks for your reply. I am using flash cs5.5 and cant find any "clear data on each launch" checkbox?

I sounds great that a app update wont affect the SharedObject (if the path/name is unchanged), this is just what i wanted to hear .

Thanks again,

Brian

Inspiring
September 14, 2011

Sorry, this feature may only be available in Flash Builder.  You can always deploy pure AS3 projects via Flash Builder.

Colin Holgate
Inspiring
September 13, 2011

What are the exact steps you take when deploying? If you delete the old one, then install the new one, old data will get lost. If you're just doing an update/replace, then normally saved data shouldn't be lost, but there is a chance that SharedObject doesn't work using data that is in the preserved parts of the directory.

Can you test that?