Repository navigation
fix(remote_config,ios): emit onConfigUpdated events on the platform thread - #18673
Conversation
…hread Firebase's config-update listener is not guaranteed to run on the main queue, and Flutter rejects platform-channel messages from other threads.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Description
iOS
onConfigUpdatedcalledFlutterEventSinkdirectly from Firebase'saddOnConfigUpdateListenercallback, which is not guaranteed to run on the main queue. Flutter then warned thatplugins.flutter.io/firebase_remote_config_updatedsent a message on a non-platform thread.Copy the updated keys on the callback thread and hop the event onto
DispatchQueue.main, matching Android'smainThreadHandler.postand other Apple stream handlers. macOS shares this Swift file via symlink.Related Issues
Checklist
///).melos run analyze) does not report any problems on my PR.Breaking Change