Develop Reference

FileNotFoundException exception in Android Studio core?

I had just installed Android Studio 2.3.3 and created a new project.
Then the error occurred.
Here is the Event Log
2017/7/30
21:50 FileNotFoundException: Entry fileTemplates//code/Google Test
Fixture SetUp Method.cc.ft not found in C:/Program
Files/Android/Android Studio/lib/idea.jar
21:50 Gradle sync started
21:50 InvalidVirtualFileAccessException: Accessing invalid virtual
file: file://C:/Android/SDK/platforms/android-26/data/res;
original:182; found:-
And here are some pics.
FileNotFoundException
InvalidVirtualFileAccessException
I'm new to Android Studio.It'll be great if someone helps.

This looks like the same problem I had. It was a new install of Android Studio. I'm just trying to learn to build an app but couldn't even create a new class.
It turned out that I had installed the 64 bit version on a 32 bit machine. In my defense, there's a big green download button that says its for windows, it says nothing about 64/32 bit until you scroll waaaaay down the page.
I found the answer here
Steps to fix:
1. uninstall android studio (but not the SDK)
2. download the 32 bit version from the same page where I found the 64 bit one.
3. Scroll down the page to find it.
4. unzip the downloaded file and move it into the programs directory.
5. launch android studion by opening the file \Program Files\Android\android-studio\bin\studio.exe

I got a similar error when trying to add C++ functionality, I think the fix will be similar too...
basicly I had to got to SDK Tools, tick the Show Packages, and then untick the Makec plugin

I've solved this issye by adjusting BIOS Setup, when I adjusted the virtualization option.
I'm using Android Studio 2.1.3.

Cannot start Android Studio. Android Studio stuck at the splash screen

I am not able to start the android studio. I have set java path in environment variables and Android studio is also latest version. I have tried to install and run administrator but no help.
Please help me...

Open file Android Studio setup directory/bin/idea.properties
Add disable.android.first.run=true to tail
Restart AS.

