I am seeing a huge upswing in reports of this in Insights in the past few days - seems to be mostly on Android, not iOS
the stack trace is
System.IO.FileStream.ctor(System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options)
System.IO.FileStream.ctor(System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean isAsync, Boolean anonymous)
System.IO.IsolatedStorage.IsolatedStorageFileStream.ctor(System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, System.IO.IsolatedStorage.IsolatedStorageFile isf)
System.IO.IsolatedStorage.IsolatedStorageFileStream.ctor(System.String path, FileMode mode, System.IO.IsolatedStorage.IsolatedStorageFile isf)
System.IO.IsolatedStorage.IsolatedStorageFile.OpenFile(System.String path, FileMode mode)
Xamarin.Forms.Platform.Android.Deserializer+<>c__DisplayClass3.<SerializePropertiesAsync>b__2()
System.Threading.Tasks.Task.InnerInvoke()
System.Threading.Tasks.Task.Execute()
has anyone else run across this? Any suggestions on how to handle it?