Invalid Product Identifiers

  • 21 December 2021
  • 1 reply

Badge +1


We are currently receiving an error fetching Offerings with the RevenueCat SDK on iOS (SDK Version - 3.13.0).

From searching and reading the ‘Why are offerings or products empty?’ support document, we have confirmed we are seemingly matching all of the requirements:

  • We have agreed to the latest App Store Paid agreement in App Store Connect.
  • We have created a In-App Purchase Subscription in App Store Connect that is a 1-month auto-renewing subscription. This In-App Purchase Subscription status is marked as ‘Ready to Submit’ in App Store Connect.
  • We have a matching Product created within RevenueCat, and have verified it’s identifier matches the Product ID in App Store Connect.
  • Within RevenueCat, the Product is associated with the correct Entitlement, and the only Offering we have contains 1 Package with this Product.
  • We are not using a StoreKit Configuration file.
  • We have enabled the In-App Purchase capability in the Xcode project settings.
  • We are testing on device.

After requesting the packages, we are seeing the console log the ‘WARN: 🍎‼️ Invalid Product Identifiers’ warning, with the product identifier in question listed in the array. Again, we confirmed this value matches both App Store Connect and RevenueCat configuration.

A prior response from the RevenueCat support team stated that when receiving this Invalid Product Identifiers warning, it is likely a configuration issue outside of RevenueCat. This seems to be true as everything works as expected when we use a StoreKit Configuration file with the same product identifier in question.


Is there any additional debugging steps / gotchas / error messages that might be helpful here? From what we can tell, we satisfy all of the requirements for testing an IAP Subscription on iOS but we are still unable to fetch packages without using a local StoreKit Configuration file.


Best answer by Stephen Heaps 22 December 2021, 23:10

View original

1 reply

Badge +1

The issue described above has been resolved. We needed to complete the tax forms for paid apps on App Store Connect.