You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering what the recommended way is to use Firebase Remote Config with Swift Concurrency.
Specifically:
Is it safe to call methods like fetchAndActivate() from a non-MainActor context, or should these APIs always be used on the main actor?
Is it safe to read Remote Config values from a non-MainActor context, or are there any thread-safety considerations?
At the moment I'm importing FirebaseRemoteConfig using @preconcurrency to silence concurrency warnings/errors, but I'm not sure if that reflects the intended usage or if I should instead isolate access (e.g. behind @MainActor or an actor).
Any guidance on the expected concurrency model for Remote Config would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm wondering what the recommended way is to use Firebase Remote Config with Swift Concurrency.
Specifically:
Is it safe to call methods like
fetchAndActivate()from a non-MainActor context, or should these APIs always be used on the main actor?Is it safe to read Remote Config values from a non-MainActor context, or are there any thread-safety considerations?
At the moment I'm importing
FirebaseRemoteConfigusing@preconcurrencyto silence concurrency warnings/errors, but I'm not sure if that reflects the intended usage or if I should instead isolate access (e.g. behind@MainActoror an actor).Any guidance on the expected concurrency model for Remote Config would be greatly appreciated.
Best,
Viktor
Beta Was this translation helpful? Give feedback.
All reactions