I have a javascript file (ParameterFunctions.js) which isn't making it to the device for some reason.
It's definitely in the project:
I extracted the apk and it's definitely inside of it:
When I look at the files on the device is doesn't exist:
Why is this happening and how do I fix it? I've tried:
Invalidate caches and restart
Uninstall and reinstalled
Sync project with file system
Sync project with gradle files
Reboot the device (both before and after reinstalling)
I figured it out. There was a syntax error in the js file I was trying to include. Rather than report it Android decided that the entire file shouldn't be recognized.
I just got a new Xamarin.Forms portable project in Visual Studio, and I'm trying to run it on the VM.
When I run it, this error appears:
Error encountered while loading the project...
How do I fix it? Every project I start has this error.
I think of 2 possibilities here where I've faced such problem
Broken/ incomplete downloaded zips
This may have occurred because you cancelled or closed the VS out of frustration because it was taking too much time.
while in fact the visual studio is downloading the zips at AppData/Local/Xamarin/zips. because you closed visual studio, the zip files are not completely downloaded.
what you do is go to AppData/Local/Xamarin/zips delete all the zip files then AppData/Local/Xamarin you should only see Universal, zips and logs folders delete the rest. wait for the zips to install completely. this is gonna take time for sure.
Problem with the References
Check if any of the references are showing any warning sign or something. if so remove the reference and reinstall it.
This fixed it for me:
Close your project
Locate the project's *.suo file and delete it (it may be a hidden file, don't remember)
Reload your project
I get the following error sometimes during compling and running the application using eclipse.
Failed to install ABC.apk on device '4df11bd574734fd9': Local path
doesn't exist. [2013-08-20 09:28:04 - ABC]
com.android.ddmlib.SyncException: Local path doesn't exist.
[2013-08-20 09:28:04 - ABC] Launch canceled!
The pop up in eclipse says that, the application contains some errors, which I need to fix.
I have updated my eclipse and other related things to latest.
I followed all the posts whihc talks about resolving this error, but none of them work for me. I see that once I get this error, my bin folder is kind of locked and I cannot delete it. Currently, the only option left for me is to restart my laptop and then it starts to work again but it is very tedious and time taking.
Can someone suggest me what should I do?
Well finally I make it. there was a program/process that has blockep miapp.apk file, so when I tryed to clean my App it doesn't drop this file. I stop the program/process and delete manually apk file. now its running great.
okay i found the solution
just transfer all your project directories except bin directory into another folder location of same name as your project name.Now import your project from new location.your project will run this time
Also suffered from this issue. The culprit turned out to be Google Drive, which for some reason locked the .apk file after I shared it to my Drive and then caused all kinds of headaches.
Closing the Google Drive tab fixed the issue.
I built a parallax live wallpaper with andEngine. I exported the .apk without any problems. I copied the project, updated the package and app name and everything needed to republish as a new .apk. The app tests fine on my tablet. But when I try to export it, it throws:
conversion to dalvik format failed with error 1
After hunting forums, here are the ways I've tried to fix the problem to no avail.
Update proGuard to it's latest version.
Updating the SDK to the latest version.
Removing project from workspace, changing it's directory and re-importing.
Removing everything but Android 'version#' in Java Build Path->libraries
Removing everything in Java Build Path->libraries and ran fix project properties.
Removing and regenerating the R.txt file in bin.
Clearing the .jar file from the libs directory.
Changing my .apk and keystore directory.
Cleaning the project after all of the above.
Refreshing the project after all of the above.
Running fix project properties after all of the above.
Occasionally the exporter won't throw the error. But it doesn't build the .apk, it just builds the keystore and closes.
I'm pretty stumped. If anyone has insight it would be invaluable.
Thank you so much.
I had the same problem with the latest Android SDK (API 17). I tried all of the above without success. Then I reverted all changes and this is what works for me now:
Clean project
Turn off Eclipce
Clean temp directory (on Windows, %TEMP%)
Turn on Eclipse, export (sometimes I clean the project once more)
What usually happens is that the temp directory will contain some files from previous export that cause problems and you can't delete them while they are used. Hence the "Turn off eclipse" step.
Note that some files will stay in temp and you won't be able to remove them - don't worry about it, some other programs use them.
Every time I open Eclipse, I get the following error messages:
Android SDK Content Loader:
parseSdkContent failed java.lang.NullPointerException
Initializing Java Tooling
An internal error occured during: "Initializing Java Tooling". java.lang.NullPointerException
Loading data for Android 2.2
Parsing Data for android-8 failed java.lang.NullPointerException
Loading data for Android 2.3.3
Parsing Data for android-10 failed java.lang.NullPointerException
Loading data for Google APIs (Google Inc.)
Parsing Data for Google Inc.: Google APIs:8 failed java.lang.NullPointerException
See link for screenshot:
http://i.stack.imgur.com/lhhQQ.png
(I am using OS X Lion, and Eclipse Helios)
First i read some posts saying that it was the AVD.ini file in the .android profile that was causing the trouble. I tried deleting all the entire .android profile folder as suggested in Android SDK Content Loader failing with NullPointerException. This didn't correct my problem.
I tried deleting the entire Android SDK folder, downloaded it again and installed a couple of Android versions through it. Still the same error messages...
To ensure that I didn't have any old plugins or something that were the issue, I uninstalled eclipse, downloaded it again and installed the Android plugin again. (So the plugin is up to date).
When I go into one of my Android projects, I get error messages on places where I acces resources by using the R file. Regular Java projects work fine, but all Android projects gets small red boxes with white crosses on them. I have been searching for a solution to this problem since yesterday, but at this point I'm completely qlueless and would appreciate any help I can get!
Close all open projects and exit Eclipse. Now you can open Eclipse without getting the error. Start opening your projects one by one to find which one causes the problem. This is most likely because you deleted a Device profile inside the AVD manager.
Do not delete all the full .metadata
Backup .metadata
delete only .metadata/.plugins/org.eclipse.core.resources/.project
restart eclipse
Observation : the projects folders are created
Further - if you are using svn/git/hg have code repository links it would be destroyed, so to reinstate
close eclipse
copy relevant projects from backup to merge with current projects in .metadata/.plugins/org.eclipse.core.resources/.project
restart eclipse
Downfall - sporadic fail error may occur (sync or something) - harmless
backagain
I encountered exactly the same issue this morning. This is a workspace related issue.
Solution 1
I looked into my .metadata and read .bak_number.log files . Some layouts failed to parse and my projects were out of sync with the file system.
So I deleted all the .bak_number.log files. Relaunch Eclipse and the whole worskspace should work again the way you left previously.
Solution 2
However if it's not due to out of sync with the file system. Change the workspace then import all the eclipse projects from the previous workspace.
Thanks the project.properties files , the dependencies are still kept.
PS : I should return to IntelliJ :)
first close your Eclipse
Go to your workspace and rename .metadata to tushmetadata and go to
tushmetadata- >.plugins -> org.eclipse.core.runtime -> .settings
and copy all files from it.
now open the Eclipse and go to your workspace there you can see the
newly generated .metadata folder in that go to .plugins ->
org.eclipse.core.runtime -> .settings and paste here and do not
overwrite any file.
Try to "Hello World" project and run it.
Try to delete file .metadata from your android workspace folder. .Metadata folder contains all configuration files for eclipse. It works for me.
Your answers might be right. What I did was to change my workspace. I redownloaded the project I was going to work on from git, and reimported it. Now it works fine :) Maybe there was some files in this project that made the error messages apear? Dunno....
I have remove the .metadata folder but after it, when I run the eclipse, I cannot creates any Android project. To solve it, I have done the follow:
Go to the main work directory of eclipse
Localize the folder com.android.ide.eclipse.adt It should be in .oldMetadata/.plugins/
Copy it to the new eclipse configuration: .metadata/plugins/
See the full solution here:
http://www.jiahaoliuliu.com/2011/06/running-android-sdk-in-eclipse-errors.html#solution4
For me, the source of the NullPointerException problem was a host-side Junit test project that references (and tests) code from an Android project. It didn't have a project.properties file. It's not an Android project, but for some reason the newer versions of the SDK somehow expects the file there. To fix the problem, I just copied a project.properties file from an Android project to the host unit test project.
When I met this problem about a year ago, I had some projects in my workspace that needed a specific Android SDK level (let's say 2.1) and i didn't have it installed in the Android SDK.
slott's answer helped a lot. Deleting the .metadata or reinstalling eclipse didn't though. The trick was to isolate the project causing the problem, delete its .settings folder and .project file and reimport it.
I discovered another cause, where I'd added a space character into an otherwise blank line in the project.properties file. When I eventually ran android update project -p .
the program (android.exe) threw a NPE exception. When I deleted the space from the blank line the android update project command worked and eclipse started behaving (after running clean a few times).
This happened with r20 of the Android SDK on a Windows 7 64-bit machine.
FYI my change that fixed the problem in project.properties is public at http://code.google.com/p/android-daisy-epub-reader/source/detail?r=517
This is just weired.
In my case when I took a subversion update, I was getting this problem. The reason was the corruption of my project.properties file (due to subversion conflict).
I just corrected the file and problem got solved.
I found it's just missing project.properties file in the project folder. After copying one from another project the error is gone. The only valid line in project.properties is
target=android-8
If you are using SVN or GIT please check whether the project.properties has conflicts or not.
Sometimes project can not be open because of this.
I hope this is useful to someone and saves his/her time: My colleague was facing same issue and we did almost everything mentioned here, with no luck. In the end we changed the Android SDK version in the manifest file and it worked.
This solution worked for me.
Close Eclipse and delete all .markers inside your workspace folder.
Restart Eclipse (once I had to restart it twice, it hang on the first but worked on the second for no aparent reason).
Of course, it's always safe to back them up first.