So, I am new to android and trying to run my first app. Created an empty activity project and tried to run it using the emulator. I am getting the following error:
23:20 Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot
find certfile: C:\Users\myUser\.android\emulator-grpc.cer security
will be disabled.
23:20 Emulator: Started GRPC server at 127.0.0.1:8554
I am have tried installing the latest SDK from SDK tools, restarted the system. Still not good. Can Someone help?
Android Studio Details:
Android Studio 3.6.1
Build #AI-192.7142.36.36.6241897, built on February 27, 2020
Runtime version: 1.8.0_212-release-1586-b04 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1246M
Cores: 4
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins:
This seems to be quite a frequent recent problem, there are a few threads about it, for example: here and here among others.
I have had this problem myself, and what worked for me was to keep the emulator running, uninstall the app you just tried to run from within the emulator, and then re-run it from Android Studio (which will re-install it in the Android device in the emulator). When re-installed, it works fine.
Others in the aforementioned threads seemed to have luck with choosing:
File -> Invalidate Caches / Restart in Android Studio, but this did not make any difference for me.
I hope you find a solution.
A "Cold Boot Now" of AVD helps me. Tools > AVD Manager > "The drop-down on rigth side" > Cold Boot Now.
I still get the certfile error, but grpc works.
Issue fixed now with the newest Updates for Canary Release of Android Studio (Emulator 30.0.10 Canary)!
See Release Updates:
Removed prints about certs and GRPC on startup.
Related
i installed the new version of android studio . version 3.1.1 and i have new error in gradle sync:
Could not connect to server [fc3d9512-540e-47b4-9cb0-8d3b0c134fbe port:5736, addresses:[/127.0.0.1]]. Tried addresses: [/127.0.0.1].
i am using windows 10
I think it's not related to connection because i can update sdk from sdk manager but when i want to sync gradle this message was displayed.
screenshot :
screenshot
Make sure your firewall setting is turned off. It works for me I am using Android Studio 4.1.2 over Windows 10 and antivirus as Quick Heal, i just turned off quick heal firewall off and problem has resolved.
If you have any antivirus installed on your pc eg. Quick Heal, so make sure you turn off your firewall setting. In my case, it works and Gradle sync was done successfully.
I was running Android Studio 2.3 2 days ago and everything with my project was working perfectly. Installs were fine and there no warnings let alone errors.
When I did the upgrade from 2.3 to 2.3.3 Android Studio recommended the gradle, platform tools and build tools upgrade also. I did all of them and now when trying to deploy my app on the same device, it fails.
** observations **
I have 3 machines in my lab. Two of them are running 2.2.2 and have no issues still installing the app on the devices.
The machine that has problems was okay on version 2.3 of Android Studio. 2.3.3 plus the gradle and plugin updates seem to be the/part of the problem.
On the 2.2.2 machines, the apk is installed individually (WORKING)
$ adb shell pm install -r "/data/local/tmp/com.domain.sub"
pkg: /data/local/tmp/com.domain.sub
on the 2.3.3 machine (NOT WORKING)
$ adb install-multiple -r "...dependencies.apk, ...slice_0.apk, ...slice_1.apk, ... slice_9.apk, ...app-debug.apk
The exception that is thrown when the install is attempted (2.3.3):
Error while uploading slice_2.apk : java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String android.os.SystemProperties.native_get(java.lang.String) (tried Java_android_os_SystemProperties_native_1get and Java_android_os_SystemProperties_native_1get__Ljava_lang_String_2)
at android.os.SystemProperties.native_get(Native Method)
at android.os.SystemProperties.get(SystemProperties.java:52)
at android.os.Environment.getCanonicalPathOrNull(Environment.java:834)
at android.os.Environment.<clinit>(Environment.java:83)
at android.os.Environment.getLegacyExternalStorageDirectory(Environment.java:421)
at android.os.Debug.<clinit>(Debug.java:101)
at android.ddm.DdmHandleHello.handleHELO(DdmHandleHello.java:164)
at android.ddm.DdmHandleHello.handleChunk(DdmHandleHello.java:91)
at org.apache.harmony.dalvik.ddmc.DdmServer.dispatch(DdmServer.java:171)
java.lang.UnsatisfiedLinkError: android.os.Debug
at android.ddm.DdmHandleHello.handleFEAT(DdmHandleHello.java:176)
at android.ddm.... (show balloon)
After a lot of attempts at different suggestions the working solution for me was to disable "Instant Run" in Android Studio.
Open the Settings In Android Studio.
Navigate to Build, Execution, Deployment > Instant Run.
Uncheck the box next to Restart activity on code changes.
Then I cleaned and rebuilt the application and the apk installed successfully.
For Android Studio 3.5+, there is no more "Instant Run" option, you should disable the "Apply changes" options instead:
I'm developing an app which doesn't run in Android 4.4.4.
Detail:
Only release version, cause when in debug time, usb plugged, runs smoothly. Created an emulator with 4.4.4 image and, same way, runs fine. The app simply refuses to open ("The application needs to be closed").
Do not know how to track the problem:
No logcat, no special message, not a clue, I'm unable to debug it.
Mean time:
Tested in many emulators sdk versions and always runs fine. My matter is with a physical device running 4.4.4.
My ambient:
Android Studio 2.1.2
JRE 1.7.0_79-b15 amd64
Gradle 2.1.2
Compiler sdk api 23
Build tools 23.0.3
Min. sdk 13
Target sdk 18
Minify enabled (release version)
Dependencies:
com.android.support:support-v4:23.1.0
com.android.support:appcompat-v7:23.0.+
com.android.volley:volley:1.0.0
com.jakewharton:disklrucache:2.0.2
Thanks in advance.
Have you try change Target sdk 18 to 19?. Because Android 4.4 is API Level 19
Don't forget to disable proguard first to make sure that wasn't because of proguard.
I just installed Android Studio (after wiping everything away from previous installations of either android studio and android SDK), I created a new app (from the templates, didn't edit anything), and I tried to run it in an emulator. I went through the process of creating a AVD (which crashes from Android Studio, but works if I start the tool directly from outside), but no matter what, it fails to run.
I always get a "jspawnhelper quit unexpectedly." error.
My system:
OSX 10.7.5 (and don't ask me to upgrade, please)
Java 1.7.0_79 (I also tried with 1.8, it's worse)
Android Studio 2.1.1
Android
SDK for API 23 and 22 installed today.
I have no clue what jspawnhelper is, and honestly, I couldn't care less. I just want to install Android Studio and start writing some code.
Seems like I found the answer and, as usual, is not the answer I want to hear ...
Android Studio requires OSX 10.8.5.
unable to create AVD with android sdk on Mac OS
I'm not upgrading this macbook even if somebody points a gun at me ... time to go shopping, or install linux.
I've recently upgraded my Intellij to version 14. I wanted to create some Android application so I created a new project. Then I wanted to start an emulator so I used the AVD manager from within Intellij and created a new AVD. But then trying to run the application failed as the AVD couldn't be run.
Waiting for device.
/usr/local/Cellar/android-sdk/23.0.2/tools/emulator -avd AVD_for_Nexus_5_by_Google -netspeed full -netdelay none
PANIC: Could not open: AVD_for_Nexus_5_by_Google
Now the thing is AVDs created by Intellij are stored in ~/.android/avd whereas those created by AVD manager from Android SDK are in /usr/local/Cellar/android-sdk/23.0.2/.android and these run fine.
I'm not sure what am I doing wrong, I don't recall having issues with Intellij 13 although I haven't played with Android for a long while now.
Any help would be appreciated :)
I was facing the same issue on Ubuntu, Windows 7 and Windows 8 machines. For some reason if you have selected your emulator ABI as x86 or x86_64 then it doesn't start, however, if you select armeabi-v7a, it should start.