FirebaseInstanceId.getInstanceId()与连接到iPhone WearOS设备上SERVICE_NOT_AVAILABLE失败

问题描述 投票:1回答:1

连接到iPhone WearOS装置最近开始打电话FirebaseInstanceId.getInstanceId()时得到SERVICE_NOT_AVAILABLE错误。确切的例外是:

2018-12-07 14:37:26.529 5093-5093/com.xxxxx.xxxxxx E/OurFirebaseActivity: Could not get Firebase token. Exception: java.io.IOException: SERVICE_NOT_AVAILABLE
    java.io.IOException: SERVICE_NOT_AVAILABLE
        at com.google.firebase.iid.zzr.zza(Unknown Source:66)
        at com.google.firebase.iid.zzr.zza(Unknown Source:79)
        at com.google.firebase.iid.zzu.then(Unknown Source:4)
        at com.google.android.gms.tasks.zzd.run(Unknown Source:5)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)

这似乎并不具体到我们的应用程序而已,看设备日志的时候,这似乎发生的其他应用程序/服务以及。

2018-12-07 14:02:48.931 891-3870/? I/GCM: Registration for wearable paired to iOS
2018-12-07 14:02:48.956 857-857/? D/AltFCMManager: reading APNS_TOKEN dataitem found a null dataitem: 
2018-12-07 14:02:49.107 857-881/? I/zygote: Background concurrent copying GC freed 
2018-12-07 14:02:53.950 891-3870/? W/GCM: Timed out getting APNS token from clockwork
2018-12-07 14:02:53.963 4509-4544/? E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE

所有火力库组件都是最新的。还证实,GoogleApiAvailability.getInstance()。isGooglePlayServicesAvailable(本)返回这些设备上成功。

也许最近谷歌Play服务更新打破了FCM对这个设备组合?

ios firebase firebase-cloud-messaging wear-os
1个回答
0
投票

这是通过在WearOS应用程序的iPhone和谷歌的问题引起的发布了一个补丁在2019年一月初与v3.11.27。

© www.soinside.com 2019 - 2024. All rights reserved.