“Identifying Users” is listed as a developer responsibility in https://docs.revenuecat.com/docs/implementation-responsibilities
Using apple’s CKContainer CKRecord.Id as and iOS in-app purchase identity seemed like a no-brainer...but is there a "better" method for this. I see there is identy merge behavior in RevenueCat for anonymous user ids, but does this solve the issue on its own?
The app I'm developing has zero-need for a user account, other than supporting review guideline [3.1.3(b) Multiplatform Services], the use of the CKRecord.Id seems like it would be a perfect, frictionless way to achieve subscription persistence across devises, since it persists the same value across all of the users devices without bothering the user... except for the quirk - of requiring "iCloud Drive" to be enabled. Which make total sense if you are looking to save documents to iCloud. but..I don’t need that part.
This all feels like reinforcement of the notion that using this service in this way should not be done. However setting up “Sign-In with Apple” seems like complete overkill.
How have others approached this issue? Any suggestions would be awesome.
Thank you all!
Best answer by ryanView original