Skip to content

Fix the issue where third-party apps encounter "Invalid argument for … #2954

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

Merged
merged 4 commits into from
Jul 17, 2025

Conversation

DaVinci9196
Copy link
Contributor

Fix the issue where third-party apps encounter "Invalid argument for the given fid" when registering with GCM.
Reproduction Steps:

  1. In microG, allow a third-party app (e.g., WhatsApp, Messenger) to register with GCM.
  2. Go to the app info page and clear microG’s app data. At this point, the previously registered GCM entries are lost, and the Android ID is reset.
  3. When the third-party app triggers GCM registration again, an error occurs:
    “Invalid argument for the given fid”, causing GCM registration to fail.

Common triggers for re-registration include:

  • Updating the third-party app
  • Reopening the third-party app

@mar-v-in mar-v-in added this to the 0.3.9 milestone Jul 2, 2025
@mar-v-in
Copy link
Member

I worry that this could accidentally unregister apps from push notifications, potentially doing more harm than use in some cases. Could you tie this unregister+reregister to this specific error message instead?

@mar-v-in mar-v-in merged commit 7005be4 into microg:master Jul 17, 2025
1 check passed
@DaVinci9196 DaVinci9196 deleted the gcm_invalid_argument_fid branch July 18, 2025 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants