-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Remote Config Dynamic Property Wrapper #10155
Conversation
* Fix retry logic to respect max retry count * Rename to isRequestInProgress
Coverage Report 1Affected Products
Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, had a few small comments.
FirebaseRemoteConfigSwift/Apps/SwiftUISample/SwiftUISample/ContentView.swift
Outdated
Show resolved
Hide resolved
FirebaseRemoteConfigSwift/Sources/PropertyWrapper/RemoteConfigValueObservable.swift
Outdated
Show resolved
Hide resolved
FirebaseRemoteConfigSwift/Sources/PropertyWrapper/RemoteConfigValueObservable.swift
Show resolved
Hide resolved
Ignore the test failure since it's something we need to fix in the infra. |
Hi @chliangGoogle, I re-ran 40804aa's CI and PTAL at the results here: The 429 errors are gone, but there are 4 failures. Are these the failures you've been seeing? |
@ncooke3 yeah these are the same failure we've seen and we've run them successfully locally. |
…ted by other tests
… the config data in api test that affecting the results to be inaccurate
* [Firebase 10] Bump 9.X versions to 10.0.0 * Bump min. GTMSessionFetcher dep version to 2.1 * Bump min. GDT dep version to 9.2 * Bump min. GULs dep version to 7.8 * Fix unintentional nanopb replace * Fix unintentional nanopb replace (2) * Fix unintentional nanopb replace (3) * Fix unintentional nanopb replace (4) * Fix unintentional nanopb replace (4) * Trigger all CI * Bump FirebaseCombineSwift to 10 * Fix FirebaseStorage.podspec I'm not sure what happened here. I had committed it during the rebase but guess not? * Fix unintentional nanopb replace (5) * Disable two tests to unblock staging * Fix and re-enable FIROptions tests * Update deployment targets in Firebase.podspec * Add CHANGELOG entry for GTMSessionFetcher * Fix AppCheck iOS availability * Fix inadvertent API change (#10245) * Docs update for Extensions and putFile (#10248) * App google domain support (#10249) Adding new 1p domain "app.google" support in FDL SDK. * Remote Config Dynamic Property Wrapper (#10155) * Separate GoogleUtilities Carthage build (#10250) * Public count (#10246) * Public Count * Swift Test Commit * Swift Format * No extra whitespace * Hopefully formatted. * Change log and feedback. * Revert "Public count (#10246)" (#10252) This reverts commit 8aae6be. * Make Firestore use FirebaseDataEncoder and FirebaseDataDecoder (re-implementation of #8858) (#9465) * Bump tvOS minimum support version to 12.0 * [skip ci] Revert Gemfile Co-authored-by: Paul Beusterien <paulbeusterien@google.com> Co-authored-by: Eldhose M Babu <eldhosembabu@google.com> Co-authored-by: Charlotte Liang <chliang@google.com> Co-authored-by: wu-hui <53845758+wu-hui@users.noreply.github.com> Co-authored-by: Morten Bek Ditlevsen <bek@termestrup.dk>
Added the new API that enables developers to define a property wrapper that listens to a remote config key value. When remote config is activated, the UI component will automatically reflect the activated value.