Skip to main content
Question

Clarification on Offering Configuration Warning

  • March 19, 2025
  • 1 reply
  • 31 views

Forum|alt.badge.img

Hi,

I have set up multiple apps under a single RevenueCat project because I want a subscription purchased in one app to be valid across all my apps. I have configured my products accordingly.

Each app has its own offering page, and I have linked separate paywalls to each one.

However, when initializing RevenueCat in app1, I get the following warning:

[offering] WARN: ⚠️ There's a problem with your configuration. No packages could be found for offering with identifier app2_offering. This could be due to Products not being configured correctly in the RevenueCat dashboard, App Store Connect (or the StoreKit Configuration file if one is being used).
To configure products, follow the instructions in https://rev.cat/how-to-configure-offerings.
More information: https://rev.cat/why-are-offerings-empty

Similarly, when I launch app2, I get the same warning for app1_offering instead.

I believe this is happening due to my setup and is not an actual issue, but if that's the case, perhaps RevenueCat could improve this debug warning to better reflect such use cases.

I wanted to reach out both as feedback and to confirm whether there is any misconfiguration on my end.

Thanks in advance for your help!

1 reply

Forum|alt.badge.img+8
  • RevenueCat Staff
  • 521 replies
  • March 21, 2025

Hi ​@fnr can you open a support ticket here with the following information:

  • The apps you are seeing this with
  • Full RevenueCat debug logs for each app where you are getting this error, see our docs here for enabling these 
  • Screenshots of how your products are setup in App Store Connect for each app
  • The offerings you are seeing this with and the code you are using for fetching offerings

Also make sure to be logging in with a proper Apple sandbox tester as specified in our docs here.


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