Going through the Known issues page(https://developer.android.com/studio/known-issues) found me the fix.

You have to set these additional PATHs
ANDROID_HOME = your SDK directory (android-sdk)
PATH=%PATH%;%ANDROID_HOME%\tools;%ANDROID_HOME%\platform-tools

Actual Solution
None of the answers here specify on how to debug the problem, you need to run the bin\studio.bat script in the terminal and inspect the actual Idea exceptions in order to fix the problem.
No need to re-install, delete precious configuration (and plugins, etc.). Just read the error message!
For me, this was the issue:
ERROR - llij.ide.plugins.PluginManager - java.net.BindException: Address already in use: bind
java.util.concurrent.CompletionException: java.net.BindException: Address already in use: bind
This means the plugin manager is trying to listen on a port that is not available. Is something listening on that port? For me, it is the stupid "excluded ports" by Windows, so I simply stopped the service:
net stop winnat (as administrator), and confirmed that Android Studio started to work.
Don't delete your configuration files, especially if you don't want to re-configure your settings. Just read the log provided by the bin\studio.bat script.

As of January 2016, the most recent canary needs the property written as as:
-Ddisable.android.first.run=true
otherwise it complains about missing JAVA_HOME. (using windows 10)

Fixed mine android studio by changing the system language, you can set yours to English go to Control Panel->Region under formats tab change the format to English(United states).

I had the same issue, I fixed it by changing the system language. Set your language to English by going to the Control Panel/Region. In the Formats tab change the format to English(United states).

I upgraded my Android Studio from 3.0 to 4.1 and after that AS always stuck on the splash screen. Fortunately, this section of the known-issues works for me https://developer.android.com/studio/known-issues#studio-config-directories

Fixed my Android Studio by changing the system language. You can set yours to English by going to:
Control Panel->Region
Under the formats tab, change the format to:
English(United states)
Thanks #ravi this also worked for me

As of March 2022, I was stuck in the splash screen was due to a plug-in conflict, but the IDE wasn't warning about it.
I received a warning balloon saying that I had the ExcelReader plug-in installed, suggesting me to install the new ExcelEditor plug-in, which is an improved (and paid ¬¬) version (I knew later). So I went and installed it and the IDE suggested restarting.
After restarting, the IDE always got stuck in the splash screen every single time I tried to launch it.
It wasn't until an hour later and so many launch attempts that, miraculously, the IDE launched and a dialog showed up warning about both plug-ins being not compatible so I had to disable one of them. It was a shame that it didn't warn me before. So I chose which one to disable on the dialog and it worked again.
Therefore, I suppose that if this were to happen again, it could be solved by editing the file /home/$USER/.config/Google/AndroidStudio2021.1/disabled_plugins.txt and adding the plug-in to the file manually.
In my case it was "com.chesterccw.excelreader" what I should have added. After that, of course, I uninstalled one of the plug-ins.

Studio doesn't start after upgrade
If Studio doesn't start after an upgrade, the problem may be due to an invalid Android Studio configuration imported from a previous version of Android Studio or an incompatible plugin. As a workaround, try deleting (or renaming, for backup purposes) the directory below, depending on the Android Studio version and operating system, and start Android Studio again. This will reset Android Studio to its default state, with all third-party plugins removed.
For Android Studio 4.1 and later:
Windows: %APPDATA%\Google\AndroidStudio<version>
Example: C:\Users\your_user_name\AppData\Roaming\Google\AndroidStudio4.1
macOS: ~/Library/Application Support/Google/AndroidStudio<version>
Example: ~/Library/Application Support/Google/AndroidStudio4.1
Linux: ~/.config/Google/AndroidStudio<version> and ~/.local/share/Google/AndroidStudio<version>
Example: ~/.config/Google/AndroidStudio4.1 and ~/.local/share/Google/AndroidStudio4.1
For Android Studio 4.0 and earlier:
Windows: %HOMEPATH%\.AndroidStudio<version>\config
Example: C:\Users\your_user_name\.AndroidStudio3.6\config
macOS: ~/Library/Preferences/AndroidStudio<version>
Example: ~/Library/Preferences/AndroidStudio3.6
Linux: ~/.AndroidStudio<version>/config
Example: ~/.AndroidStudio3.6/config
Note that the configuration directory for Canary and Beta releases of Android Studio is PreviewX.Y instead of X.Y for the . For example, Android Studio 4.1 Canary builds use AndroidStudioPreview4.1, instead of the AndroidStudio4.1 directory that is used for Release Candidates and Stable releases.
https://developer.android.com/studio/known-issues

just add this line disable.android.first.run=true at the bottom of the idea.properties file in the bin directory of the installation folder

Error message in Android Studio when trying to run and load emulator for the first time

The error message is:
PANIC: Could not open AVD config file: C:\Users\Darth\.android\avd\Nexus_5_API_21_x86.avd\config.ini
I've looked in that directory and there is no config.ini file. Only a userdata.img file.
When looking in the AVD manager the actions column says "Failed to load". If I right click it and click details it shows an error of:
Error: Failed to parse properties from C:\Users\Username\.android\avd\Nexus_5_API_21_x87.avd\config.ini
Fixes attempted that didn't work:
1 - Try choosing a different device definition. (config.ini file still missing when choosing multiple other devices)
2 - sharing the .android directory with my whole homegroup (selecting a device still doesn't generate a config.ini file, same error persists)
FIX: Thanks for all the replies. The fix that worked was changing the Memory of the AVD to 512!

I also had this same error, but the cause wasn't mis-matched x64 vs x86. Turns out my emulator failed to load because the skin wasn't defined. The way that I fixed it was:
Remove any previous wear emulators that failed
Pick the Model (Round/Square) and Android version(Lollipop, for instance)
On the final screen, click "Show Advanced Settings"
Scroll all the way to the bottom and set the "Custom skin definition" to "AndroidWearSquare" or "AndroidWearRound", which should be at the bottom of the skins list
Then after you're finished it should all just work!

Just put the Android SDK in the same Drive where you have installed the Android Studio 1.0. There is a problem if these drive letters are different. This will definitely work for you.I have solved this last week.

Try to use an AVD Manager from C:\User\<%USERNAME%>\AppData\Local\Android\Sdk\
https://code.google.com/p/android/issues/detail?id=78577#c25

For windows:
1) in the environment variables add a new "system variables"
ANDROID_SDK_HOME=D:\Program Files\android-sdk-windows (select your home directory of android sdk )
2) modify system variables Path, add "%Android_SDK_HOME%\tools;"

I have created many emulators and never touch .android\avd\Nexus_5_API_21_x87.avd\config.ini
you just create an Emulator, try to avoid "warp user Data", chose the appropriate Device and target API, set the SD memory to amount you want, and do the same with external RAM,and there is no reason to not work.
guesses: may the \Nexus_5_API_21_x87.avd\config.ini is read only! or you don't have permission to access .android/ (share this folder to all users,and give them full acsess.
I hope this will help

As I mentioned above I was facing the same issue.
For me it looks like the bug of the build and definitely not the issue rights, while another file was perfectly created (userdata.img) as well as the whole folder for the avd.
Solution #1: without changing anything in installation, I just found config.ini file in the internet. For example here is the config.ini for Nexus_S_API_21
So then I created Nexus_S AVD and put the config file in the folder. Then it starts working.
The issue with this method:
limited devices
config updates manually through config file
I still had some issues, e.g. instead of displaying the project I was displayed with the home page of Android, and there was no my app
Solution #2: Then I totally removed the Android Studio and cleaned all the stuff and downloaded 0.8.14 from scratch, during installation I updated it once to v.0.9.9. and then didn't update further.
In this version - everything worked just fine without any manipulation. AVD created from the first time and when launched - the project screen is displayed opened with Hello World.

I had the same issue and I was able to fix it with the below solution.
Root Cause: My system is 32-bit and the config.ini file was present in
C:\Users\Saajan Pruthi\.android\avd\Nexus_5_API_21_x86.avd
instead of
C:\Users\Saajan Pruthi\.android\avd\Nexus_5_API_21.avd
Note the x86... I simply copied the config file into the later folder and it worked.

I had the same issue inside Linux. The problem was that made install with root and executed the Android Studio from mi normal user, so in the momment that I install Android Studio every files android for emule stay here:
/root/.android/avd/Nexus_5_API_21_x86.avd
/root/.android/avd/Nexus_5_API_21_x86.ini
So you need do copy the files at your user, then:
sudo cp -Rf /root/.android /home/YOUR_USER
I hope that be help. Regards.

I did the following and it worked:
moved the sdk folder from C:\Users\User\AppData\Local\Android\sdk to the Android Studio program folder under C:\Program Files\Android\Android Studio\sdk
Restarted Android studio and reconfigured it to point to the new sdk folder
Recreated the emulator and started it

I had this problem as well. I just removed the AVD and added it back again - emulator is running fine now.

I had the same problem, and it turned out that my hard drive was full. For anyone still looking for a solution, definitely make sure you still have space.

PANIC: Missing emulator engine program for 'arm' CPUS

I am getting the same issue as mentioned in below link.But this one has been put on hold and I am still seeking for a solution.
https://stackoverflow.com/questions/27146511/panic-missing-emulator-engine-program-for-arm-cpus-eclipse
So I would like to frame the question and ask here. Until yesterday, emulator were working fine. But since today I am receiving the following error while I am trying to open emulator
PANIC: Missing emulator engine program for 'arm' CPUS
My AVD:
This is the error I am receiving:
I have updated and installed components through SDK Manager and I even tried to restart eclipse and my pc as well.
I tried creating new AVD But nothing worked here.
Thank You in advance.

In my case, my PATH environment variable was set incorrectly. It was including
<sdk-path>/sdk/tools
Instead of
<sdk-path>/sdk/emulator
emulator.exe exists in both of these directories, so the emulator command will work either way. However, emulator-arm.exe only exists in my emulator directory.

It is related to Avast Antivirus, has found bunch of emulator-arm files in its quarantine. Problem started couple of hours ago.
What I did as temporary solution: restored emulator-arm from quarantine, added it to avast exception, paused Avast, run AVD, then resumed Avast

This error happened to me when I re-formatted my computer and tried to copy and paste my old SDK files into my newly formatted computer.
I needed to re-download the SDK’s API stuff. For example, when I re-download API 19, it added these files in red and my Emulator for API 19 worked. API 18 & 17 kept giving me the "PANIC: Missing emulator engine program for 'arm' CPUS." error message. API 18 & 17 were the files I copied and pasted in.
Just delete everything and re-install it. Especially the Tools folder.

I had the same error but I solved it differently from the others. I was trying to create an emulator to test on an older Android version on my Mac.
My mistake was I had selected the wrong tab (see screenshot). I should have clicked the "x86 Images" tab instead of the "Other Images" tab to avoid this error:
Emulator: PANIC: Missing emulator engine program for 'arm' CPU.

This error indicates that there are some missing components in the Android SDK Tools!
In my case, for some reason, Avast Antivirus recognizes the tools/emulator-arm.exe as a threat and puts it in the virus chest!
This started happening since I've updated the SDK manager and everything to latest (tools 23.0.5)
Once I've restored the emulator-arm.exe file and disabled Avast for 10 minutes, I was able to start the emulator without problems!
Note: I've tried to add the file as exception to the Avast AV but it still removes the file from my system.
Please check if your SDK Tools installation is complete and update (delete first?) everything, or at least the Tools section in the SDK Manager!
I hope that helps!

I got the same error a few minutes ago. Look into antivirus chest and try to check if emulator-arm.exe is there. Try add the file to exception of antivirus.
It is working for me. (I have got avast!). Hope this will help you

I had the same problem in the same time as you guys and I am also using Avast. But I could not find the file in the chest of Avast.
So what worked for me was to reinstall the Tools of Android SDK:
Open Android SDK Manager
Select Android SDK Tools
Click "Delete 1 package"
Once it is done, reselect Adroid SDK Tools and click "Install 1 package".
Hope it helps.

I know this is a crazy old topic, but I ran into this same problem and had a hard time solving it. This topic kept popping up on all the searches
The quick work around is to simply copy everything from
/sdk/tools To /sdk/emulator without overwriting anything.
My path looks like this
C:\Users\MyProfile\AppData\Local\Android\sdk\tools

I got the same error too this morning... and I've got Avast !
"Restore and add to exclusion" seems not to work in this case, so i manually added the exclusion...
Solution:
1- Go to Avast Control Panel > Scan > Quarantine > Right Click on "emulator-arm.exe" > Restore and add to exclusion...
2- From Avast Main Screen > Parameters > Active protection (2nd item) > File Agent (click on the wheel) > Exclusions (4th item on the left menu) > Add the complete file path of emulator-arm.exe at the bottom of the list.
Then it works for me...

Avast Antivirus is sensing emulator-arm.exe as a thread and blocking from some reasons. When you add it exclusions in Virus Chest page with right-click -> "restore and add to exclusions" it's not solved in future runnings. To solve this permanently in Avast 2015 :
Settings ->
Active Protection ->
File System Shield ->
Customize ->
Exclusions then add thread as a exclusion . And then press ok.

in my case,there was missing arm eabi v7a system image for api level 22. After downloading it started to work. so make sure that Your arm eabi v7a system image is installed for the particular API Level

If you are trying to use an Android Virtual Device (AVD) with an Android Version, whose SDK platform version you have not installed, this error also appears.
Download all the Android SDK versions whose AVD you might use, i.e., be sure you have the API level installed whose AVD you will use.
Furthermore, check the first line the next image in the column CPU (this was also giving an error). Change the CPU of your AVD, to x86 and then it will work.

