Develop Reference

Export projects for Android Studio with different Unity versions

INTRODUCTION:
I exported android project from Unity version 4.6.1f1. After that, I imported it in Android Studio. I worked on a project for a few days and everything worked as supposed to.
When I change something in Unity, I just export android project again. In android studio, I delete ASSETS folder and then paste the new one that I get from Unity export. I did this in Eclipse to update my project. I am doing it now and everything works just fine.
PROBLEM PART:
Then, I updated Unity to version 4.6.2p2. I exported android project again. I changed ASSETS folder as usual. I also changed unity-classes.jar. I used this method in Eclipse before and it worked for me (apparently it worked for a lot of people, as my research on the internet confirmed it).
This does not work in Android Studio. I get error
Invalid serialized file version. Expected version: 4.6.2p2. Actual version: 4.6.1f1.
I tried: restarting Android Studio; cleaning and rebuilding project; syncing gradle; using other versions of Unity,... I also tried removing all dependencies, cleaning project, then adding dependencies again and rebuilding project.
I did not find any reference to this problem on the internet.
The only solution I get so far is to import project in Android Studio as new one and then do all the work again. But that is very undesirable.
Did anyone has this problem and come up with a solution that will not require making new project from scratch?

I did more research and here is the solution.
The problem is that Unity doesn't export all libraries together now. Specifically, libmain.so libmono.so and libunity.so are now separated and you need to change them also after you export project with new version of Unity (changing unity-classes.jar and assets folder is mandatory as before).
When you export project from Unity, you can find those libraries in libs/armeabi-v7a folder. In Android Studio, you can find them in src/main/jniLibs/armeabi-v7a folder.

Migration from Eclipse to Android Studio

So,
as it seems that more and more people are using Android Studio i got curious and wanted to take a peek at it.
I have used Eclipse up until now and wanted to migrate a project to Android Studio. So i exported a gradle buildfile from within Eclipse, as android.developer.com suggested.
That worked fine, now i wanted to import that into Android Studio 0.3.2
When trying to import i got that Unable to import Eclipse project to Android Studio error. Now it is building.
But it got a new suprise, now before it is finished building, its asking specifically for an older Version of Gradle(1.6)... Ok, i can do that. Which leads me right back to the first error. So i tried this - Gradle version 1.6 is required. Current version is 1.8-20130730220035+0000
I can however create a New Project with Android Studio.
I've tried this for about an hour now and im getting sort of pissed, because it doesnt seem to know what it wants. Is it some sort of Bug or did i make some sort of mistake.

