Pro across devices
| Platform | Status | Where |
|---|---|---|
| iOS | partial | vulture-ios/Modules/App/Sources/Services/Subscriptions/AppStoreSubscription.swiftRevenueCat user = CloudKit record name; Firebase uid planned (ios-changes A4). |
| Android | done | vulture-android/app/src/main/kotlin/be/fousa/vulture/accountRevenueCat user = Firebase uid after Google sign-in. |
Behaviour
Section titled “Behaviour”- On iOS the RevenueCat app user ID is the CloudKit user record name, so Pro follows the Apple ID across iPhone, iPad, Mac and Watch.
- On Android Pro follows the Google sign-in: the RevenueCat app user ID is the Firebase uid.
- One subscription for both platforms is the goal, but it is not built yet, so the apps make no cross-platform promise (P8-D8).
Platform differences
Section titled “Platform differences”- iOS still logs in to RevenueCat with the CloudKit record name. When iOS joins Firebase it will log in with the Firebase uid (ios-changes A4, P8-D14); only then can one subscription unlock both.
- The Firebase extension of RevenueCat puts a
revenueCatEntitlementsclaim on the ID token; the cloud storage rules read it.