blocks|key|2540059|text|我和你一样有同样的问题。我的错误是:我将<service>标记放置在<application>标记之外的AndroidManifest.xml文件中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2540060|我的看上去是这样的：|2540061|<application
++++android:allowBackup="true"
++++android:icon="@mipmap/ic_launcher"
++++android:label="@string/app_name"
++++android:supportsRtl="true"
++++android:theme="@style/AppTheme">

++++<service
++++++++android:name=".MyFirebaseMessagingService">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.MESSAGING_EVENT"/>
++++++++</intent-filter>
++++</service>

++++<service
++++++++android:name=".MyFirebaseInstanceIDService">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
++++++++</intent-filter>
++++</service>
</application>|code-block|syntax|javascript|2540062|而且没有任何问题。|2540063|entityMap^0|K|9|Y|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

I had the same problem like you. My mistake was the following: I placed my <code>&lt;service&gt;</code> tags outside the <code>&lt;application&gt;</code> tag in the AndroidManifest.xml file. 

Now mine looks like this:

<pre><code>&lt;application
 android:allowBackup="true"
 android:icon="@mipmap/ic_launcher"
 android:label="@string/app_name"
 android:supportsRtl="true"
 android:theme="@style/AppTheme"&gt;

 &lt;service
 android:name=".MyFirebaseMessagingService"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.MESSAGING_EVENT"/&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;

 &lt;service
 android:name=".MyFirebaseInstanceIDService"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.INSTANCE_ID_EVENT"/&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;
&lt;/application&gt;
</code></pre>

And it works without any problem.

blocks|key|3399218|text|只有在生成新令牌时才调用FirebaseInstanceIdService中的FirebaseInstanceIdService。如果您的应用程序是以前安装并生成的令牌，那么onTokenRefresh将不会被调用。尝试卸载和重新安装应用程序，以强制生成一个新令牌，这将导致onTokenRefresh被调用。|type|blockquote|depth|inlineStyleRanges|entityRanges|data|3399219|还请确保您的FirebaseInstanceIdService在AndroidManifest.xml中有正确的定义。|unstyled|3399220|在你的报表文件里。|3399221|+<service
++++++++android:name="com.bnt.etailers.fcm.MyFireBaseInstanceIDService"
++++++++android:exported="false">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.INSTANCE_ID_EVENT"+/>
++++++++</intent-filter>
++++</service>

++++<service
++++++++android:name="com.bnt.etailers.fcm.GCMNotificationIntentService"
++++++++android:exported="false">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.MESSAGING_EVENT"+/>
++++++++</intent-filter>
++++</service>|code-block|syntax|javascript|3399222|FirebaseInstanceIdService类|3399223|public+class+MyFireBaseInstanceIDService+extends+FirebaseInstanceIdService+{


private+static+final+String+TAG+=+MyFireBaseInstanceIDService.class.getSimpleName();

@Override
public+void+onTokenRefresh()+{
++++//+Get+updated+InstanceID+token.
++++String+refreshedToken+=+FirebaseInstanceId.getInstance().getToken();
++++Log.d(TAG,+"Refreshed+token:+"+%2B+refreshedToken);

++++if+(refreshedToken!=null)+{
++++++++SettingPreferences.setStringValueInPref(this,+SettingPreferences.REG_ID,+refreshedToken);
++++}
++++//+TODO:+Implement+this+method+to+send+any+registration+to+your+app's+servers.
++++sendRegistrationToServer(refreshedToken);
}
//+[END+refresh_token]

/**
+*+Persist+token+to+third-party+servers.
+*
+*+Modify+this+method+to+associate+the+user's+FCM+InstanceID+token+with+any+server-side+account
+*+maintained+by+your+application.
+*
+*+@param+token+The+new+token.
+*/
private+void+sendRegistrationToServer(String+token)+{
++++//+Add+custom+implementation,+as+needed.
}}|3399224|FirebaseMessagingService类。|3399225|public+class+GCMNotificationIntentService+extends+FirebaseMessagingService+{
//+Sets+an+ID+for+the+notification,+so+it+can+be+updated


public+GCMNotificationIntentService()+{
++++super();
}


@Override
public+void+onMessageReceived(RemoteMessage+message)+{

}}|3399226|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|Y|8|@]|9|@]|A|$J|K]]|$1|L|3|M|5|D|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|I|7|10|8|@]|9|@]|A|$J|K]]|$1|P|3|Q|5|D|7|11|8|@]|9|@]|A|$]]|$1|R|3|S|5|I|7|12|8|@]|9|@]|A|$J|K]]|$1|T|3|-4|5|D|7|13|8|@]|9|@]|A|$]]]|U|$]]

