Skip to content

Conversation

@TobiasPott
Copy link
Member

Fixed an issue where the storage controller does not use consistent UTF encoding and mixes UTF-8 and UTF-16 causing invalid cache files to be written to disk.

Compare to #319 as it addresses the same issue but was closed by the creator previously.

TobiasPott and others added 2 commits March 1, 2019 13:32
…null reference prior to create new StorageDictionary instance and trying loading its data from disk

Changed file write and read methods in StorageManager class to use unified Unicode encoding
Changed use of VolumeSeparatorChar to DirectorySeparatorChar as it is used in context of creating a relative folder insider the local app data special folder
Changed ParseClient.Initialize behaviour to use MetadataBasedStorageConfiguration.NoCompanyInferred as default configuration of no other was set (did override any existing with the old switch statement)
Added subclass registration of ParseInstallation class which caused an error with the other changes made when reading and parsing local cached information to an ParseInstallation instance at runtime.
@TobiasPott TobiasPott merged commit afbcf97 into parse-community:master Aug 29, 2019
@TobiasPott TobiasPott deleted the feature/fix-currentinstallation-caching branch August 29, 2019 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant