Replies: 2 comments 3 replies
-
Hi @ShurikAg, Sorry for the long waiting time. Our Java SDK should not work inconsistently. I suspect that the userId is not allways set when the Java SDK evaluates the toggle. Is it possible for you to log that userId to test if that is the issue? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Hey @ShurikAg I'll close this for now as it seems things have worked out for you. But if you have more questions feel free to open a new issue! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have recently implemented feature flagging in our app (based on self-hosted Unleashed).
React side works perfectly as expected. However, the server-side (written in grails) is giving wrong results every now and then. It is inconsistent. I am not even sure where to start debugging it, but I am sure it is something in our code.
On another note: on local everything works as expected :(
Here is our setup in Unleash
API Keys:
One of the feature keys setup:
Related code on the backend
Controller wrapper:
Unleash service:
UnleashContextProviderService:
UnleashClientProviderService:
Basically, what happens is it always returns the correct result on Fronend (in React). However, in most cases, the code above returns false, even if the feature is enabled.
The code is super simple and follows the docs. Maybe something in the configs in Unleash.
I am totally lost.
Beta Was this translation helpful? Give feedback.
All reactions