Hey @femialiu ,
The message you're seeing - “the offering has no configured paywall” - usually means that the Offering you’re trying to display in the app isn’t linked to any paywall yet. In the new version of Paywalls flow, paywalls are no longer required to be attached to an offering at creation time, which can lead to this exact confusion.
This said, it’s also important to note that each Offering can only have one paywall linked to it. If all your existing offerings are already paired with other paywalls (like your older V1s), there won’t be any "available" to attach to your new paywall.
To resolve this, you’ll want to either:
- create a new Offering (you can duplicate an existing one to save time)
or - detach the current paywall from an offering if it’s no longer needed.
Then, go back to your new V2 paywall and attach it to that newly created or cleared Offering in the dashboard.
As an extra step, make sure that in your code you're fetching the correct Offering identifier (like "default" or the new one you just created). If your app is trying to display an offering that isn’t linked to a paywall, you'll keep seeing this error, even if the paywall is fully configured in the dashboard.
Hope this clears it up! Let me know if you have any more questions.
Best,
Gui