HB9TNZ
June 15, 2025, 3:24pm
1
Hi there,
i switched now to a flip 6 with android 15. before i used hamalert without any issues. Great thing! Now when starting up, i do get
“Push registration failed - Make sure that this app has permission to use push notifications. Error: java.util.concurrent.ExecutionExce???java.IOException: Invalid argument for the given fid.”
So i reinstalled the app without success
I saw an article regarding whitelisting, but i did not get the point what to do.
Anybody had the same issue and fixed it?
73 HB9TNZ
KK4KFG
June 15, 2025, 5:00pm
2
Seeing similar behavior. Have been unable to resolve so far
HB9DQM
June 15, 2025, 5:12pm
3
Hmm, I’m not sure what to suggest. Push notifications work fine for me in Android Emulator with an Android 15 image. Searching the net for the mentioned error turns up two issues filed in the Firebase Android project by other people experiencing the same issue, but no solution so far. Although given that it magically resolved itself for one developer experiencing it in April with many users, without them having done anything, there is hope that it’s just some temporary fluke on Google’s server side that will hopefully resolve itself soon…
opened 11:03PM - 25 Apr 25 UTC
closed 12:53PM - 28 Apr 25 UTC
api: messaging
### Environment
* Android Studio version: 2024.3.1 Patch 2 Meerkat
* Fireba… se Component: Firebase BOM 33.13.0
* Component version: com.google.firebase:firebase-messaging 24.1.1
### The problem
We are seeing a large increase in the following error:
IOException: Invalid argument for the given fid. (stack trace below)
This started happening at around April 15 with no changes to the client side code. Here is a screenshot from Crashlytics:
<img width="307" alt="Image" src="https://github.com/user-attachments/assets/12831502-c0b6-4e98-947e-dd261738b46e" />
It only reproduces on a small % of devices and I cannot reproduce locally. The users that have hit this issue say that it doesn't occur on all their devices. On the devices where the issue occurs, re-installing the app does not fix the issue.
### Relevant code
```
FirebaseMessaging.getInstance().token
```
Stack Trace:
```
Non-fatal Exception: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: Invalid argument for the given fid.
at com.google.firebase.messaging.FirebaseMessaging.blockingGetToken(FirebaseMessaging.java:665)
at com.google.firebase.messaging.FirebaseMessaging.lambda$getToken$7(FirebaseMessaging.java:420)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@18.5.0:2)
at java.lang.Thread.run(Thread.java:1012)
```
```
Caused by java.util.concurrent.ExecutionException: java.io.IOException: Invalid argument for the given fid.
at com.google.android.gms.tasks.Tasks.zza(com.google.android.gms:play-services-tasks@@18.1.0:5)
at com.google.android.gms.tasks.Tasks.await(com.google.android.gms:play-services-tasks@@18.1.0:9)
at com.google.firebase.messaging.FirebaseMessaging.blockingGetToken(FirebaseMessaging.java:663)
at com.google.firebase.messaging.FirebaseMessaging.lambda$getToken$7(FirebaseMessaging.java:420)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@18.5.0:2)
at java.lang.Thread.run(Thread.java:1012)
```
```
Caused by java.io.IOException: Invalid argument for the given fid.
at com.google.firebase.messaging.GmsRpc.handleResponse(GmsRpc.java:309)
at com.google.firebase.messaging.GmsRpc.lambda$extractResponseWhenComplete$0(GmsRpc.java:320)
at com.google.android.gms.tasks.zzc.run(com.google.android.gms:play-services-tasks@@18.1.0:3)
at com.google.android.gms.tasks.zzd.zzd(com.google.android.gms:play-services-tasks@@18.1.0:1)
at com.google.android.gms.tasks.zzr.zzb(com.google.android.gms:play-services-tasks@@18.1.0:5)
at com.google.android.gms.tasks.zzw.zzb(com.google.android.gms:play-services-tasks@@18.1.0:3)
at com.google.android.gms.tasks.zzc.run(com.google.android.gms:play-services-tasks@@18.1.0:8)
at com.google.android.gms.cloudmessaging.zzy.execute(com.google.android.gms:play-services-cloud-messaging@@17.1.0:1)
at com.google.android.gms.tasks.zzd.zzd(com.google.android.gms:play-services-tasks@@18.1.0:1)
at com.google.android.gms.tasks.zzr.zzb(com.google.android.gms:play-services-tasks@@18.1.0:5)
at com.google.android.gms.tasks.zzw.zzb(com.google.android.gms:play-services-tasks@@18.1.0:3)
at com.google.android.gms.tasks.TaskCompletionSource.setResult(com.google.android.gms:play-services-tasks@@18.1.0:1)
at com.google.android.gms.cloudmessaging.zzr.zzd(com.google.android.gms:play-services-cloud-messaging@@17.1.0:3)
at com.google.android.gms.cloudmessaging.zzt.zza(com.google.android.gms:play-services-cloud-messaging@@17.1.0:2)
at com.google.android.gms.cloudmessaging.zzk.handleMessage(com.google.android.gms:play-services-cloud-messaging@@17.1.0:14)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8751)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
```
opened 05:02PM - 11 Jun 25 UTC
api: messaging
* Firebase Component: firebase-messaging
* Component version: 24.0.1
### Desc… ribe the problem
#### Steps to reproduce:
For some users, attempting to get the token returns this error:
`Fetching the token failed: java.util.concurrent.ExecutionException: java.io.IOException: Invalid argument for the given fid.`
Here's a related issue that shows a full stack trace: https://github.com/firebase/firebase-android-sdk/issues/6914
#### Relevant Code:
```kt
FirebaseMessaging.getInstance().token
.addOnCompleteListener { task ->
if (!task.isSuccessful) {
val exception = task.exception
promise.reject(REGISTRATION_FAIL_CODE, "Fetching the token failed: ${exception?.message ?: "unknown"}", exception)
return@addOnCompleteListener
}
// ...
}
```
Note: I am using this through a library called expo-notifications, so you can see all the code here: https://github.com/expo/expo/blob/c46aeff68ecf6747d792b530482f2c88111cff39/packages/expo-notifications/android/src/main/java/expo/modules/notifications/tokens/PushTokenModule.kt#L51
HB9TNZ
June 16, 2025, 7:42am
4
thx for the quick response. I
. uninstalled + installed again
So this looks like not working on my Android 15 on a Galaxy Flip 6.
K7KER
June 16, 2025, 7:54am
5
Exact same issue here with Android 15 on a Google Pixel 9. I’ll search some more and come back here to see if anyone has had success.
HB9DQM
June 16, 2025, 7:59am
6
So far it sounds like it’s related to Android 15. @KK4KFG What phone model and Android version are you using?
In the meantime, all I can suggest as a temporary measure for affected users is to use Threema for receiving HamAlert push notifications on their phones.
HB9TNZ
June 16, 2025, 11:31am
7
i am using
. Galaxy Z Flip 6
I do switched to Threema. That works
KK4KFG
June 16, 2025, 2:25pm
8
Google Pixel 9a running android 15
HB9DQM
June 18, 2025, 8:04pm
9
There has been some feedback from Google in the GitHub issue mentioned above ([firebase-messaging] IOException: Invalid argument for the given fid · Issue #7025 · firebase/firebase-android-sdk · GitHub ). Apparently it is caused by duplicate device IDs, which in turn can be caused by using data migration tools to move app data from one device to another. According to Google, reinstalling the affected app should resolve the issue. Evidently it doesn’t. One other affected developer has speculated that the “Clear storage” feature in the system settings app could help clear all app data (which reinstalling may not do) and resolve the issue.
HB9TNZ
June 18, 2025, 9:11pm
10
Thx for the update. Works for me now. I navigated
. Standard-Apps
and reset Password. Its always easy if you know how
1 Like
KK4KFG
June 20, 2025, 6:19pm
11
Got the upgrade to Android 16 and still no notifications. Deleted the app, restarted the phone, and installed app again with no success
I did go into settings and deleted the app storage for ham alert.
It is now working for me!
Betting it was the duplicate device ID and clearing storage got it going.
1 Like
