-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Awaiting some calls does not timeout if there are network issues #282
Comments
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out! |
Hi @PAFriedrichMueller, |
There aren't really any logs as the call never returns but here is a minimal example https://github.com/PAFriedrichMueller/RevCatIssue/ and this is all i get in the js console
in my example repo there should be at least some console output from this code
but since there is no network connection/the request are blocked/timed out the call seems to never return |
i guess there is this form the android logs
|
I'm having the same issue but with Purchases.getOfferings() will not fulfill or reject the promise |
i think it happens for almost all network calls especially if there is no cache available |
this does not allow me as a customer to view the progress on the issue does it ? |
Calling getCustomerInfo like this
will not fulfill or reject the promise if there are network problems on android
usually this will just return the cached version afaik but if you start the app for the first time on android and all network traffic
is blocked (not disconnected)
The text was updated successfully, but these errors were encountered: