Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

No feature flags loaded after upgrade from 5.6.7 to 5.7.0 #258

Closed
yuzawa-san opened this issue Feb 4, 2022 · 3 comments
Closed

No feature flags loaded after upgrade from 5.6.7 to 5.7.0 #258

yuzawa-san opened this issue Feb 4, 2022 · 3 comments

Comments

@yuzawa-san
Copy link

Is this a support request?
No

Describe the bug
No feature flags loaded after upgrade from 5.6.7 to 5.7.0. There is an exception in the log (below).

To reproduce
Instantiate a client in version 5.6.7 and then instantiate at client in 5.7.0.
I am using a custom DataStore implementation, but the exception does not appear to be coming from there.

Expected behavior
The client should be filled with the feature flags.

Logs

2022-02-04 17:33:18,751 INFO okhttp-eventsource-stream-[]-0 com.launchdarkly.sdk.server.LDClient.DataSource info - Connected to EventSource stream.
2022-02-04 17:33:18,752 ERROR okhttp-eventsource-events-[]-0 com.launchdarkly.sdk.server.LDClient.DataSource onMessage - LaunchDarkly service request failed or received invalid data: com.launchdarkly.sdk.server.StreamProcessor$StreamInputException: com.launchdarkly.sdk.server.interfaces.SerializationException: java.lang.RuntimeException: Failed to invoke public com.launchdarkly.sdk.LDValue() with no args
2022-02-04 17:33:18,754 INFO okhttp-eventsource-stream-[]-0 com.launchdarkly.sdk.server.LDClient.DataSource info - Waiting 20760 milliseconds before reconnecting...

SDK version
5.7.0

Language version, developer tools
Java

OS/platform
Amazon Linux 2 x86_64

Additional context
5.6.7 dependencies:
image

5.7.0 dependencies:
image

is that launchdarkly-java-sdk-common causing issues? it appears there is a duplicate com.launchdarkly.sdk.LDValue in there:
image
this is not present in 5.6.7.

@gwhelanLD
Copy link
Contributor

Hi @yuzawa-san,

Thanks for reporting this issue. There was an issue with the packaging of the 5.7.0 SDK release we discovered yesterday that causes this error. We have an internal PR to address this issue, which we will release as a 5.7.1 release as soon as it has been reviewed and testing has been completed.

Sorry for the inconvenience,
@gwhelanLD

This was referenced Feb 4, 2022
@gwhelanLD
Copy link
Contributor

@yuzawa-san
Copy link
Author

This fix appears to work. Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants