Corey

> There should be no substantial implication in the server or SDKs because being date fields, it would be unreliable to draw any conclusion about the object state. If there...

> The approaches you referenced seem a bit flawed anyway. Various ways to determine whether an object has been saved or not, depending on whether custom obj id is set,...

> Would that solve the problem for the API clients ? I’m not sure... I made my comment just to mention that `createdAt` is currently used to determine state on...

In my [parse-hipaa](https://github.com/netreconlab/parse-hipaa) repo, I’m currently able to add indexes to a parse-server by doing the following in my [index.js](https://github.com/netreconlab/parse-hipaa/blob/61f39143795af311e12d402a8e837a9f98e5299a/parse/index.js#L182-L207) (this works for Postgres and Mongo as it leverages the...

I believe `.parseSwift.sdk` should be able to stay the same to distinguish it as a the Swift SDK Keychain. It seems like you would like something to specify the bundle...

The current init for the Keychain makes all instances have the correct ending if they are suppose to. Code that creates instances by passing in the service and doesn’t end...

> Otherwise I would just remove the duplicate parts. duplicate parts can be removed and/or linked to the server document > Are there any docs about how to use the...

> **ParseError code=-1 error=Invalid struct: No value associated with key CodingKeys(stringValue: "name", intValue: nil) ("name").** If you are receiving this error when attempting to save a `ParseFile` it is because...

The server returns a number of improper errors: https://github.com/parse-community/parse-server/issues/7444, https://github.com/parse-community/parse-server/issues/8029

> - [x] I can reproduce the issue with the latest versions of [Parse Server](https://github.com/parse-community/parse-server/releases) and the [Parse Swift SDK](https://github.com/parse-community/Parse-Swift/releases). Also, please uncheck the box above as the latest version...