<blockquote>
 onTokenRefresh in FirebaseInstanceIdService is only called when a new token is generated. If your app was previously installed and generated a token then onTokenRefresh would not be called. Try uninstalling and reinstalling the app to force the generation of a new token, this would cause onTokenRefresh to be called.
</blockquote>

Also be sure that your FirebaseInstanceIdService is properly defined in your AndroidManifest.xml

In your Manifest File.

<pre><code> &lt;service
 android:name="com.bnt.etailers.fcm.MyFireBaseInstanceIDService"
 android:exported="false"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.INSTANCE_ID_EVENT" /&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;

 &lt;service
 android:name="com.bnt.etailers.fcm.GCMNotificationIntentService"
 android:exported="false"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.MESSAGING_EVENT" /&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;
</code></pre>

FirebaseInstanceIdService class

<pre><code>public class MyFireBaseInstanceIDService extends FirebaseInstanceIdService {


private static final String TAG = MyFireBaseInstanceIDService.class.getSimpleName();

@Override
public void onTokenRefresh() {
 // Get updated InstanceID token.
 String refreshedToken = FirebaseInstanceId.getInstance().getToken();
 Log.d(TAG, "Refreshed token: " + refreshedToken);

 if (refreshedToken!=null) {
 SettingPreferences.setStringValueInPref(this, SettingPreferences.REG_ID, refreshedToken);
 }
 // TODO: Implement this method to send any registration to your app's servers.
 sendRegistrationToServer(refreshedToken);
}
// [END refresh_token]

/**
 * Persist token to third-party servers.
 *
 * Modify this method to associate the user's FCM InstanceID token with any server-side account
 * maintained by your application.
 *
 * @param token The new token.
 */
private void sendRegistrationToServer(String token) {
 // Add custom implementation, as needed.
}}
</code></pre>

FirebaseMessagingService class.

<pre><code>public class GCMNotificationIntentService extends FirebaseMessagingService {
// Sets an ID for the notification, so it can be updated


public GCMNotificationIntentService() {
 super();
}


@Override
public void onMessageReceived(RemoteMessage message) {

}}
</code></pre>

blocks|key|3399234|text|try+{
++++FirebaseInstanceId.getInstance().deleteInstanceId();
}+catch+(IOException+e)+{
++++e.printStackTrace();
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3399235|在onCreate方法中删除令牌。|unstyled|offset|length|style|CODE|3399236|entityMap^0|0|1|8|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@$G|O|H|P|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>try {
 FirebaseInstanceId.getInstance().deleteInstanceId();
} catch (IOException e) {
 e.printStackTrace();
}
</code></pre>

in <code>onCreate</code> method to delete token.

blocks|key|2540140|text|是的，有时可能会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2540141|无论您想要获得fcm+id，请调用以下方法。|2540142|++++try+{
++++++++++++String+refreshedToken+=+FirebaseInstanceId.getInstance().getToken();
++++++++++++Log.d("Firbase+id+login",+"Refreshed+token:+"+%2B+refreshedToken);
++++++++}+catch+(Exception+e)+{
++++++++++++e.printStackTrace();
++++++++}|code-block|syntax|javascript|2540143|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Yes this might happen some times.

Please call the following method wherever you want to get your fcm id.

<pre><code> try {
 String refreshedToken = FirebaseInstanceId.getInstance().getToken();
 Log.d("Firbase id login", "Refreshed token: " + refreshedToken);
 } catch (Exception e) {
 e.printStackTrace();
 }
</code></pre>

blocks|key|3292679|text|在我的情况下，我忘了在清单中添加互联网权限，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3292680|<uses-permission+android:name="android.permission.INTERNET"+/>|code-block|syntax|javascript|3292681|希望大多数人不会犯这个错误。|3292682|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case I forgot to add internet permission in manifest,

<pre><code>&lt;uses-permission android:name="android.permission.INTERNET" /&gt;
</code></pre>

Hope most people won't make this mistake.

blocks|key|3399293|text|尝试重新安装应用程序，首先从您的设备或模拟器卸载它。然后它将生成一个新的令牌，因此将再次调用onTokenRefresh()。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3399294|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try re-install the app, by uninstall it first from your device or emulator. It will then generate a new token, thus onTokenRefresh() will be called again.

blocks|key|3399329|text|在我的例子中，我什么都试过了，但从来没有叫过onTokenRefresh。然后我更改了我的WiFi并连接到不同的网络，现在它成功了！以前的WiFi有很好的互联网连接性，不知道为什么会这样。也许这能帮到一个人。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|3399330|entityMap^0|M|E|19|4|1K|2|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|P|8|@]|E|@]|F|$]]]|H|$]]

