user12927500
user12927500

Reputation:

Why do I get this GRPC Error "WARNING: EmulatorService.cpp:448: Cannot find certfile" when I start the emulator?

Good evening everyone, I have only been dealing with Java and Android Studio for a few months, can someone help me to solve this error? It occurs every time the emulator starts. Thank you

Emulator: Started GRPC server at 127.0.0.1:8554

Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: C:\Users\Sawye.android\emulator-grpc.cer security will be disabled.

Upvotes: 33

Views: 42978

Answers (9)

SDP190
SDP190

Reputation: 336

I have tried all the strange answers above nothing solved the issue. So searched in google's issue tracker, I found someone posted an Issue about it, and here is what the team wrote in response:

Hi, this warning is benign. We'll remove it in a future update.

So as google said: that warning is nothing to be worried, not harmful, and will be removed!

Update: Issue was now indeed fixed with latest Release Update for the Canary Dev Channel:

  • Removed prints about certs and GRPC on startup.

Upvotes: 0

Serkan Yıldırım
Serkan Yıldırım

Reputation: 191

Here my scenario: I closed the emulator with force quit. After restarting emulator, I always got this error.

Fix: I opened the AVD Manager in Android Studio by selecting Tools > AVD Manager menu. In the opened popup, I chose Wipe Data option as can be seen below image. After that, I restarted emulator and it worked !!!

enter image description here

Upvotes: 7

SAURABH_12
SAURABH_12

Reputation: 2310

Your emulator is out of date, please update by launching Android Studio:

  1. Start Android Studio
    • Select menu "Tools > Android > SDK Manager"
    • Click "SDK Tools" tab
    • Check "Android Emulator" checkbox
    • Click "OK"

Upvotes: 5

Abir Hasan Shawon
Abir Hasan Shawon

Reputation: 6119

I was also getting the same error. The above answers didn't fix my issue. I tried a lot of things, then finally when I uninstalled Intel x86 Emulator Accelerator (HAXM installer) from-

Tools > Android > SDK Manager > Android SDK > SDK Tools.

Then I reinstalled Intel x86 Emulator Accelerator (HAXM installer). This fixed my issue and I was able to run my emulator again. Hope it helps!

Upvotes: 0

Colin Gell
Colin Gell

Reputation: 382

A quick fix:

From the main navbar menu Tools > Android > SDK Manager > Android SDK > SDK Tools

You'll then see the screen below where you can select '- Android Emulator Hypervisor Driver for AMD Processors (installer) version 1.3.0'

enter image description here

I am not sure what the actual root cause of the issue is, but this patched the issue for me and may help other people.

Upvotes: 12

Daniel Rudy
Daniel Rudy

Reputation: 1439

Unless it's preventing your app from running in the emulator, or preventing the emulator from running at all, I wouldn't worry about it. It's something new that Google put into the emulator so it now checks for that file. I looked at an installation which did not have the updates and the cert file was missing there as well, and it ran just fine with no error. I'm not sure what Google is doing, but I know that this wasn't thought through all the way based on the number of people who have been having problems with this.

Upvotes: 0

irotsoma
irotsoma

Reputation: 715

Invalidate and Restart option in Android Studio, followed by gradle clean, and manually uninstalling the application from the emulator finally worked for me. Individually, they didn't for whatever reason.

I tried several other options mentioned without any luck. The file it mentioned "emulator-grpc.cer" still doesnt exist anywhere. There is a keystore in that folder called debug.keystore which isn't altered after fixing it, so I'm guessing that error is just misleading about the real problem, whatever it is. Anyway, thought I'd share what worked for me since I searched everywhere for it and didn't find it.

Upvotes: 12

Ziggi
Ziggi

Reputation: 9

You need to add credentials for your application in console.developers.google.com i.e. credentials, clik Api Key 1 and than ADD AN ITEM in Restrict usage to your Android apps.

Upvotes: -1

Marco Espinoza
Marco Espinoza

Reputation: 93

Got the same issue, I restarted the computer and then runned again the emulator and it worked. Important! you have to run the app, not debug it. You can use debug after the app is installed again in the emulator

Upvotes: 0

Related Questions