Corey

> SyntaxError: Unexpected token � in JSON at position 0 at JSON.parse () at createStrictSyntaxError This is literally the same exact error message I posted in the Parse Slack: ...

Related [discussion](https://community.parseplatform.org/t/how-to-create-file-paths-inside-bucket-and-upload-specific-files-to-it/2941/3?u=cbaker6) which states they receive the same type of error using JS. As I've mentioned many times now, this looks to be a server issue and not related to...

You can try out [ParseCareKit](https://github.com/netreconlab/ParseCareKit) which synchronizes your data across devices and with a [Parse Server](https://github.com/netreconlab/parse-hipaa). You can self host or use, heroku, [back4app](https://www.back4app.com/), AWS, etc. For databases you can...

Your question is also related to this comment: https://github.com/carekit-apple/CareKit/issues/599#issuecomment-859831869

Thinking more about what @erik-apple [mentioned](https://github.com/carekit-apple/CareKit/pull/457#discussion_r440512939) > ... probably needs to be paired together with some other considerations, like updating the OCKDailyTasksPageViewController to make sure it show the tasks for...

When building a project that uses CareKit (latest commit on main) via SPM on macOS Ventura, the CareKitStore produces the following error: This error doesn't occur when building on macOS...

The `sortedOutcomeValuesByRecency` method currently isn't public, but copy/pasting the extension within your app and using it directly should address your issue: https://github.com/carekit-apple/CareKit/blob/248c42c4e4ea97ff5fe349361fa6e0a849eab204/CareKit/CareKit/Shared/Extensions/OCKAnyEvent%2BExtension.swift#L34-L52 You should then be able to use it...

I believe `values` lose order because they are stored in the OCKStore is a `Set` instead of an `Array`, so the order can never be guaranteed, https://github.com/carekit-apple/CareKit/blob/248c42c4e4ea97ff5fe349361fa6e0a849eab204/CareKitStore/CareKitStore/CoreData/OCKCDOutcome.swift#L38

@erik-apple I added some missing properties to `OCKHealthKitOutcome`. Though some of these aren't used currently, I made them match `OCKOutcome` as I suspect they will be needed in the future....

This might be related to `isSynchronizing` being removed from CareKit in #553, so there’s nothing in CareKit to stop duplicates being sent to the remote if multiple syncs are requested....