Skip to content

Releases: parse-community/Parse-Swift

4.14.2

09 Oct 02:02
dc7666f
Compare
Choose a tag to compare

Full Changelog, Documentation

Fixes

  • Addressed an issue that prevented updating ParseObjects with saveAll (#423), thanks to @cbaker6.

4.14.1

17 Sep 17:04
40a7b42
Compare
Choose a tag to compare

Full Changelog, Documentation

Fixes

  • For Swift 5.5.2+ all asynchronous methods that attempt to save, create, update, or replace use the async/await version of deep saving ParseObjects. This fixes any purple warnings caused by the SDK in Xcode. Older Swift versions use the synchronous version of deep saving (#418), thanks to @cbaker6.
  • Can catch when the Parse Server throws an improper ParseError that only contains "error" or "message", but does not contain a "code" (#418), thanks to @cbaker6.

4.14.0

15 Sep 21:18
085f5ad
Compare
Choose a tag to compare

Full Changelog, Documentation

New features

  • Add file caching using the Parse download folder (#416), thanks to @cbaker6.

4.13.1

14 Sep 17:04
e54a22c
Compare
Choose a tag to compare

Full Changelog, Documentation

Fixes

  • Remove ParseFile caching due to OS not having a natural way to cache files. Instead, if developers want to access a saved ParseFile, they should check the download directory for the respective file name. If you were having an issue with cached files, call ParseSwift.clearCache() after updating to 4.13.1 (#414), thanks to @cbaker6.

4.13.0

13 Sep 22:21
e2827c5
Compare
Choose a tag to compare

Full Changelog, Documentation

New features

  • Add helper methods to ParseFileTransferable protocol to assist with creating propper responses to file uploads (#411), thanks to @cbaker6.

Fixes

  • Remove cached error responses when decoding errors occur (#411), thanks to @cbaker6.

4.12.0

13 Sep 02:29
9ab5271
Compare
Choose a tag to compare

Full Changelog, Documentation

New features

  • Add the ParseFileTransferable protocol for overriding the default transfer behavior for ParseFile's. Allows for direct uploads to other file storage providers (#410), thanks to @cbaker6.
  • Add the become method to ParseInstallation which allows any ParseInstallation to be copied to the current installation. This method can be used to migrate any ParseInstallation to the current installation in the Swift SDK (#407), thanks to @cbaker6.

Fixes

  • Properly get the session token from the Parse Objective-C Keychain when using ParseUser.loginUsingObjCKeychain (#407), thanks to @cbaker6.

4.11.0

09 Sep 21:10
8245f9e
Compare
Choose a tag to compare

Full Changelog, Documentation

New features

  • Add a set method that developers can call on their ParseObjects which automatically sends updated properties to a Parse Server and merges those updates with the original ParseObject locally. The feature removes the requirement to call mergeable and implement merge(), but comes at additional computational overhead (#406), thanks to @cbaker6.

4.10.0

05 Sep 03:49
d94dcad
Compare
Choose a tag to compare

Full Changelog, Documentation

New features

  • Add a new operation method that allows developers to set a new value to a KeyPath without needing the string version of the key. Also adds the get() method to allow developers to get the unwrapped property of any ParseObject based on its KeyPath (#403), thanks to @cbaker6.
  • Add revertKeyPath() and revertObject() methods to ParseObject which allow developers to revert to original values of key paths or objects after mutating ParseObjects that already have an objectId (#402), thanks to @cbaker6.

4.9.3

02 Sep 14:57
4909de3
Compare
Choose a tag to compare

Full Changelog, Documentation

Fixes

  • When saving ParseFiles locally, files that have a directory in their filename save correctly instead of throwing an error on the client (#399), thanks to @cbaker6.
  • Default to not setting kSecUseDataProtectionKeychain to true as this can cause issues with querying the Keychain in Swift Playgrounds or other apps that cannot setup the Keychain on macOS. This behavior can be changed by setting usingDataProtectionKeychain to true when initializing the SDK (#398), thanks to @cbaker6.

4.9.2

30 Aug 18:15
ed74494
Compare
Choose a tag to compare

Full Changelog, Documentation

Fixes

  • Allow fully qualified ParseSwift types to be used externally by fixing clash with module name (#397), thanks to @cbaker6.