In my case, I tried everything but <code>onTokenRefresh</code> was never called. Then I change my WiFi and I connect to different network, Now it worked!!. Previous WiFi has good internet connectivity, Don't know why it was happening. May be this can help someone.

blocks|key|2540200|text|重新安装对我来说是个诀窍！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2540201|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Reinstalling did the trick for me!

blocks|key|3292759|text|我曾经经历过，当您在无法连接互联网的设备上运行应用程序时，不会调用MyFirebaseInstanceIDService。这样，onTokenRefresh()就不会被调用。因此，在运行您的应用程序以获取更新的FirebaseToken时，请确保您的设备必须具有internet连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3292760|另外，卸载之前的应用程序&重新安装+it以获取更新的令牌。在下列情况下，注册令牌发生更改：|offset|length|style|BOLD|3292761|1)应用程序删除实例ID|3292762|2)在新设备上恢复应用程序|3292763|3)用户卸载/重新安装应用程序|3292764|4)用户清除应用程序数据。|3292765|entityMap^0|0|D|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I have experienced that MyFirebaseInstanceIDService is not called when you are running your application on a device where internet connectivity is not available. In this way onTokenRefresh() is not called. So make sure that your device must has internet connection during running your application for taking updated FirebaseToken. 

Also uninstall the previous app &amp; Re-Install it for taking updated token.
The registration token change when:

1) The app deletes Instance ID

2) The app is restored on a new device

3) The user uninstalls/reinstall the app

4) The user clears app data.

blocks|key|2540252|text|我已经挣扎了一个多小时，然后我更改了下面的代码，它突然起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2540253|按以下方式处理您的refreshedToken：|2540254|String+refreshedToken;
++++try+{
++++++++refreshedToken+=+FirebaseInstanceId.getInstance().getToken();
++++++++Log.d(TAG,+"Refreshed+token:+"+%2B+refreshedToken);
++++++++Localytics.setPushRegistrationId(refreshedToken);
++++}+catch+(Exception+e)+{
++++++++Log.d(TAG,+"Refreshed+token,+catch:+"+%2B+e.toString());
++++++++e.printStackTrace();
++++}|code-block|syntax|javascript|2540255|尝试将android:exported="true">添加到清单中的MyFirebaseMessagingService和MyFirebaseInstanceIDService中，这样看起来如下所示：|2540256|<service
++++++++android:name="com.localytics.android.sample.fcm.MyFirebaseMessagingService"
++++++++android:exported="true">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.MESSAGING_EVENT"/>
++++++++</intent-filter>
++++</service>

++++<service
++++++++android:name="com.localytics.android.sample.fcm.MyFirebaseInstanceIDService"
++++++++android:exported="true">
++++++++<intent-filter>
++++++++++++<action+android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
++++++++</intent-filter>
++++</service>|2540257|卸载您的应用程序，重新安装，工作。在真正的设备上测试。|2540258|android:exported="+true“是一个默认选项，因此您也可以完全删除该选项，并将其设置为true。|2540259|另外，如果您想更显式地调用onTokenRefresh，只需在代码中的任何地方调用它：|2540260|String+refreshedToken+=+FirebaseInstanceId.getInstance().getToken();
Localytics.setPushRegistrationId(refreshedToken);|2540261|你不必再依赖广播被接收了|2540262|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I've been struggling with that for over an hour, then I changed the following code and it suddenly worked. 

handle your refreshedToken as such:

