-
Notifications
You must be signed in to change notification settings - Fork 11
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
Documentation on how to setup the FlagValueSource
as a shared UserDefaults
from the "Settings" app
#115
Comments
Hi @will-lumley - how are you mate? I am in a new app projec, where I am too keen to use Vexil with feature flags manager. All docs working fine, understood the steps needed, and I managed to setup app-group to share UserDefaults between two app targets. But I ended up having the same issue that settings app does not let me change the flag values. And get stuck. You remembered how we managed that buggy issue in our plus app? Thanks mate, some tips (I just forgot how to) would really help me. 🙏🏽 cc- @bok- |
As first step, I managed to include the Vexilographer based SwiftUI view in the main app But as next next step, I tried to take that part out in a dedicated eg. I have used
But got into this stuck situation. I did a a few troubleshooting like (my app's min deployment iOS is 15)
|
Actually, I have got it working now. 😀 Seems like I missed a step to attach the source precisely at one point. Before: (not working :( )
After: (working :) )
|
@arinjoy Glad you got it working. I am working on my own app on the side and ran into this exact issue - hence why this issue which I raised that advocates for clearer documentation. |
In the documentation it is stated that we recommend that the view/Vexillographer be contained in its own app.
This requires the user to setup an App Group, and then set the source in both the seperate app/target and in the app to be the shared UserDefaults file. While not super tricky to implement, I feel like it'd be nice to provide documentation on how to do that.
Happy to do it myself but wanted to flag (heh) the idea here first in case there's a reason why we shouldn't.
The text was updated successfully, but these errors were encountered: