I was debating doing that but it adds another layer of complexity support wise.It's possible for the user (via the iCloud tab in Settings) to disable iCloud document storage on a per app basis. If they turn off access for my app, the appearance is the same as if they are not logged in - the ubiquityIdentityToken is then nil. I could provide an alert that says You must be logged in to iCloud and have the app enabled in Settings etc - I'll think about this approach.In the meantime I'm going to handle this as follows:Store the data I need in the iCloud key/value store (KVS) - if the user is logged into iCloud (and from polling my test users, it seems at this will be the typical case) then I'm done and data will automatically get propagated to the user's other devices the moment they run the app. No app receipt refresh etc required.On the first purchase, remind the user that they must be logged into iCloud to access the subscription on their other device(s)On my support web pages for the app, include an FAQ about
Topic:
App & System Services
SubTopic:
StoreKit
Tags: