Skip to content
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

allFlags var on LDClient returning empty dict in case of app launched in offline, after app upgrade #431

Closed
karolkulesza opened this issue Feb 13, 2025 · 3 comments
Labels
Stale waiting for feedback Indicates LaunchDarkly is waiting for customer feedback before issue is closed due to staleness.

Comments

@karolkulesza
Copy link

karolkulesza commented Feb 13, 2025

Description
allFlags var on LDClient is returning empty dictionary, in case of app launched in offline for the very first time after app upgrade.

To reproduce

  1. Launch the app and make sure that the LD flags are cached
  2. Update the app to a newer version (either via TestFlight or by manually running via Xcode), so that the bundle id changes
  3. Go offline on that device
  4. Launch the app for the first time after the upgrade, in offline mode

Expected behavior
allFlags var on LDClient should return cached values, currently it returns empty dictionary.

Library version
9.12.2

XCode and Swift version
XCode 15.2

Platform the issue occurs on
iPhone, iPad

@keelerm84
Copy link
Member

keelerm84 commented Feb 13, 2025

Thank you for bringing this to our attention. We will let you know once we have a resolution for you!

Tracking internally as SDK-1069

@keelerm84
Copy link
Member

Thank you again @karolkulesza for raising this issue.

The SDK cache is keyed on the bundle identifier. It is my understanding that the identifier doesn't typically change.

Can you please provide more information about your use case, and why the identifier frequently changes?

@keelerm84 keelerm84 added the waiting for feedback Indicates LaunchDarkly is waiting for customer feedback before issue is closed due to staleness. label Feb 13, 2025
Copy link
Contributor

This issue is marked as stale because it has been open for 30 days without activity. Remove the stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 16, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale waiting for feedback Indicates LaunchDarkly is waiting for customer feedback before issue is closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants