The exact problem described in this nine-month-old question suddenly (and apparently spontaneously) manifested for me today. It worked as recently as a few days ago. None of the answers on that older question solved the problem. In addition, I've tried updating all my Eclipse plugins to the latest versions, and tried creating a project in a clean new workspace. No dice
Has this happened to you recently? What is the solution?
(On a side note, can anyone explain why the most popular program used by programmers to write programs is such a complete piece of garbage? Grrr...)
Edit: After attempting to fix this via all the suggested methods, I have now also lost the ability to do Team > Revert... on any file or project. Yay! Looks like I'll be getting familiar with Android Studio this weekend.
Related
I am trying to create a LittleKT project in Visual Studio Code. I tried building a Gradle instance of the project but was told that I did not have an Android SDK. I installed the Android SDK Tools and got pretty far. I was unable to use a key emulator that I needed and was wondering if I could completely remove android support for my project.
Any advice pertaining to LittleKT or how to install the needed emulator I need would be greatly appreciated. I did not include many details as to doing that because that is not the point of this question. Plus, there are plenty of discussions pertaining to that issue.
Thanks
Hi everyone,
I'm trying to implement a swipelistview into an android project with Android Studio, of course i'm using gradle, so i try to download the library from a repository, some odd things I realised so far:
The git repository of 47deg/swipelistview is no longer working. (404)
Also the repository from where gradle tries to download the library is no longer accessible 'http://clinker.47deg.com/nexus/content/groups/public'
The project worked like a charm just one week ago, I have an APK witch is deployed in my phone and i'm looking to it as am writing this question.
This happened days ago when I tried to open the project to do some enhancement to the app, nothing related to the swipelistview thought. And when I try to build Android studio says Cannot resolve
com.fortysevendeg.swipelistview:swipelistview:1.0-SNAPSHOT#aar
I tried removing snapshot#aar, changing version of swipelistview... no result.
Question:
Is there a problem with the repository I'm trying to download from?
If not, what are other libraries that can replace the swipelistview library?
I also checked all the related stackoverflow questions, I updated my Android Studio, changed version of gradle, tried to find a Jar of the library, but all of this without any positive result.
Thanks in advance for any efforts you put in this thread. I'm available for any clarifications.
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
I'm using Android Studio and I'm close to just canceling the Android version of my app and just sticking with the released iOS version. I need to use an expansion APK and I cannot for the life of me get the downloader_library to import into Android Studio.
I try and run the project and it says it can't find anything from the expansion downloader. I've tried everything I can find on the forums. I've tried bringing into Eclipse and exporting out. I just can't get this to work.
I don't know if I have some kind of fundamental misunderstanding about Android and libraries and modules and things but I'm about ready to give up on this unless someone has an easy way to help me through. This is the very last step. I have the IAB working, the app works on multiple devices, the performance is good, I just can't figure out this splitting of the APK.
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.