[FCM] Fix ANR in SharedPreferencesQueue by reducing lock contention

[xiaohegong]

Change SharedPreferences.Editor.commit() to apply() in SharedPreferencesQueue.syncState().

Previously, the synchronized block held the lock while performing a synchronous commit(), which could block the background thread on disk I/O. If the main thread attempted to access the queue (e.g., in add()), it would block waiting for the lock, leading to ANRs.

By switching to apply(), the operation updates the in-memory SharedPreferences immediately and schedules the disk write asynchronously. This avoids blocking on disk I/O while holding the lock, significantly reducing lock contention and preventing ANRs. Keeping it inside the synchronized block ensures that updates are applied in the correct order even if called from multiple threads.

[gemini-code-assist]

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize 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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. 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.