Inspiring

Question

Seriously Adobe! Fix SharedObject issue .. it's been 2 years!

Forum|Forum|9 years ago
May 26, 2016
4 replies
3255 views

@Adobe .. This one is extremely frustrating.

my SharedObject's stop working and throw an error when the users available storage on iOS drops below approx 960 MB. This is a HUGE problem as most of my games target demographic is kids. Majority of these kids are on 16GB iPad Mini's... Majority of these kids are fighting for space on them. Most have to delete apps to add apps. This renders my games useless on their devices as they will get the error messages that they need to free up space.. even if they have 900 MB free.

Why can't this be fixed? Why has this been ignored for 2 years?

Development

This topic has been closed for replies.

Colin Holgate

Inspiring

Here is an interesting line from today's AIR 23 release notes:

[iOS] sharedobjects fail when available storage is low (3711301)

You can get the beta SDK here:

Download Adobe AIR 23 Beta - Adobe Labs

Pahup

Adobe Employee

Yeah, you've read it right, we were able to fix it finally, our internal testing shows that it's fixed now. However, we request everyone on this thread to try out and let us know if you still observe the issue. Thank you everyone for your feedback and replies to our questions, it helped us crack this one.

-Thanks

Pahup

Adobe AIR

IGZN

Inspiring

Hi

Does this affect EncryptedLocalStore and/or other databases as well, or only ShareObjects?

Can anyone please confirm?

Thanks

Colin Holgate

Inspiring

I tested other ways of writing data under the same conditions, and yes, the other ways of writing files also fail.

R

Roshan Chhetri

Adobe Employee

Hi Colin Holgate ,

Can you try running this Native Objective C code in your iPhone with issue?

NSLog(@"Start");

NSArray *paths = NSSearchPathForDirectoriesInDomains

(NSDocumentDirectory, NSUserDomainMask, YES);

NSString *documentsDirectory = [paths objectAtIndex:0];

//make a file name to write the data to using the documents directory:

NSString *fileName = [NSString stringWithFormat:@"%@/filename.txt",

documentsDirectory];

NSString *content = @"This is a TEST!!";

[content writeToFile:fileName

atomically:NO

encoding:NSStringEncodingConversionAllowLossy

error:nil];

NSLog(@"Done");

Create a new Xcode Objective C project and put the above code in the function: applicationDidBecomeActive:(UIApplication)

It should create a file filename.txt in the app's Document directory with the content "This is a TEST!!"

Let us know if you see any abnormal behavior.

-Roshan

R

Roshan Chhetri

Adobe Employee

Hi All.

We tested this bug on all iOS 7,8,9 by leaving below 100 Mb space but the bug is not reproducible.

However, when we filled the memory to "Available 0 bytes" the below error message showed up which I think is expected.

Error: Error #2130: Unable to flush SharedObject.

Anyone, who has an app that reproduces this issue when less than 400 MB free can mail me @ chhetri AT adobe DOT com or paste the Dropbox link here.

Adobe is happy to fix the issue.

-Roshan

Colin Holgate

Inspiring

The problem is that it's device specific, not app specific. When we had a Connect session about this two years, my very simple test case would go wrong for me every time on my iPhone 5, but you couldn't reproduce it on iPhone 5s. I also couldn't reproduce it on iPad. Perhaps you have an iPhone 5 now?