client.configure does not resolve inside the Android Emulator

[emin93]

Describe the bug
Calling client.configure does never resolve when called in the Android Emulator but does so on a real device.

To reproduce

const client = new LDClient();

console.log('configuring LaunchDarkly'); // This is being logged into the console

await client.configure(
    { mobileKey: 'abc-123' },
    { key: 'example-user' }
);

console.log('configured LaunchDarkly'); // This never shows when run inside the Emulator

Side note
When putting the app into the app switcher, the promise resolves but allFlags() returns an empty object instead of the flags.

Expected behavior
configure resolves also in the Emulator.

SDK version
5.1.0

OS/platform
Android Emulator

[louis-launchdarkly]

Hello @emin93, thank you for reporting this issue. We will investigate the issue to understand why you see this behavior.

Filed Internally as 136994

[gwhelanLD]

Hi @emin93,

We've been unable to reproduce this issue ourselves with the Android emulator. If the promise is not resolving it may be due to an inability to connect to the LaunchDarkly service. When the app detects it has moved to the background by opening the app switcher, it moves into background mode and will no longer wait for a connection to complete the promise. Could you verify whether your application has network connectivity to LaunchDarkly services when run on the Android emulator?

Thanks,
@gwhelanLD

[hannahla97]

Hi @gwhelanLD,

I'm experiencing the same issue. While debugging I found out that the SDK cannot connect to LD service at all. It only happened for Android. I would like to know what is the solution for this.

const init = async (user: LDUser) => {
  const config: LDConfig = {
    mobileKey: featureKey
    connectionTimeoutMillis: 10000,
  }

  await LaunchDarklyClient.configure(config, user)
}

useEffect(() => {
    init(user).then(() => {
      //Never reach this
    }). catch(e => {
     //Also never reach this
    })

    return () => {
      LaunchDarklyClient.close()
    }
  }, [])

Best regards.

[gwhelanLD]

Hi @hannahla97,

Could you let us know what version of the Android emulator and Android OS you are testing with ?

One test that may help us narrow this down is to disable the streaming functionality of the SDK. Sometimes, network security configurations, proxies, or other networking configurations can cause issues preventing streaming connections from working correctly. Could you try setting the stream configuration option to false and check whether the promise of the .configure call completes?

Thanks,
@gwhelanLD

[fabriciosautner]

Same problem on iOS simulator

[louis-launchdarkly]

Hello @fabriciosautner, to follow up on this issue - were you able to reproduce the issue using either the ManualTestApp or the hello-react-native repo?

I just verified again that the ManualTestApp is working correctly on the iOS emulator. Comparing that with your code may give you some difference to help identify what is causing the "does not resolve" issue for you.

[kengjin]

One test that may help us narrow this down is to disable the streaming functionality of the SDK. Sometimes, network security configurations, proxies, or other networking configurations can cause issues preventing streaming connections from working correctly. Could you try setting the stream configuration option to false and check whether the promise of the .configure call completes?

I was seeing the same issue of configure() not resolving in the iOS simulator and setting stream to false as suggested by @gwhelanLD fixed the issue for me ❤️