-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flag is not returned correctly after updating user #19
Comments
@jeff-byrnesinnovation @jkodumal I know what the issue is. I will look and fix tonight. Thank you @argon |
Fixed in pull #20 |
I tried the code in #20 and I am still seeing the same problem. Further investigation shows that after calling |
I am seeing another coredata error related to events which is unrelated #21 . I will look into the config flags not updating. As far as the config values. Are you seeing them eventually update? I ran a quick smoke test swapping between :
I was outputting the flags in the log and they seemed correct to me. Is your case when you start from an anonymous user? Any additional info you give will help me isolate the issue. Thank you |
Ok I was able to reproduce the error (see attached log). Investigating now. It appears that the first time we switch users the updated config from the server is not being set. On subsequent calls it is reading from the persisted config object in coredata which is returning the correct values @argon can you confirm this is the issue you are seeing as well?
|
Version: 0.4.0-beta
Steps to reproduce:
toggle:<feature> default: false
for the feature and observe it is disabledtoggle:<feature> default: false
for the feature.Expected:
Actual:
Notes:
reponseObject
at https://github.com/launchdarkly/ios-client/blob/master/Darkly/RequestManager.m#L112 and after callingupdateUser
the response definitely contains1
for the flag I am looking at buttoggle
still returns false.The text was updated successfully, but these errors were encountered: