Skip to main content
Solved

Upgraded to Xcode 13 RC, and latest RevenueCat package, and now Purchases won't work with watchOS.

  • September 16, 2021
  • 2 replies
  • 1566 views

Forum|alt.badge.img+3
  • Helper
  • 3 replies

I have an independent watch app on the store as part of a family of apps. The watch app is part of a single project with the iOS app. After I upgraded Xcode, my app will no longer recognize the Purchases(now RevenueCat) package. I am using a single class that manages the purchases. If I have it as part of the watch extension it throws errors. If I only target the iOS app, the errors go away. The errors all essentially amount to:

'PurchaserInfo' is not a member type of class 'RevenueCat.Purchases'

I am also showing an error of

Watch Extension.build/Objects-normal/arm64_32/Settings.dia:1:1: warning: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Watch Extension'…

Steps I have done:

  1. Make sure that the package is linked to the extension
  2. cleared the derived data, cleaned the project and restarted.

I can find no setting that seems to be a problem. Any help would be appreciated.

Best answer by sharif

This question received an answer on StackOverflow:

This is one of the changes in purchases-ios version 4.0.0. The type Purchases.PurchaserInfo has been updated, it's now just PurchaserInfo (you can also refer to it as RevenueCat.PurchaserInfo).

The update is documented in the following link:

https://github.com/RevenueCat/purchases-ios/blob/4.0.0-beta.1/docs/V4_API_Updates.md#type-changes-for-swift

There are more changes along the same lines, like Purchases.Offerings -> OfferingsPurchases.package -> package.

Updating those should help with the migration.

If you're not ready to migrate yet, you can also stick with version 3.12.4 until you're ready.

View original
Did this post help you find an answer to your question?

2 replies

sharif
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • 513 replies
  • Answer
  • September 20, 2021

This question received an answer on StackOverflow:

This is one of the changes in purchases-ios version 4.0.0. The type Purchases.PurchaserInfo has been updated, it's now just PurchaserInfo (you can also refer to it as RevenueCat.PurchaserInfo).

The update is documented in the following link:

https://github.com/RevenueCat/purchases-ios/blob/4.0.0-beta.1/docs/V4_API_Updates.md#type-changes-for-swift

There are more changes along the same lines, like Purchases.Offerings -> OfferingsPurchases.package -> package.

Updating those should help with the migration.

If you're not ready to migrate yet, you can also stick with version 3.12.4 until you're ready.


Forum|alt.badge.img+3
  • Author
  • Helper
  • 3 replies
  • September 21, 2021

Sharif,

Thanks. Yes it did. I asked the question on SO as well. I should have cross posted the answer.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings