FirebaseInstanceId Token retrieval failed SERVICE_NOT_AVAILABLE

Question

I'm working on an android app, it uses Firebase Authentication, Database and Storage. It was all working fine until this error message started to show up in logcat. (I did not tamper with any configs at firebase console)

E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE

this error message shows even when I have commented on all firebase-related code.

Therefore I'm unable to proceed with authentication and other firebase-related stuff.
Yes, I'm connected to the internet and also have gotten a new Google-Services.json file from Firebase Console but it has made no difference at all.

yes both Google play services and Google play store are enabled in my device. Any idea about what other issue could be? I've tried the same code on an android emulator and it worked. I don't know how my physical device got this problem, it worked fine before this. — Masroor, Apr 21 '18 at 08:18
so, I was able to resolve it finally! It turns out that Google play services were enabled, but they were restricted over Cellular Data. To solve it, I did the following: App Data Usage -> Google Services -> Turn Off the "Restrict Cellular Data Access" option — Masroor, Apr 21 '18 at 23:27
Hey I am getting the same issue but didn't solved it by--> Turn Off the "Restrict Cellular Data Access" option . Any help will appreciated. Thanks. — TechValens, Sep 03 '18 at 06:03
Enabling only one type of network connection (wifi or lte) worked for me. — shadowsheep, Feb 27 '19 at 10:38

Manuel Mühlemann · Answer 1 · 2019-09-09T09:26:44.940

98

"Cold Boot Now" Device in AVD Manager worked for me.

Edit: After updating emulators and than doing the cold boot it helped. – parohy Apr 5 at 9:22

edited Sep 09 '19 at 09:26

answered Sep 02 '18 at 15:05

Manuel Mühlemann

991
5
5

3

After updating emulators and than doing the cold boot it helped. – parohy Apr 05 '19 at 09:22
1

Cold boot did it for me. Thanks – Dante Gulapa Feb 22 '20 at 02:36
That was it all along!? Is there a specific reason this would fix the issue? Maybe having different applicationIdSuffixes with each flavor or something? – Dustin Silk Jul 09 '20 at 08:29
This tip work for me too. Working with Flutter with an emulated devide on Android Studio. – Juan Cabello Oct 25 '20 at 01:18
I went to the AVD Manager, click on device and then show advanced settings and finally i switched to "Cold Boot Now", then save and my issue was gone, thansk! – Fernando Torres Nov 01 '20 at 06:30
"Cold Boot" worked also for me; thx for the hint – jawa Mar 10 '21 at 17:07
in my case after "Cold boot", for only first time, getting this error, if i just reopen the app then issue is not there, so should i expect that this error will not come in real devices?? – Vivek Thummar Mar 02 '22 at 08:16

score 28 · Answer 2 · answered Apr 25 '19 at 14:35

28

Stop emulator device and open AVD Manager Panel, edit device configuration. In device configuration panel "Show Advanced Settings" in "Emulated Performance" section select "Cold boot" option as Boot Option then click Finish, it should be worked.

answered Apr 25 '19 at 14:35

cowboycb

509
4
11

score 21 · Answer 3 · answered Sep 05 '18 at 22:29

21

I also faced with this issue. As I can see it can happen for many reasons.

Finally I figured out that my problem was that the current latest Facebook Android SDK version (v4.36.0) has a bug. Everything works fine if I set it back to v4.35.0. Maybe this info can help someone in the future.

You can find here the releases: https://github.com/facebook/facebook-android-sdk/releases

answered Sep 05 '18 at 22:29

gabhor

579
8
22

7

Using com.facebook.android:facebook-android-sdk:4.36.0 caused white blank screen on loading of mine application. Changed to 4.35.0, fixed the problem. Thanks! – kashlo Sep 10 '18 at 14:57
1

Wow! You just saved me! – orelzion Sep 15 '18 at 19:12
I downgraded to v4.35.0 of FacebookSDK and that fixed the problem! Thanks a lot! – Mladen Sep 16 '18 at 20:52
I was having the same issue in Android Q - API 29, and this fixed it. Thanks – andrey2ag Jul 29 '19 at 22:20
It's glad to hear that! You can also try to upgrade to the latest one since it was already fixed in the upcoming versions. – gabhor Jul 30 '19 at 11:33

score 9 · Answer 4 · answered May 24 '18 at 19:40

9

you need to update the emulator to the latest version that includes Google Play services

answered May 24 '18 at 19:40

EdHuamani

1,729
11
16

score 9 · Answer 5 · answered Oct 23 '20 at 06:20

To fix it you should check your Google play services properly are enabled

If it is still showing the same error then you need to try the below steps

You need to stop your emulator device.
After that you need to open the AVD Manager Panel then the edit device configuration. In your device configuration panel go to "Show Advanced Settings" in the "Emulated Performance" section then you need to select the "Cold boot" option as the Boot Option then you should click on the Finish.

After following the above steps your issue related to firebase must be fixed and it should be working.

NanPd · Answer 6 · 2020-09-08T13:38:32.370

6

For future readers:

Found this error when I set device date different than current and open. My application logs start printing similar log. Solution: restart your device and it will start working fine.

edited Sep 08 '20 at 13:38

answered Jan 08 '20 at 09:06

NanPd

710
7
14

score 5 · Answer 7 · answered Aug 28 '18 at 13:40

5

I changed my emulator and now it is working correctly without any error.

answered Aug 28 '18 at 13:40

Mo Meshkani

1,306
1
14
26

score 5 · Answer 8 · answered May 04 '20 at 14:17

Check that Google play services are enabled

if it still shows error Now try these steps

Step 1 - Stop emulator device

Step 2 - open AVD Manager Panel, edit device configuration. In device configuration panel "Show Advanced Settings" in "Emulated Performance" section select "Cold boot" option as Boot Option then click Finish, it should be worked.

If this does not work try to work on different Emulator

score 1 · Answer 9 · answered Oct 19 '19 at 11:13

1

Root cause: You miss google services in your device. So if you use emulator then apply "Cold boot" mode in advanced setting, if you use real device please change another

answered Oct 19 '19 at 11:13

Quang Le

331
3
8

score 0 · Answer 10 · answered Jul 24 '20 at 07:17

0

You could be using a deprecated version of Google Play Services on your device, try upgrading your Play Services first.

answered Jul 24 '20 at 07:17

Vishal Kumar

1

3

this is more of a comment than an answer – meewog Jul 24 '20 at 07:28

score 0 · Answer 11 · answered May 07 '21 at 15:28

For me, this was a connection issue with my emulator. I was unable to load websites outside of my company's VPN. Probably worth confirming that you can do that (load up yahoo or stackoverflow on the device's browser) if you're having this issue. Once I figured out my emulator's connection issues, I was able to get the token.

score 0 · Answer 12 · answered Jul 14 '21 at 09:37

0

In my case, I was facing an Internet connectivity Issue. Make sure your Internet Connection is Strong enough to Generate FcmToken.

answered Jul 14 '21 at 09:37

Akash Neeli

154
7

score 0 · Answer 13 · answered Apr 26 '22 at 15:02

0

Visual Studio 2022 menu:

Tools
Android
Android Device Manager
Select device and click Edit

answered Apr 26 '22 at 15:02

Martin4code

31
4

FirebaseInstanceId Token retrieval failed SERVICE_NOT_AVAILABLE

13 Answers13

Linked