I have been studying Android on Eclipse Mars for some time and i have been facing a constant problem everyday-the changes made in a folder/file are not recognized by some other folder/file. For example, if i create a new layout in the layout folder and then use it in the setContentView, it shows me an error ("layout-name cannot be resolved or is not a field). It works if i save the project,close it, and open it again, but this takes up a lot of time if i have more than one error, so the question-is there a way to save and refresh the project (without having to close it) so that the newly made files and folders are recognized by the java files?
Thank you.
You can refresh your project in Eclipse by right clicking on the project root folder in your Project Explorer and selecting "Refresh".
You may also want to consider checking if you have "auto build project" turned on. In your top toolbar go to Project -> Build Automatically.
If build automatically is turned off you will have to manually build your project, by Right Clicking on the project in your Project Explorer and selecting "Build Project".
However, I do agree with Pankaj Nimgade that Android Studio is likely a better entry point IDE for Android development.
Real advice: Switch to Android Studio as soon as you can. There you would sometimes have another problem called "sync" though. But it's a much better IDE and you are at least in line with Google.
on Eclipse, F5 should do the trick. Or right click your project and Refresh. Or Clean all projects. If you are still stuck, simply close Eclipse and run it again.
Related
I'm running Android Studio 3.1.1 on OSx and I have three projects that all use the same local library projects / modules.
My problem is that Android Studio often opens the wrong project when I open one of those 3 projects. Let's say I open Project 2 or Project 3, then I might find that Project 1 is the project that is actually opened, even though it displays the correct path for all three in the "Welcome to Android Studio" dialog.
The solution I've been resorting to until now is to
Remove all three projects from the "Welcome to Android Studio" dialog project list
Go into all three project folders, removing the .iml file
Importing the projects back into Android Studio using the "Import project" function
I'm getting really tired of this, and it's really confusing to think that you have opened one project but another one opens instead.
What could be causing this very strange behaviour?
Sometime android_studio is catching the old cache, to solve this go file , hit invalidate cache and restart. And the second solution is, you have to Refactor the package name, every project should have the unique package name in this situation. i hope this will help...
https://developers.google.com/android/guides/google-services-plugin
go to this official link. It solved me this problem. In my case, ] deleted saved file in this path "app/build/generated/res/google-services/{build_type}/values/values.xml" which contains my previous app's information. After that, when I run my current app, it created that file again, but with my current app's info.
I followed googles instructions and exported a test project from Eclipse by using the
Export -> Generate Gradle build files
opened up Android Studio and imported. After getting my support libraries working properly my project would compile with out any errors. My problem started when I tried to run the app on my device. When ever I try to run the app it directs me to use an AVD, never giving me the option to select my device. I obliged, created a new AVD but to no avail only to get build failed error. (I'll add the exact error when I can) NOTE: I can see my device is connected by clicking on "(6)Android" and the bottom left of the screen. I do see all logcat messages in verbose. I added android:debuggable="true"to my manifest but still nothing.
Confused I created a new project directly from Android Studio, hit run and bingo,...it gave me the option to use my device to run it or an AVD. Selecting either results in a successful launch of the dummy "Hello World" app. I think it may have something to do with build variants as my imported project doesn't specify "debug" vs "release" while the Android Studio generated project does.
Anyone else experiencing this?
I found the answer to my own question. Bit of a double whammy. Before installing Android Studio I updated my SDK via Eclipse (as recommended/required by google). Turns out by doing so a few items in my current projects got disconnected. ie. build paths, dependencies, ect. (you now have to place external Jar's in the src/libs folder)
Here is what I did to fix it.
In Eclipse, Preferences -> Java Built Path ->"Order and Export" tab. Make sure items are selected
If you have external Jars, manually copy and paste the jar in the libs folder of the project. (I did this in my Finder)
confirm the project launches via Eclipse
If it runs, export the project again by "Generate Gradle build files" (confirm overwriting existing files, if any)
5.Open Android Studio and re-import the project. Again, confirming overwriting of any existing files.
6.Next to the run bottom at the top of the screen click on the drop down next to your project name. Click "Edit Configurations..." and select "show chooser dialog" if not already selected.
clicked ok to exit,..and PRESTO!!! I finally have a successful project migration.
Hope this saves someone else time.
Cheers!
Yeah i have experienced similar stuff on Eclipse, its quite buggy. Since Android studio is based on it i would expect everything. Still the best solution to everything is to reload project, refresh project or restart IDE.
I imported a sample 4.0.3 project and after deleting it from the Project Explorer list every thing is lost, now there are none of the projects that I was working before in Package Explorer??
Moreover now on importing these old project For Example name "On" are coming with the name "OnActivity" but still not able to run.
Else in workspace every file is ok, I tried to CLEAN but still no effect.
I'm new to devlopment kindly guide me.
Recover the source code from your workspace in the Windows file browser. If all attempts to recover fail, you can just create the projects from existing (recovered) code.
And what project are you trying to run? If APIDemo or QAActivity, the log shows you why you can't run them.
And instead of using the Play button (start) to launch, use the dropdown triangle and select the project to run, else the XML will be run (obviously that won't work).
Furthermore, make sure Eclipse knows it's a Android Project you're trying to run.
It is stuck in cleaning output folder for “Project”. It is not always the same Project. So is there some workaround ?
I tried the method of cleaning the project, but the library update happens too fast. I even assigned a custom keyboard shortcut to Clean and I still couldn't get it in there before it started.
I really didn't want to delete the .metadata folder because it is a pain in the arse to lose your workspace settings/preferences/setup.
So I tried:
Make a copy of the .metadata folder
Delete the original
Launch eclipse (it will open with a default/reset workspace), but it will open fine.
Quit eclipse
Delete the new .metadata folder
Make another copy of your original copy and rename it .metadata (basically put the original back)
Eclipse should now launch fine. In my case the Android Library Update still ran but it actually finished within a few seconds instead of hanging.
Then for me the underlying issue was one of my library projects got into a really broken state. I went into the properties for it, unchecked isLibrary in the Android tab and then refreshed the project. Afterwards I turned the library flag back on and did a clean.
I also had a build error in the library code that had to be fixed.
Any how, hopefully that helps if you find yourself in a similar position. Good luck!
So while I asked this question I found workaround for me , and possibly for others. You have to kill eclipse and on next start , do clean up on all projects before eclipse start that “Android Library Update” task and it will not stuck eclipse.
Deleting the .metadata folder works to get Eclipse back up and running, but after importing Android projects into the workspace the problem came right back for me.
In my case the underlying cause turned out to be the "Android Library Task" being stuck on trying to access the network. I'm connecting to the network via a proxy, and despite being configured in the global OS network settings and all other applications working fine, Eclipse was still unable to access the network. The only thing that worked was, after deleting the .metadata folder to get Eclipse running, manually entering the proxy configuration in "Preferences->General->Network Connections" to match that of the OS network settings.
Now the "Android Library Update" takes a second on startup instead of getting stuck.
In my case the other mentioned methods did not work for me
but "Reinstalling Eclipse and its all plugins" related to my project did.
After doing that it came to the normal state.
My env;
Eclipse Juno (under OS X Mountain Lion)
GWT
ADT
SVN
Another trick that works is to kill Eclipse, delete the ".metadata" folder from your workspace and restart Eclipse.
It'll force your workspace back to its initial state and clear up any hung conditions.
Since installing Eclipse 4.2 I have had to resolve this problem twice. The second time I knew that the only thing that worked for me was to create a new workspace and import the projects from the "broken" workspace. It is very fast and is a good opportunity to de-clutter by leaving obsolete projects behind.
Specifically,
choose File/Switch Workspace/other and put in the name of your new workspace.
Then right click in the Package explorer of the new workspace and choose Import and select Existing Android Code into Workspace.
Then browse to the root of a project that you wish to import and also select Copy projects into workspace.
Hit Finish.
You will have to do the same for any projects that this project is dependent on such as google-play-services.
Recently experienced this, caused by an Annotation Processor throwing an uncaught exception. Killed Eclipse, removed references to the offending Annotation from one project .java file, and started successfully.
In my case, within Eclipse, I had set up a C/C++ Builder to invoke build_native.sh, which is needed to build cocos2d-x. Interestingly, the Android Library Update indicated that it was invoking build_native.sh ! For me this explains why it was taking so long sometimes and seemed to be taking a LONG time to finish. I basically replaced this with an echo command. echo "do nothing" and I think this resolved the hanging issue.
This seems pretty goofy to me -- AFAIK, there's no way to configure 'Android Library Update', and I'm not sure why it's doing what it's doing, since Eclipse has a number of build options which the user can manually control.
Just my a new Android phone and I've been tinkering with some basic apps. It's been driving my crazy that the Android plugin for Eclipse refreshes externals folders whenever I save ANYTHING. Normally I wouldn't mind but when it takes 10s to refresh I start to notice.
I already searched and other people have this problem, but there are no solutions.
If it matters, Eclipse 3.5 running on a 64bit jvm on Ubuntu 9.10
If you have references to external sources put them in a zip file:
YourProject->rightClick->Properties->Java Build Path->libraries->..., and then most notably android.jar, but other libs can be the culprit too. Expand it and and select Source attachment, and then (if it doesn't say 'None') press the 'Edit...'-button. If that points to a directory waht you should do is compress that source-directory into a zip file and make the source attachment point to that file.
Apparently eclipse/adt feels the need to refresh sources on the file-system. When they're in a zip-file it seems confident that they have not changed....
You could try disabling "Build automatically" from the Project menu.
First of all Eclipse has a cool feature called a Preferences menu which is located under the window menu located at the top of the screen. Inside there are all sorts settings for pretty much anything you could want to adjust, including the option to turn off Native file system hooks and polling (under General -> Workspace). This is the actual solution to your problem as disabling build automatically doesn't solve the external folders issue, as soon as you build your project it starts right back up with refreshing them. Just keep in mind that if you update your Android SDK at all you will probably need to right click on the root directory of your project and hit refresh after the update finishes.
Secondly, as far as Netbeans is concerned there are at least a half a dozen pages worth of forums posts and various methods for using the Android SDK with it that are also available through Google, I'd give it a look.
I generally do the above step of turning off Automatic build and also try to have not more then 1 open project in my project list.
I myself am fed up of Eclipse from this. Importing a big android project 'ALWAYS' hangs my eclipse and i have to force close it and restart it.
P.S. I really wish google would create an Android plugin for Netbeans =(