I imported a project from Intellij (pre-Gradle structure) to Android Studio (latest version) by simply copying the files into a new project and making the corresponding changes necessary (loading libs, changing package names, etc.)
It works nearly perfectly except for there's a bug with all the animations and placements of views.
Can this be a problem depending on the IDE or is there something wrong with my code? (I tried the code in Intellij and it worked perfectly after importing the problems occur).
Thank you very much in advance!!!
No. The IDE itself changes nothing about how an application is built or runs. The IDE exists to provide a convenient way of viewing and editing your code.
The most likely culprits are using different versions of the build tools or using different versions of libraries.
Related
Im not really sure how to being this... this started a couple months ago every so often i would receive apk install failed errors and when i unzipped my built apk and looked at the android manifest mine was replaced with a android manifest from a sample serial port library i was testing with a while back. This problem has become constant to the point where every 3 builds or so i have to use the visual studio installer to repair visual studio. Cleaning the solution doesn't fix it nor does deleting my local visual studio files or bin/obj folders. I have cloned my solution over to my personal desktop and it built fine and has never exhibited these problems so i believe its environment specific. if anyone has run into a similar problem or has any suggestions i would greatly appreciate it.
With Xamarin.Android some of the AndroidManifest.xml file is generated at build time.
All types which have [Application], [Activity] or [Service] attributes and their extra stuff like [IntentFilter], [MetaData] will be added to the manifest at build time.
You can verify this by comparing Properties/AndroidManifest.xml to the one generated which usually can be found in the obj/Debug/Android folder. You should see that your Activities are added there.
If you use the Xamarin.Android.ManifestMerger package, additional content from Android Libraries might be added to the manifest as well
I found the problem! the newest non preview xamarin android will do this if you have a bound jar . here is a link to the github issue this should be fixed in future versions for now im updating to the preview visual studio.
https://github.com/xamarin/xamarin-android/issues/4804
I have succeed to run my android project from Eclipse to Android Studio simply by generating its gradle build (without changing the project's structure).
I would like to change this project structure to the Android Studio's format, however im afraid this p**roject will not be working anymore in Eclipse**.
Have someone did this before?Did the re-structured project still working in Eclipse? (I have a bad feeling about this)
Note : If you wondering why i dont try it before asking, its because the project is fairly complicated (around 5 libraries also need to be restructured and i only know a very little about gradle) so it will be nice if i know it will be working.
Thanks everyone.
So I've been trying to install libgdx for a few days with Eclipse and it kept telling me various things (Android ADT, Java JDK, etc.) needed to be updated, so I did that, but I kept getting the same error.
Then I decided to download an older version (0.9.8) and I used the gdx-setup-ui.jar to set up my projects. But upon opening them in the Eclipse/ADT bundle, the Android and HTML projects had errors in them involving the import statements, which I tried to solve to no avail.
This is the tutorial I've mainly tried to follow.
Does anybody have a solution for me to get it to work? I'm most familiar with Eclipse, having worked with it for Android for a while now, so I'd prefer not to switch IDEs.
Thanks in Advance
Use ADT (Android Developer Tools) instead of Eclipse. (Is the same thing anyways)
http://developer.android.com/tools/index.html
If you got errors after importing your projects on android, right click on the android project, and at android, check the version that is there.
For HTML you need to install the GWT plugin.
Recently libGDX has moved to Gradle, so you might want to look over that
https://github.com/libgdx/libgdx/wiki/Project-Setup-Gradle
Well I want to highlight this and bring it all in this thread, as the rest of threads did not have a concluded answer, so before skipping into them here are the threads I referred to:
Adt doesn't create default hello world but command line does
[solved ]Eclipse behaving differently while creating new project/activity
ADT has been behaving a bit weird since past few days. I keep my SDK always updated so I frequently Run the SDK manager and download all the updates. recently I noticed that if I create a new android app project it is not creating a default MainActivity even if I check that box, it does not create a Activity under src and more to annoy me, I wasnt able to refactor anything, so I realized that I had to update my Eclipse as after reading few posts, but now when I create every new project it creates an annoying appcompat_v7 project with EVERY project, say I create two new projects it creates appcompat_v7_2....this is driving me crazy and the new project library is the appcompat_v7 project. This is becoming annoying and no idea whats going on here !!!! What should I do...please rescue me ! Thanks in advance ....A screenshot to annoy u guys too ... :)
***************Current Alternative, not a solution***********************
As of 12/5/2014 with ADT 23.0.2 I dont see this issue anymore.
I have waited for an acceptable solution on this issue (as of now there is none), but one of the SO members directed me to this post https://code.google.com/p/android/issues/detail?id=66975. What I am doing is described in one of the solutions below, but for people who have come to this post, the alternative is to delete that ugly project(if you have more than one) which has been created and add up this one(appcompat_v7) as a library. So if you create another project and appcomat_v7_2...comes up delete that and point your project to the appcompat_v7, do the same for other projects too. This is not recommended for some reason though, but it worked well for me till now without issues. If anyone hits up with a solution please post it here.
****************Current Alternative, not a solution*****************************
the folder appcompat_v7 doesnt get created if i use
minSdkVersion="14"
Seems like it is a eclipse bug. What you need to do is go to properties in the of the Android Project and in the Android Section. Add the library appcompat_v7 and remove the appcompat_v_7_2 (duplicate). Then you can remove the appcompat_v7_2 as a eclipse project. All errors fixed.
Just a workaround.
The appcompat project is a library to support android's older versions. The support library was introduced by Google recently - I don´t know in which Android version.
But the point is, this project is only created when you create an Android project to cross Android platforms. I mean, when you select an old min API, e.g. API 8 (Froyo), but target recently versions, your project must have the support library.
Anyway, the creation of appcompat_v7 project is some issue that has to be better configured by the eclipse plugin maintainers. However you can elegantly turn over this issue by targeting newer APIs and including in the build path the support library. This is more elegant than the others because it is better to you focus in only one android version when building your application, and when it is done, you have an authentic version of your app that you can use as a mold to support other versions, either older or newers.
I am working with a complex library that, for historical reasons, is separated into two Android library projects that reference each other. Prior to r14 of the SDK, this worked fine. Each simply referred to the other's source code. We released a jar, and in Eclipse, applications could refer to the two library projects.
With r14, Eclipse tries to build a separate jar from each one. Since each references the other, they both fail. It may be necessary to construct a single new library project from the two. But that's development work and presents other problems. For now, I'd like to instruct Eclipse and ADT to handle them as before, i.e. not to build jars from them, just to reference the source. I've been digging, but I haven't yet found a way to do that.
Thanks in advance for any advice.
The answer is probably no. We worked around it using source links, which improves matters tremendously. This mechanism didn't work with previous ADT versions.
The other solution that would work is using apklib project that you create with the android maven plugin.