There can be the bugs / updates happened in the OS. So, instead of updating in .profile, /etc/environment, or .bashrc file to point adb, emulator etc, put (copy and paste) all the emulator folder inside /usr/bin directory. Install adb tool from the terminal. This should solve everything.
And/Or, update your all environment variables in /etc/bash.bashrc file. Note that: /etc/bash.bashrc file is what gets executed everytime you open the bash terminal.

Titanium Studio cannot find Android SDK (tried multiple solutions)

Okay. I'm kind of at my wits' end here. I've been trying for about 2 days to set up Titanium Studio to recognize and connect to the Android SDK (Windows 7). I have tried multiple solutions (below) with no luck. There's got to be something I'm missing. I've tried Google and the Titanium developer guides. So this is my last straw. Any ideas?
Android SDK home path is C:\Android\android-sdk (to avoid spaces with "Program Files")
installed all SDKs (3,4,7,8,10,11,12,13,14,15), their Samples, and all Google APIs
installed all "Extras" packages
Added both the Android tools and platform-tools directories to Windows' PATH variable
Copied adb.exe from platform-tools to tools as Titanium likes to look there for adb
Installed the current master build of Titanium SDK for Mobile Devices
Created Android Virtual Devices (AVDs) for SDKs 7 and 8 (Titanium's required SDKs)
Restarted adb server and computer itself after each change
On the Titanium 'Dashboard' tab, under 'Configure', I get:
An Android SDK is missing. Titanium requires Android platforms 2.1.* and 2.2.*
When attempting to set the default Android SDK path in 'Preferences', I get:
Could not locate the Android SDK at the given path
Titanium log file output (sorry, kinda long):
!ENTRY com.appcelerator.titanium.mobile 4 0 2012-02-22 14:06:21.992
!MESSAGE (Build 1.0.0.1327639206) [ERROR] [ERROR] The system cannot find the path specified.
[ERROR] The system cannot find the path specified.
Traceback (most recent call last):
File "C:\Users\Stick\AppData\Roaming\Titanium\mobilesdk\win32\2.0.0.v20120221190136\android\avd.py", line 45, in <module>
print get_avds(sdk)
File "C:\Users\Stick\AppData\Roaming\Titanium\mobilesdk\win32\2.0.0.v20120221190136\android\avd.py", line 21, in get_avds
for line in run.run([sdk.get_android(),'list','target'],debug=False).split("\n"):
AttributeError: 'NoneType' object has no attribute 'split'
I have no idea what's missing. Eclipse recognizes everything just fine. ANY suggestions??
P.S.
I've noticed that when I attempt to run 'android' commands, i.e.
android
android list targets
I get what seems to be an error:
The system cannot find the path specified.
However, the commands still continue to run with no issues (I get a list of all the targets and the SDK Manager pops up). I'm not sure whether or not whatever is causing that message is also causing Titanium headaches.

I was facing the exact same issue, but now I have figured this out and it was working fine.
Basically, when I install Titanium Studio and I configure Android SDK it worked fine, but when I try to execute Project there was "javac not found" error. While resolving this issue I came across a Post where it was mentioned to include '%JAVA_HOME;%' in your Path. And when I did this the Android SDK was not longer detected by Titanium.
I removed the '%JAVA_HOME%' from Path Variable and then I include Java bin Folder Path to Path Variable and created a new variable 'JAVA_HOME' which points to root directory of Java installation. Everything works fine after doing this step.
I hope you will now get your Titanium Environment running. :-)
Thanks.

Newer version of Titanium have the Update Android SDK option in the Dashboard. Just make sure, the path is correct. Some cases like mine, there might be two Android SDK paths; one was obsolete and the other was active. So, please make sure of that path. When Titatnium is about to update the SDK software, looking in for newer versions, please select Cancel, as that wouldn't be required!

open titanium ide.
click on file-> titanium mobile project.
a window will show up with a link Set-up/Configure SDKs in the
bottom. click on this link.
now give android sdk home: c:\Androi\android-sdk (or browse to
android-sdk folder in your system)
select the default Android Sdk
click Apply
Click Ok.
You should be good to go.
Let me know if you face any problems.