Support

Hi Needle,

Both of those have recently been added to the API. You can find them on a preview branch here: https://github.com/nullObjectPtr/hovelh ... ase/v1.1.8 They will be made available to the asset store shortly.

Hi Shay, I have some more information for you. I tested the demo project on both Catalina (10.15.7) and BigSur (11.2) build from Unity version 2020.1.17f1. It works on Catalina, but I see the bug in BigSur. I did some googling and other developers are experiencing similar issues in BigSur. Check out...

Thank you for the report Shay,

I will attempt to reproduce on my end today and hopefully get you some answers. In the meantime, can you provide me with the following?

• the unity version you are running

• the package version of the plugin

• your macOS version

Cheers,

You'd think right? But no - this callback only has a single error. This is true for all batch operations in cloudkit. This matches the API here https://developer.apple.com/documentation/cloudkit/ckmodifyrecordsoperation/1447486-modifyrecordscompletionblock?language=objc When you use batch operations...

It's a bit tricky but won't be too much trouble. I'll get to it this week.

Awesome!

OH man, you are really exploring all the options in this API aren't you? =) Yeah, you've hit a part of the plugin that isn't implemented. I figured no one would want to use it when it's easy enough to sort the records in C#. However, that would generate more marshaling overhead that would really be ...

Found some time to experiment with this today. Looks like you are right. Not every predicate can be expressed as a pure string. I was feeling confident there would be an underlying string representation for a CKReference, since the "%@" format specifier is used in string substitutions. As in: NSLog(...

Yeah, that's not a use case I've tested yet. I'll read up on the issue and reply back later with either a working string query, or a plan to update the API.

Makes sense. Yeah, dealing with apple APIs are a pain, especially this aspect of it. Causes lots of bugs when you have a code path that you can only test on deployed devices. I end up wrapping almost anything apple related in a platform-agnostic interface so that the editor code mirrors the platform...