I updated my Eclipse to have the newer version with latest Android ADT. I decided to update it by doing a "simple" install of the whole package provided by google. The package version is adt-bundle-mac-x86_64-20130219. Now, I still have a code assist for java but not for Android API. I spent a long time searching google and Stackoverflow and none of it solved the problem. When I go to menu ADT> Preference> JAVA> Editor> Content Assist> Advanced, I see that the choice "API Tools Proposals" is missing from the choices. I believe this is why I do have code assit for regular JAVA stuff but nothing for Android API. I tried to create a new workspace and import the project in it. I made sure the Android libraries are in the compile path. The are because the compiler reports some error messages related to Android API when compiling telling me I should implement some methods when extending a "BaseAdaptor" so, the compiler knows where to find the libraries.
I tried the trick where you add the "-clean" in the "eclipse.ini" file. I don't have years of experience in Android programming so Code assist for Anbdroid API is very important for me. Any Idea how to bring it back?
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
In my project I am integrating push notification for that I require classes from com.google.android.gms package.
Is it possible for me to include selected package from whole library?
I am using eclipse. actually there are lot more libraries required, due to which I am facing 65k multidex issue. Any solution?
If you really really want to use the Eclipse to compile this, you need to perform these steps:
Have someone with Android studio include your needed Google components as dependency.
Kidnap the components from exploded-aar Android studio folder and setup the components as your own Eclipse library.
But of course, this is highly not a recommended procedure, but this is for those people who desperately needs it as last resort. This also marks a disclaimer that the kidnapped libraries are already free from the developer's accountability, because you didn't compile it the right way.
PS. Did this with Google Maps
If you want to use selective components of the Google Play Services you will need to switch to Android studio.
Read this: (Source)
Important: Support for the Android Developer Tools (ADT) in Eclipse
has ended, per our announcement. You should migrate your app
development projects to Android Studio as soon as possible. For more
information on transitioning to Android Studio, see Migrating from
Eclipse ADT.
If you still want to continue using eclipse, you'll have to to the hard work yourself - of deleting the unwanted packages/components from the full source code and making sure it compiles and works fine.
Instructions of setting up selective APIs can be found on this page, for android studio. For Eclipse, as the documentation says nothing about setting up selective APIs, you just have to go with the whole set.
NO. you have to migrate your code to Android Studio.
I'm using android-sdk-plugin to make Android apps with Scala using SBT. This generally works great - however when trying to import the project into IntelliJ IDEA 14.1 the imported project looks rather empty and does not recognize my source files as being part of the project.
The documentation says:
IntelliJ 14 now includes native support for importing projects from android-sdk-plugin. The process generally works well, however there are still several caveats:
The idea-sbt-plugin is still required to actually perform the build (no longer necessary as of IDEA 14.1)
Cloning and importing even the simplest example project results in an empty IDE not showing any sources at all:
I have installed both the Scala plug-in and the SBT plug-in (which I believe should no longer be required) as requested by the documentation.
What essential step am I missing?
Edit: I added the plug-in manually to project/plugins.sbt, then ran gen-android to get a project/build.scala containing object Build extends android.AutoBuild.
The essential step missing is the Android plug-in of IDEA. This might seem obvious but in contrast to plug-ins for other frameworks this one does not just provide extra goodies but is actually essential for anything Android.
Having the plug-in installed allows for selecting Android as a Project SDK (which not just selects an Android SDK but also a Java SDK to go with it).
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.