Restarting the client with a different mobile key

[molnarr2]

Having a production and a test environment we need to switch between those two within the app without having to restart the app. There is currently no way to do that. This functionality is built into the iOS mobile version.

[irwinb]

Similarly, we sometimes do not know every single user attribute at startup. It useful if we could re-initialize the LdClient. We understand the implications of initializing the client more than once, but there is no ability to do that right now.

1. Initialize client.
2. Use client to query feature flags
3. Some user interaction introduces a new attribute
4. Re-initialize client

[eli-darkly]

@irwinb The user attributes can be changed at any time with Identify() or IdentifyAsync().

@molnarr2 Do you mean you want to switch the entire app from one environment to the other - so that the single static instance of LdClient is now using a different key - or keep them both active and use the production flags for some things, but the test flags for others, in effect maintaining two client instances?

[molnarr2]

The first case where the single static instance of LdClient is using a different key.

[bwoskow-ld]

Hi @molnarr2,

You're referring to the multiple environments functionality in the iOS and Android SDKs. We'll let you know when this functionality is added to the Xamarin SDK.

[mchan-genetec]

Is there any update on the progress for this feature request? I am also in need of this functionality for the mobile sdk. From the Xamarin SDK doc it is stated that we can call Dispose with the following call ldClient.Dispose(); however through inspection it does not seem Dispose is marked as public. I am using LaunchDarkly.Xamarin 1.0.0-beta16. Thanks.

[eli-darkly]

@mchangenetec If you're using beta16, you're more than 4 months out of date. The documentation describes the most recent beta release, in which LdClient implements IDisposable. Many other features have changed and bugs have been fixed in the last four months, so if you're working on implementing something with the Xamarin SDK it's highly advisable to stop using that version.

[eli-darkly]

@mchangenetec Note that the package name changed after beta16 - it is now LaunchDarkly.XamarinSdk. Unfortunately there was no way for us to make that information visible on the NuGet page for the old package, but it was mentioned in the release notes on Github. I highly recommend reading through the release notes since there have been quite a few changes since beta16.

[eli-darkly]

We are getting close to general release so we're hoping to avoid any more breaking API changes at this point.

[theboyknowsclass]

any progress on this?

[eli-darkly]

The 2.0 release is coming soon, but the multiple environments feature will not be in it. We may add support for that in the future, but there were a lot of other improvements we had to prioritize for 2.0.

[theboyknowsclass]

It seems that calling dispose and re-initialising the client works in the rc Sent on the go. Apologies for typos and brevity

…

________________________________ From: Eli Bishop ***@***.***> Sent: Thursday, January 6, 2022 7:09:01 PM To: launchdarkly/dotnet-client-sdk ***@***.***> Cc: theboyknowsclass ***@***.***>; Comment ***@***.***> Subject: Re: [launchdarkly/dotnet-client-sdk] Restarting the client with a different mobile key (#8) The 2.0 release is coming soon, but the multiple environments feature will not be in it. We may add support for that in the future, but there were a lot of other improvements we had to prioritize for 2.0. — Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Flaunchdarkly%2Fdotnet-client-sdk%2Fissues%2F8%23issuecomment-1006845322&data=04%7C01%7C%7C29e2c64cec084ac8b31608d9d1480046%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770929429618883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=m2m35aAajfRjc5AQeqepFNhT4i6RFuQmWcXa1a2Hel0%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fnotifications%2Funsubscribe-auth%2FAAQKOJNZUTCH3EMJPA3SOJLUUXSE3ANCNFSM4GQPNHTQ&data=04%7C01%7C%7C29e2c64cec084ac8b31608d9d1480046%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770929429628841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wJe38tuW06jPvVdHBzw5YP9Vc%2FOf7WoyQ%2BaGv%2FxvNGQ%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7C29e2c64cec084ac8b31608d9d1480046%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770929429628841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=iHxaG%2FtqrE1o0yuh5%2F0SRui2fLnM5y9bQRp4lQlJ8mo%3D&reserved=0> or Android<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7C29e2c64cec084ac8b31608d9d1480046%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637770929429638797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZwykXwEfI2E5zKVGw41FQH1O2Y0%2BgTWM%2FpkrCPLnKXU%3D&reserved=0>. You are receiving this because you commented.Message ID: ***@***.***>

[mjkkirschner]

It seems that calling dispose and re-initialising the client works in the rc

I am curious about this - is this a supported workflow in version 2.0.1 client sdk? I am using launch darkly in a plugin architecture, where I do not control the process lifetime and the plugin may be restarted multiple times - is it safe to dispose and re initialize the client, or does it make more sense to simply forgo the shutdown?

[eli-darkly]

@mjkkirschner Sure, it's always safe; it's just mildly inefficient because it will have to make a new HTTP connection each time, and also each time you shut it down it will have to do a blocking HTTP request to deliver any pending analytics events.