<pre><code>String refreshedToken;
 try {
 refreshedToken = FirebaseInstanceId.getInstance().getToken();
 Log.d(TAG, "Refreshed token: " + refreshedToken);
 Localytics.setPushRegistrationId(refreshedToken);
 } catch (Exception e) {
 Log.d(TAG, "Refreshed token, catch: " + e.toString());
 e.printStackTrace();
 }
</code></pre>

Try adding 
android:exported="true"> to both MyFirebaseMessagingService and MyFirebaseInstanceIDService in manifest so it looks like that:

<pre><code>&lt;service
 android:name="com.localytics.android.sample.fcm.MyFirebaseMessagingService"
 android:exported="true"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.MESSAGING_EVENT"/&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;

 &lt;service
 android:name="com.localytics.android.sample.fcm.MyFirebaseInstanceIDService"
 android:exported="true"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.INSTANCE_ID_EVENT"/&gt;
 &lt;/intent-filter&gt;
 &lt;/service&gt;
</code></pre>

Uninstall your app, Install again, worked. Tested on real device. 

android:exported="true" is a default option so you can also remove that entirely and it will be set to true. 

Also if you want to call onTokenRefresh more explicitly, you can simply call that anywhere in your code:

<pre><code>String refreshedToken = FirebaseInstanceId.getInstance().getToken();
Localytics.setPushRegistrationId(refreshedToken);
</code></pre>

You don't have to rely on broadcast being received any more

blocks|key|3399408|text|确保你增加了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3399409|应用插件：'com.google.gms.google-services‘|3399410|这到app.gradle文件的底部|3399411|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Make sure you have added 

apply plugin: 'com.google.gms.google-services'

this to bottom of the app.gradle file

blocks|key|3292837|text|我也有同样的问题。我的设备(kitkat+4.4.2)由于某种原因无法获得onTokenRefresh()。我的互联网连接是完美的，谷歌的游戏服务是最新的，并满足了所有必要的条件，消防基地的工作。我的代码在5.0.0和更高版本的设备上运行得很好。为了解决这个问题，我不得不将我的设备重置为工厂设置，并且应用程序开始工作。我知道这很难，但也许能帮上忙。必须有一些问题或与其他应用程序冲突，这导致onTokenRefresh()不被调用。祝好运!|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3292838|entityMap^0|D|E|11|G|2V|5|5G|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I had the same problem. My device<code>(kitkat 4.4.2)</code> couldn't get <code>onTokenRefresh()</code> for some reason. My internet connection was perfect, google play services was up to date and all necessary contiditions for firebase to work were met. My code worked perfectly on the devices <code>5.0.0</code> and higher. To solve this issue i had to reset my device to factory settings and application started to work. I know it's tough measure but maybe it may help somebody. There must be some problems or conflict with other application, which caused <code>onTokenRefresh()</code> not to be called. Good luck!

blocks|key|3292951|text|没有调用onTokenRefresh+methon有几个原因。我已经列出了这一点，并逐一提及。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3292952|请确保您已经添加了internet权限。|ordered-list-item|3292953|检查是否在项目中添加了从应用程序目录内的google控制台生成的google-services.json文件|3292954|​|3292955|📷|atomic|offset|length|3292956|3292957|在模块级文件(通常是app/build.gradle)中，在文件底部添加应用插件行，以启用Gradle插件：|3292958|应用插件：'com.android.application‘android+{+//+.}依赖性{+//+.实现'com.google.firebase:firebase-core:16.0.4‘//得到一个“找不到”错误？确保在根目录build.gradle+}+//添加了//+Google资源库//在底部添加此插件：'com.google.gms.google-services‘|blockquote|3292959|4)在项目级build.gridle文件中添加play服务类路径|3292960|buildscript+{+//+.依赖性{+//+.类路径'com.google.gms:+google-services+:4.1.0‘/google-services+plugin+}+allprojects+{+//+.资料库{+//+.google()+//+Google的Maven存储库}|3292961|5)确保在应用程序标记中的AndroidManifes文件中添加了这些服务|3292962|3292963|6)当令牌刷新和安装第一个应用程序时，都会调用onToken刷新，因此请确保已手动删除应用程序或清除数据。|3292964|7)确保在服务类中扩展了FirebaseMessagingService|3292965|备注：如果它不适用于特定版本，例如android版本，那么尝试更改fcm版本。|style|BOLD|3292966|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/597585fc2501da8254106d8a38ef5062.png|imageAlt^0|0|0|0|0|0|1|0|0|0|0|0|0|0|0|0|0|0|0|2|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1I|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1J|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1K|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1L|8|@]|9|@$L|1M|M|1N|1|1O]]|A|$]]|$1|N|3|H|5|6|7|1P|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1Q|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1R|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1S|8|@]|9|@]|A|$]]|$1|V|3|W|5|S|7|1T|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|S|7|1V|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1W|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1X|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1Y|8|@$L|1Z|M|20|16|17]]|9|@]|A|$]]|$1|18|3|-4|5|6|7|21|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F|1G|-4]]]]

