Error on app update

[aholla]

Hi,

I have a strange issue. I am using ES3 to save a list of a custom type (CustomProfile).

For new users this save works fine. For existing users, when i try and save the list, i get an error.

The list has different key to the previous version. Any ideas as to what might be causing the erorr? I am using a new key to save a new list so not to interfere with any previous data that might have been saved because the 'CustomProfile' has changed a lot.

Thanks,

Adam

[Joel]

Hi there,

Please could you let me know what error you are getting.

All the best,
Joel

[aholla]

Im not sure what the errror is as I cant replicate because I cant update the app as I dont have an old version.

When trying to save it would through an exception but im not sure is this is an IO error or a permissions error at the moment.

I will report back when I know more from the new logging.

[aholla]

Ive got this from the Unity Dashboard (I have 1000's of these, all esizting users are getting it):

Code: Select all

ES3Writer.Merge (ES3Reader reader) (at <00000000000000000000000000000000>:0)
ES3Writer.Merge () (at <00000000000000000000000000000000>:0)
ES3Writer.Save (System.Boolean overwriteKeys) (at <00000000000000000000000000000000>:0)
ES3.Save[T] (System.String key, T value, ES3Settings settings) (at <00000000000000000000000000000000>:0)

[Joel]

Hi there,

It's not possible to tell what is happening as what you've posted is the stacktrace of an error message rather than the error message itself.

All the best,
Joel

[aholla]

Code: Select all

NullReferenceException: Object reference not set to an instance of an object.

ES3Writer.Merge (ES3Reader reader) (at <00000000000000000000000000000000>:0)

Also this seems to be happening on IOS only... Butthat might just be the main audience. I have no issues of this on Android.

[Joel]

As this is a generic error, and there are no line numbers for where this is happening, it's difficult to know exactly what is happening. However, the most likely cause is that the path provided is not a valid path for iOS. However, this would only throw this error in earlier versions of Easy Save.

Just to check, are you using the latest version of Easy Save?

Another cause could be that the save data contains a type which no longer exists in your project. Does the error happen when you tested it in iOS with the old save data present? If this is happening for all iOS users then it should also happen in your testing, so you should be able to do a development build where we can see the line numbers of the stack trace.

All the best,
Joel