Skip to main content
Solved

Error with Product Identifiers - iOS

  • 3 November 2021
  • 3 replies
  • 138 views

Forum|alt.badge.img+3

My app works with the subscription and RevenueCat. However I get an error with the following:

2021-11-03 07:29:01.912 seed2021[68531:4997387] [Purchases] - WARN: 🍎‼️ Invalid Product Identifiers - (
    801,
    901
)

 

Initially when I had configured RevenueCat, I had two additional products added for iOS for the inApp purchase, and the products added to RevenueCat. Over time I decided to remove these (801,901) from iOS and also from RevenueCat. 

However, I get this warning that appears RevnueCat still has these cached somewhere and I don’t know how to remove these to get rid of the error.

Best answer by cody

The RevenueCat SDK will briefly cache offerings, and re-fetch them on app launch, so it’s failing to fetch those products still. Are you still encountering this error after re-fetching offerings (I’d recommend doing this often, each time you want to display your paywall) and/or a new installation? It might take some time for the cache to be updated.

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

tina
RevenueCat Staff
Forum|alt.badge.img+10
  • RevenueCat Staff
  • November 3, 2021

Hey @Brian Remington 

You should check if you have those values hard coded anywhere. Also, if you’re using StoreKit configuration files, ensure that those products are removed from the file. 


Forum|alt.badge.img+3

Hi Tina,

I do not have it hard coded anywhere in my app. The error is from calling Purchases.getofferings

 

I am also not using Storekit config files. My initial thoughts was a file RevenueCat built that the Purchases.getofferings action pulled, and this had the initial products, but is not getting updated from RevenueCat.


cody
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • December 16, 2021

The RevenueCat SDK will briefly cache offerings, and re-fetch them on app launch, so it’s failing to fetch those products still. Are you still encountering this error after re-fetching offerings (I’d recommend doing this often, each time you want to display your paywall) and/or a new installation? It might take some time for the cache to be updated.


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