• Community
  • Get Help
  • SDKs
  • Error: There is an issue with your configuration. Check the underlying error for more details.
Question

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

  • 11 January 2023
  • 11 replies
  • 199 views
A
Badge +2

Hey Everyone,

I have a problem, I get this Error when I try to fetch Products: 

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

This Happens with Android.

I tried to look up the problem but couldn’t find a specific solution. any help from anyone?

 

This is my code:

 

11 replies

H
Rank
Userlevel 3
Badge +8

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

A
Badge +2

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

H
Rank
Userlevel 3
Badge +8

Internal ticket opened, will post here with solution

H
Rank
Userlevel 3
Badge +8

Solved

N
Badge +3

Hi,

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

H
Rank
Userlevel 3
Badge +8

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 

N
Badge +3

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

T
Badge +1

@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.

N
Badge +3

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 :-)

O
Badge +3

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 :-)

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.

V

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 :-)

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

Reply


Terms & ConditionsCookie settings