Error: There is an issue with your configuration. Check the underlying error for more details.

This error is not related to your code, instead your configuration. Can you send our SDK’s full debug logs of this so we can see the underlying error? Please see here for how to enable them: https://www.revenuecat.com/docs/debugging#section-debugging

But I’m confused, the debugLogsEnabled is on the code and I still get the simple message, so what can I do?

Internal ticket opened, will post here with solution

Solved

Hi,

Exact same issue here. Any way to get some help? 😁

This error is usually from product identifier mismatch or unsupported features of Google Play's new subscription model. You want to make sure your product ids match between Google Play and RevenueCat, that all your products are marked with the “Backwards compatible” tag, and that you only have one base plan per subscription. See here: https://www.revenuecat.com/docs/android-products 

[edit] Solved by myself, was an issue on my side.

@NotAlex I am also encountering this issue. Do you think your solution is generally useful or was it specific to your use case? I have confirmed that my Android subscriptions are backwards-compatible and am still getting this configuration error.

Hi,

To be honest, I don’t know. The least I can say is that I used this to get more details about the issue :

console.log(JSON.stringify(e));

Hopefully it can help :-)

console.log(JSON.stringify(e));

That’s really helpful actually.

@ RevenueCat team, it would be great if you could adjust the error stringification so that with `console.log(err)` it also prints the error’s `userInfo.underlyingErrorMessage` text, as this is where the actual error message is hidden.

console.log(JSON.stringify(e));

With this line of code you saved my life bro, I was going crazy to better understand my problem.

loooks like offerings are mandatory and not optional as the documentation says
{"nativeStackAndroid":[],"userInfo":{"underlyingErrorMessage":"There are no products registered in the RevenueCat dashboard for your offerings. If you don't want to use the offerings system, you can safely ignore this message. To configure offerings and their products, follow the instructions in https://rev.cat/how-to-configure-offerings.\nMore information: https://rev.cat/why-are-offerings-empty","readableErrorCode":"ConfigurationError","readable_error_code":"ConfigurationError","message":"There is an issue with your configuration. Check the underlying error for more details.","code":23},"message":"There is an issue with your configuration. Check the underlying error for more details.","code":"23"}

what I don’t understand is that offering needs a package and a package needs a product. but my products are consumables, I dont need to categorize them in a package, it’s a one time purchasE!

loooks like offerings are mandatory and not optional as the documentation says
{"nativeStackAndroid":[],"userInfo":{"underlyingErrorMessage":"There are no products registered in the RevenueCat dashboard for your offerings. If you don't want to use the offerings system, you can safely ignore this message. To configure offerings and their products, follow the instructions in https://rev.cat/how-to-configure-offerings.\nMore information: https://rev.cat/why-are-offerings-empty","readableErrorCode":"ConfigurationError","readable_error_code":"ConfigurationError","message":"There is an issue with your configuration. Check the underlying error for more details.","code":23},"message":"There is an issue with your configuration. Check the underlying error for more details.","code":"23"}

Facing same issue. 

Indeed, it does seem that Offerings is mandatory. As soon as I added an offering everything worked like I was expecting (following this tutorial https://www.youtube.com/watch?v=noTeDJypcqY&t=995s).

Welp, unfortunately I ran into this same issue with Android but fortunately adding it to the Offering fixed it yet again! Too bad it took me a day or two to find this thread again and see that I posted the same thing about iOS 🤦‍♂️

Having something like this in the docs would be really helpful.