There are several reasons to not calling the onTokenRefresh methon not called. I have listed that and mention it one by one .

<ol>
<li>Please make sure you have added the internet permission 

</li>
<li>check have you added the google-services.json file that generate from google console inside of app directory in your project</li>
</ol>

<a href="https://i.stack.imgur.com/YrPBT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YrPBT.png" alt="enter image description here"></a>

<ol start="3">
<li>In your module Gradle file (usually the app/build.gradle), add the apply plugin line at the bottom of the file to enable the Gradle plugin:</li>
</ol>

<blockquote>
<pre><code>apply plugin: 'com.android.application'

android {
 // ...
}

dependencies {
 // ...
 implementation 'com.google.firebase:firebase-core:16.0.4'

 // Getting a "Could not find" error? Make sure you have
 // added the Google maven respository to your root build.gradle
}

// ADD THIS AT THE BOTTOM
apply plugin: 'com.google.gms.google-services'
</code></pre>
</blockquote>

4) add the play service class path in project level build.gridle file

<blockquote>
<pre><code>buildscript {
 // ...
 dependencies {
 // ...
 classpath 'com.google.gms:google-services:4.1.0' // google-services plugin
 }
}

allprojects {
 // ...
 repositories {
 // ...
 google() // Google's Maven repository
 }
}
</code></pre>
</blockquote>

5) Make sure you have added those service in the AndroidManifes file inside application tag

<blockquote>
 

<pre><code>&lt;service
 android:name=".MyFirebaseMessagingService"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.MESSAGING_EVENT"/&gt;
 &lt;/intent-filter&gt;
&lt;/service&gt;

&lt;service
 android:name=".MyFirebaseInstanceIDService"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="com.google.firebase.INSTANCE_ID_EVENT"/&gt;
 &lt;/intent-filter&gt;
&lt;/service&gt; &lt;/application&gt;
</code></pre>
</blockquote>

6) onToken refresh is called when token refresh and when install the app for the first so make sure you have deleted the app manually or clear the data

7) Make sure you have extends the FirebaseMessagingService in your service class

[Note : If its not working only for specific version for example android kitkat version then try to change the fcm version.]

In my <code>MainActivity</code>in my log, I can see the token using <code>FirebaseInstanceId.getInstance().getToken()</code> and it display the generated token. But it seems like in my <code>MyFirebaseInstanceIDService</code> where it is extends to <code>FirebaseInstanceIdService</code>, the <code>onTokenRefresh()</code> is not called, where in this function it was said that the token is initially generated here. I needed to call <code>sendRegistrationToServer()</code> that's why I'm trying to know why it doesn't go in the <code>onTokenRefresh()</code>. 

Here is my code

<pre><code>public class MyFirebaseInstanceIDService extends FirebaseInstanceIdService {


@Override
public void onTokenRefresh() {
 // Get updated InstanceID token.
 String refreshedToken = FirebaseInstanceId.getInstance().getToken();
 Log.d(TAG, "Refreshed token: " + refreshedToken);

 sendRegistrationToServer(refreshedToken);
 }
}
</code></pre>

Firebase onTokenRefresh() is not called

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在日志中的MainActivity中，我可以看到使用FirebaseInstanceId.getInstance().getToken()的令牌，它显示生成的令牌。但是在我的MyFirebaseInstanceIDService (扩展到FirebaseInstanceIdService )中，似乎没有调用onToke...

问不调用Firebase onTokenRefresh()
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不调用Firebase onTokenRefresh()EN