You're using a very old version of Android Studio. I'd recommend upgrading to 0.4.3. Versions later than 0.4.0 allow direct import of Eclipse projects instead of requiring you to do the cumbersome (and as you've seen problematic) export of projects from Eclipse; it's smarter about setting up the right plugin and Gradle versions. 0.4.3 has some important bugfixes over 0.4.0-0.4.2.

I've just migrated my projects. Here is two suggestions from my side.
Take the latest Android Studio.
Do not export / import projects from Eclipse. Most likely you are going to have errors in the project after this step. Starting from a clean project, which builds, will safe you a lot of time and avoid unnecessary frustration.
Create an empty Android Project in Android Studio. It must build without errors (⌘ F9). The start to enhance it using official Gradle Plugin user guide.
Create libraries folder and add all libraries in there one by one. Update build.gradle dependencies as mentioned in user guide. Make sure everything builds successfully.
After all libraries build you can copy-paste sources, resources and assets from Eclipse project to corresponding folders of Android Studio project. Make sure everything build as expected.
Now you can start with more advanced configuration like ProGuard configuration, release certificates etc.
I've done it in a couple of hours. Hope this helps you too.

Eclipse stop generating R.java

Today, I update ADT to 22.0.1.v201305230001--685705, and found that Eclipse stopped generating R.java. I believed that it is problem of Eclipse, because I create a whole new clean android project, and I cannot even run it as android application. I cannot find any files under gen folder.
The version of Eclipse is 4.2.2, is there any way to solve it?
I try to use Eclipse 4.3 with the latest version ADT, but the problem is still there.

I had the same problem.
Open up the android SDK Manager, and install the new android build tools. Without this you will no longer be able to build anything.
For some reason they have seperated them, and a lot of people are not noticing.

Try deleting bin folder and clean the project..and In Eclipse, under the Project menu, is an option build automatically. That would help you build the R.java file everytime modifications are made. The Clean... option is also there under Project It seems to be a common issue with many different answers

Update android-sdk, I think sdk need Android SDK Build-tools. For update it follow some steps--
Go to Window->Android SDK Manager.
Update and Install all tools (Android SDK Tools, Android SDK Platform-tools,Android SDK Build-tools) which are in Tools folder.

Check the xml files of your layout whether they are properly saved with no error or not.
I have faced similar problem that suddenly R.java is disappeared and eclipse could not regenerate it after building SDK. I checked SDK manager and saw that Android SDK build tool is perfectly installed. Finally, I have noticed that there are some errors in xml files. After fixing and saving those, R.java generated automatically in my case.

Android R.java doesn't regenerate in Eclipse after SDK & ADT update

I have recently downloaded both the 2.3 and 3.0 SDK for Android using Eclipse.
I have also updated the ADT plug-in to 10.0.0.
However since doing this the R.java file in my project will not regenerate at all, I have tried every solution on the web that google can give me and none of them work.
So I imported my project to a different machine that only has the 2.2 SDK and an older ADT plugin installed and the R.java file regenerates fine on that machine.
Currently on my work machine I am trying to add a png to drawables but the R.java doesn't seem to pick it up meaning I cant use it in my project.
Is there something stupid that I'm missing that I should have done when I upgraded the SDK and ADT?
EDIT: R.java simply wont rebuild at all, even if I change my XML.
The issue is definitely with the 2.3 SDK or ADT 10, it works fine if I have 2.2 and ADT 9

I recently had this problem as well. In my case I had type-o in one of my resource xml config files. This error caused the resource builder to terminate and my R.java was never built. I tried to delete it first to trigger a rebuild but that did not work.
I temporarily removed the resource file causing the error and then did Project -> Clean and the R.java was correctly built again.
Not sure if will help, but it might get you going in the right direction.

Its a bug within ADT r14 and it isnt really fixed with r15 or r14. Only thing I can think is to unistall and redownload the older ver 13 and keep using the code from there.

try to clean and Build workspace from eclipse=>project->clean.
me done this it work for me..

Could not find ****.apk + android

Whenever i am trying to run my project, i am getting this error in the console.
"Could not find **.apk"
Operating system: windows XP
IDE: Eclipse SDK
Version: 3.4.2
Build id: M20090211-1700
Android: 1.6
ADT: ADT 10.0.0
FYI: it is only happening with a single project, other projects are running fine..

I think this can happen when you rename the library project out from underneath the dependent project. Eclipse is reasonably good about about updating dependencies in most cases but this one seems fragile.
First try removing and then re-adding your library in Project > Properties > Android > Library.
If that doesn't work try cleaning your projects, exiting Eclipse, and opening the ".classpath" file in your project's root directory. If you see a line that references your library project under a previous name, just delete it, save the file, and relaunch Eclipse. Build the library project and then your dependent one. You may need to re-add the library like I mentioned above. This is what worked for me at least.
Edit note: I also found some stale references in my .project files. They didn't seem to be causing any problems but I removed them too. If you do that, be sure to search for the old name in that file as there was a whole "link" section near the bottom that also referenced it.

Make sure after updating your android sdk sdk build tools are updated properly.
You can check it by Open sdk manager -"Android Sdk Build Tools" status must be installed.
if the status is not installed then install Android Sdk Build Tools for the same.

restart your eclipse and try again
check this it might be helpful to you

Make sure your project imported the Android 1.6 library correctly. That is, under your project, you should see 'Android 1.6', which expands and displays 'android.jar'.
If it says Referenced Libraries > android.jar, you will need to fix this by manually altering the .classpath for the project.
Open .classpath for the project and type the following:
The important line is the 3rd classpathentry, which is the actual link to the Android SDK libraries.
source

clean your project and check . eclipse is not building apk file.
check this thread. It might help you.
http://groups.google.com/group/android-developers/browse_thread/thread/2c3e45540b915945/f06e10bcda3ad68b?lnk=raot&pli=1

Run eclipse as administrator and then import your project

Update Android SDK, is what did it for me.
I was building a game with the LibGdx Framework and got the same error. I tried several solutions from various posts at stackoverflow and others.
Found help in a post at the LibGdx Forum:
http://www.badlogicgames.com/wordpress/?p=3010 Posted by Mario, on May 18, 2013
Just updated to ADT 22, so should you. However, the process wasn’t all that smooth. What you need to do:
Update the ADT plugin in Eclipse (Help -> Check for Updates)
Open the Android SDK Manager, either from within Eclipse, or from
your Android SDK folder
Fetch all the updates
Fetch all the updates again
Fetch the updates one more time…
The end result should be an updated ADT plugin, as well as up to date SDK packages. Make sure you have all three of the ones in the following image, with the exact version numbers.
I needed to update them only once and from there on it worked.
Even if this post is outdated I figured I'll share this, because I lost a day finding nothing.

I experienced that problem, too, when I created an android project that was using an android library. Obviously I didn't know how to incorporate a library into an application the right way. I wrongly used project dependencies (Java Build Path/projects) or adding a library (Java Build Path/Libraries). While all I had to do was go to the Android tab and import my android library by means of the add button from the Library section.

I am using PhoneGap and I checked several solutions about configuration (properties, build path). However, my problem was that I tried to run everything with the default setup for Eclipse. Then, I solved it going to the SDK manager to install: Android SDK Build-tools, and it worked.

Mine was caused by this problem (incompatibility between ADT and SDK), and was fixed thus:
Eclipse > Help
Install New Software
Add 'https://dl-ssl.google.com/android/eclipse/' to 'Work With'
section and press enter
After developer tools appears on the list, check it and click Next
Restart eclipse once download is finished

Make sure put correct SDK Location (I have 2 instances of SDK and update wrong once).