I believe it was announced that apps outside the Mac App Store could use iCloud when iCloud drive was introduced.
This is logging out when try to run an exported Developer ID application:
Killed my.App.Bundle.Id.here because its use of com.apple.developer.ubiquity-container-identifiers entitlement.
Good guess 🙂 , but, you know, I'm not sure the system works off the bundle identifiers. Doesn't it evaluate each signed app separately, not really caring about the bundle identifiers?
I would think so...not really my area though.
It's just a hunch because I can't think of any other reason why my app would be terminated by the system for using iCloud entitlements when signed with my developer iD, and this app would not be. Maybe some hocus pocus...if the app is signed from the same developer...with the same bundle id as one on the MAS, they just let it go through?
Maybe it's undocumented but an intentional way to say "hey you can get an iCloud container outside MAS but you have to at least have a version of the app also inside MAS." Or maybe whatever checking the system does, is simply not good enough and this is some sort of bug. Or maybe Apple has a really good relationship with this developer.
Try running spctl -av or codesign --verify on that app to see what kind of code signature it has. That might shed some light here.
Looks like a standard Developer ID signed application. App isn't sandboxed. Ran it through the RB App Checker Lite.
If you are interested in checking it out further I'd just send you the link to download off the developer's website but there is no way to send private messages on these forums, and I'm not trying to put another developer on blast here...I just would like to know what exactly the policy is on this.
