configure() never returns

[ciriousjoker]

• Same issue as here: #23
• The call back is never called. I tested it on iOS and Android.
• retrieveProducts() works, so I assume that configure() also does

This is in the logs:

Note: pre-requisites configuration is mandatory for SDK to work. Learn more(https://www.chargebee.com/docs/2.0/mobile-app-store-product-iap.html)

Is this normal? If I remember correctly it is, but I'm not sure.

[cb-amutha]

Hi @ciriousjoker This is normal flow of configuration method. It doesn’t provide the callbacks, just verify app details with Chargebee. is there any specific reason looking out for the callback?

[ciriousjoker]

I'm trying to use it like this:

try {
  await configure();
  // Log if it worked
} catch (e) {
  ...
}

Currently, it seems like it will throw and if it doesn't throw, that means everything went smoothly?

What if the user has no internet connection? In that case it failed silently because the network request never completes.

[cb-amutha]

In Android, if no internet connection it should throw error, this use case has been handled. can you please check and confirm?. for iOS, will update the sdk to handle this scenario. Thanks.

[ciriousjoker]

During my testing, it did throw an error, but network requests are really hard. Sometimes there is a working wifi connection or 3G connection, but due to high package loss the bytes basically come in one by one. Is there a timeout for such cases at which point the request is considered "failed"?

[cb-amutha]

During my testing, it did throw an error, but network requests are really hard. Sometimes there is a working wifi connection or 3G connection, but due to high package loss the bytes basically come in one by one. Is there a timeout for such cases at which point the request is considered "failed"?

The SDK doesn't specified timeout explicitly for now and the default connect time out that Retrofit gives between 10s and 15s.

[cb-amutha]

In Android, if no internet connection it should throw error, this use case has been handled. can you please check and confirm?. for iOS, will update the sdk to handle this scenario. Thanks.

We have updated the sdk that throws an error in case of failure during configure() method in both iOS and Android. Please check and let us know if running into issue around this method. Thanks.