Open hasanfd opened 6 months ago
Hi, @hasanfd! Most of the time, this error indicates some form of misconfiguration of your products within AppStore Connect or the Adapty Dashboard. I suggest double-checking all the products and their states. If you continue to encounter this error, please contact our support team via support@adapty.io, they will assist you further.
Hello, Even though,
In addition to this, I have a new error in android,
`#103 (undefined): Play Market request failed: Google Play In-app Billing API version is less than 3
Can you help me?
I see this error intermittently on iOS in the field. Our app store and Adapty config are not changing. It seems sometimes Adatpy's cache or its ability to talk to its server results in this error, I am not sure. Regardless, this is a live bug.,We see purchases succeed but we also see this via Sentry:
The app is otherwise making http requests just fine. Here's a stack trace from sentry 👍
Given the error that is reported is patently wrong - (the adapty/.store config is fine) , it seems this is some other error that should be reported by the adapty client failing to request or parse the results from its servers. The error handling code in native-request-handler.js (or what it depends on) is likely at fault.
I meet this error too. Anything update?
I have the same problem even though I have configured everything according to the documentation.
In my case, apple update agreement so in app purchase is stuck. Just need accept new agreement and wait about 2 hour to active product
Thanks for sharing @khanhkom, but I just double-checked, and all my agreements are active. Additionally, there are no errors on the TestFlight app; this is only happening on production as far as I can see.
Update about my issue: I realized my subscription was stuck "in review" but now it's resolved. So, mine was not related to Adapty.
I am seeing this error in iOS production sometimes. What could be the root cause of this? I think there could be a bug in adapty client. Thanks
#1000 (noProductIDsFound): No In-App Purchase product identifiers were found.