As a student learning Android programming, the newest update to Android Studio 1.4 has been a total cluster****. There have been a number of new files added to the project you get from using all the defaults. Deleting any of these files, or deleting any of the values in some of these files, results in a slew of errors in the Android Manifest file. I would really like to avoid dealing with all this, so here's my question:
Is there a way to rollback an update in Android Studio 1.4?
I'm guessing the answer is no. A search of the web showed a few promising hits, but these were all for releases in the 0.* range. And developer.android.com is silent on the issue.
If the answer is no, am I screwed if I don't have an installer from before this update? Or should I just ignore the files for now and not delete any lines of code in these files I am not using. Just starting out in this, I understood quite clearly the files that USED to be generated by the default project settings. All these new files they just tossed in? I'm clueless (for now).
You can find some older versions of Android Studio here: https://developer.android.com/studio/archive
Related
I have a problem and I would like your help :)
I received a native Java project from Android Studio and I want to know how I can configure my environment, the first time I tried I had a lot of errors with gradel.
Is there a way to know exactly what settings are needed to start project maintenance?
As long as you have installed Android Studio and are able to create sample projects, you should be set up.
Gradle should show you all the problems which your legacy project has. I assume, that you will see a lot of warnings which can be ignored at first.
You might have problems with a missing key.properties file.
Some dependencies might not be available anymore.
You have to resolve all the issues manually. There aren't any special settings.
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
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.
Is it possible to create a new project without gradle support in Android Studio, i.e. likewise in Intellij IDEA IDE?
I found one way only: create new project with IDEA and reopen in AS :-(
Unfortunately, I don't know such preference or option in AS. If you found it, please comment.
ps.s Gradle is a big pain at least in current AS beta 0.8, I spent more than 80% work time to fight with it's fatal issues. I think Google team must make AS more and more friendly to developers, never used gradle.
As far as I understand android studio is dependent on gradle as the build engine, and therefore you couldn't create an android project without gradle support
the Java sources for the Android framework are available at source.android.com. Can I download and feed them to Eclipse so that I can step into framework methods while debugging? Better yet, does anyone know of an Eclipse plug-in that would get them from Android Git automatically as needed?
EDIT: during debugging, I can step through the framework code; I can see local variables by their declared names, and line numbers as well. It seems like the debug info is already there - only the source file is missing. While I can open it in parallel and watch the execution unfold, the question of version matching remains. Of many versions of the class file in Git, how do I pick one that matches whatever is running on the device (or emulator)? This is more of a Git navigation question - how do I pick up the very version of the file that went into Android release, say, 2.2?
EDIT much later: now sources come prepackaged with Android SDK. This question is somewhat obsolete.
This article nicely explains how to accomplish this: http://android.opensourceror.org/2010/01/18/android-source/