I am using Android Studio 1.0.2 on Mac to develop an app for Google Glass. I have been trying to start with one of the recommended projects that Google supplies on github, but I'm running into a problem. The instructions say to open Android Studio, select Check Out Project from Version Control, select Git in the dropdown menu, choose a location for the files, and then paste the url to the github. So I paste the url and when I click the test button to check the vcs repository url, it says the connection is successful. The problem occurs after I click Clone in this window. All documentation that I have read states that one or two more windows should pop up and that I should select OK in both of them, however, nothing ever shows up. The project never opens, and when I try to find the project following the path I chose, there is only an empty folder with the name "gdk-stopwatch-sample". So, what's going wrong?
I have also tried downloading the zip file from github and then trying to open it via another selection in the Android Studio Startup window like Open an Existing Android Studio Project or Import Non-Android Studio Project but I am very new to Android development and I cannot seem to choose the correct gradle import settings so the projects never run or build correctly if I can manage to open them. I am convinced that the easiest way to start this process will be to check the project out through version control, but I don't understand what's going wrong and I can't find any documentation that discusses this problem. I would greatly appreciate any help on how to get this going.
App found here:
https://github.com/googleglass/gdk-stopwatch-sample
Instructions found here under Before You Begin:
https://developers.google.com/glass/develop/patterns/ongoing-task
I've met with the same problem as you. (also Android Studio 1.0.2, but on windows)
Here's the solution I've found:
for Check-out/clone issue, make sure you've installed git and it is accessible in your android_studio.
At Android_studio, set the git in the following settings page
(My path is under Windows...)
to open the gdk-stopwatch-sample project (using the local gradle_2.2.1), make the following modifications
(1). \gdk-stopwatch-sample\app\build.gradle
(old) runProguard false
(new) minifyEnabled false
(2). \gdk-stopwatch-sample\build.gradle
(old) classpath 'com.android.tools.build:gradle:0.12.+'
(new) classpath 'com.android.tools.build:gradle:1.0.0+'
(3). install SDK Build tools v20 (from SDK manager), if not yet.
If your gradle plugin version is 0.14.0 or higher, you have to go to your build.gradle file and change "runProguard" to "minifyEnabled". You can read more about the recent changes here: http://tools.android.com/tech-docs/new-build-system
Related
I'm new to Android development (and to gradle), as is our small team. We have one developer who has been working on a project for a couple weeks, and who has been checking their code into GitHub periodically.
When I download their code and attempt to open in Android Studio 2.2, I get asked about various project settings. This surprised me, because it seems that all the project settings should already be specified somewhere in a file saved in the project settings. My coworker ought to be able to save all of their project configuration settings into the project file, upload it to the repository, and I should be able to download all of his files and simply build and run the project on my machine, assuming we're running the same version of Android Studio and both have the same SDK(s) installed.
My question is, what file(s) contain the project settings under Android Studio 2.2 and 2.1 (the version he started development with)? I've tried searching online and here on stack overflow for "what file contains project settings in android studio". However, this only gets me results that talk about what a project is, and what dialog boxes contain certain settings. I'd like to know which files (gradle, xml, etc) files contain the project settings (build, SDK, workspace, etc).
I've also tried uninstalling 2.2 and going back to 2.1.2, but that doesn't help much either. In both cases, I'm getting questions about project settings as well as build errors. I don't want to address all of those issues here though.
Thanks so much for you help!
From the location where you have installed Android Studio,
you will have something like .AndroidStudio2.2 folder this contains settings for version AndroidStudio2.2
What you do is Unistall studio and installng new one(AndroidStudio2.2), it will ask you to take settings from just give this path mentioned.
Other than this,
your gradle file will have all settings of your project.
it will be of module level and project level.
I want to set local documentation path in android studio 0.8, but i cant do this. I google this, but i can't find any solution for this problem. Can any body help me please.
Thanks a lot.
I found the solution in Android Studio 2.1 :
First, you have to see which Android SDK you are using from the Project Structure. Currently I am using Android 7.0 because the problem was caused by Android 7.1.1 SDK (I will explain why).
Now, open the Standalone SDK Manager. Find the SDK version that you use, then select Documentation for Android SDK then Install package and you will have a local copy of the docs automatically used by your AS.
As you can see, there is no documentation available to download for Android 7.1.1, that's why Android Studio was loading it from the Android developer website.
So, the solution is to use an Android SDK that has a downloadable documentation.
I had the same problem.Documentation was empty when I used documentation shortcut(ctrl + Q) and I also couldn't change the documentation paths because it wasn't there! so here is the solution:
Delete C:\Users[user name].AndroidStudioBeta folder.(Don't worry it just delete your configurations! ;) )
rename C:\Program Files (x86)\Android\android-studio\sdk (SDK path)folder to something else.
run Android studio and make sure you don't import you configurations.
Now you can change new sdk folder's name back to SDK .
Android studio will ask you new path for SDK ,so you can continue.
If you have downloaded the documentation using SDK manager, it'll get added automatically when you add an SDK in "Project Structure"
In Android Studio, You can verify this by selecting File -> Project Structure -> SDKs (on left pane).
Select one added SDK from the list, Select the tab "Documentation Paths" from right most pane. Check whether the path is automatically added. If not, add it manually by clicking the plus (+) button on right.
The only way I could accomplish this on AS 1.0 is to run local web server (Abyss Web Server) to host the documentation from here (C:\Program Files (x86)\Android\sdk\docs). And use Fiddler as proxy to remap url developer.android.com to 127.0.0.1:8080 (Abyss address), setting Fiddler's address as proxy in AS settings.
Oh, and created a .bat file to run and stop this all together.
Really dirty trick, but the only I found.
I followed googles instructions and exported a test project from Eclipse by using the
Export -> Generate Gradle build files
opened up Android Studio and imported. After getting my support libraries working properly my project would compile with out any errors. My problem started when I tried to run the app on my device. When ever I try to run the app it directs me to use an AVD, never giving me the option to select my device. I obliged, created a new AVD but to no avail only to get build failed error. (I'll add the exact error when I can) NOTE: I can see my device is connected by clicking on "(6)Android" and the bottom left of the screen. I do see all logcat messages in verbose. I added android:debuggable="true"to my manifest but still nothing.
Confused I created a new project directly from Android Studio, hit run and bingo,...it gave me the option to use my device to run it or an AVD. Selecting either results in a successful launch of the dummy "Hello World" app. I think it may have something to do with build variants as my imported project doesn't specify "debug" vs "release" while the Android Studio generated project does.
Anyone else experiencing this?
I found the answer to my own question. Bit of a double whammy. Before installing Android Studio I updated my SDK via Eclipse (as recommended/required by google). Turns out by doing so a few items in my current projects got disconnected. ie. build paths, dependencies, ect. (you now have to place external Jar's in the src/libs folder)
Here is what I did to fix it.
In Eclipse, Preferences -> Java Built Path ->"Order and Export" tab. Make sure items are selected
If you have external Jars, manually copy and paste the jar in the libs folder of the project. (I did this in my Finder)
confirm the project launches via Eclipse
If it runs, export the project again by "Generate Gradle build files" (confirm overwriting existing files, if any)
5.Open Android Studio and re-import the project. Again, confirming overwriting of any existing files.
6.Next to the run bottom at the top of the screen click on the drop down next to your project name. Click "Edit Configurations..." and select "show chooser dialog" if not already selected.
clicked ok to exit,..and PRESTO!!! I finally have a successful project migration.
Hope this saves someone else time.
Cheers!
Yeah i have experienced similar stuff on Eclipse, its quite buggy. Since Android studio is based on it i would expect everything. Still the best solution to everything is to reload project, refresh project or restart IDE.
The problem
I have a strange problem with SpringSource Tool Suite 2.9.1 Release and Subversive plugin, running on Windows 7 Home Premium x64. I'm trying to checkout an android project from an SVN repository.
Here's what I'm doing:
File > Import > SVN > Project From SVN
I fill in the path to my repository and check the HEAD revision
I click Finish
The project is found and the default option is Check out as a project with the name specified. I leave the name alone Set the Depth field to Recursively and again, select the HEAD revision.
I click Finish
A progress bar appears for a second just to show an error message:
Checkout operation for 'https://(.....)/Android' failed.
svn: Cannot create new file 'C:\workspace-sts-2.9.1.RELEASE\AppName \.svn\lock': System can not find the path specified
When I retry and follow the steps from 1 to 6, another dialog appears. It says:
This project already exists in the workspace
or there is a data folder in the checkout destination.
It allows me to select a folder to overwrite. When I do that, a similar but different error message is shown. It says:
Checkout operation for 'https://(...)/Android' failed.
0x0000000f: The folder 'C:\workspace-sts-2.9.1.RELEASE\AppName \.svn' is locked by some external process. Please unlock the folder and try to check out the project again.
What I've tried
First, I opened the SVN Lock view to see if there were any locks created by the IDE. There were none.
I restarted the computer, hoping it would solve the problem of any application locking the file but this does not seem to be the case.
After that, I created a new workspace in a different location and tried to check out the project in there. The result was the same.
Then, I attempted to change the version of SVN Kit. The situation persists in:
SVN Kit 1.2.3
SVN Kit 1.3.5
Native Java HL 1.5.4
Native Java HL 1.6.12
I thought that changing permissions to the directories of my workspace was worth giving a try. It didn't do the trick either.
Finally, I checked out the project in a different location, using Tortoise SVN and imported it into my workspace. I could run it (though some build path settings seemed to be missing) but it's not a solution. I can't possibly imagine working on the project simultaneously with a couple of people without the ability to commit/update/view history/resolve conflicts in my IDE.
I was advised to install a separate version of eclipse with its own set of tools and a different workspace for this application alone but it doesn't seem like a good idea. I'd like to keep it all in a single IDE. I'd also prefer to avoid reinstalling the whole thing as I don't feel like configuring all the other tools (mostly spring and android-related) from scratch.
Has anybody seen a situation like this? How can I get it working?
It's uncear to me whether this is a subversive problem or an SVN problem. I would try checking out from the command line (you must install SVN command line tools to do this, but I'd recommend having the tools around as a backup anyway).
Checkout from the command line and then import into STS using File -> Import -> Existing projects into workspace. Once in the workspace, you can select the project -> Team -> Share project to get svn support on it.
Rename the project and check out again , It must be a problem where u are trying to checkout the project which already exists with same name in the Package Explorer
I'm new to this, so please bear with me. I simply want to get the basic App Engine Connected Android Project to work in eclipse.
I first downloaded Eclipse 3.7 and the Android SDK. I installed the ADT plugin through eclipse. I configured eclipse to point to the sdk and created an android project. I added some widgets, messed around with SMS messages, and ran it on my phone. Worked like a charm.
Then I decided it was time to work with app engine. I downloaded the Google plugin for eclipse from within eclipse using this link http://dl.google.com/eclipse/plugin/3.7. I also downloaded the Google App Engine Java SDK from that link.
Ok, here's where it gets more fun. I created a new app engine connected android project and named it "TestProjectThree". I then clicked "Debug as->local app engine connected android project". On the console I got a url, but on my phone I got a black screen. I then noticed that there was nothing in the android/gen folder, so I did a clean build of both projects. Suddenly, it gave me 10 warnings.
"Cannot fully validate context since domain type com.testprojectthree.server.HelloWorldService is not available.
You must run the ValidationTool as part of your server build process."
I googled the problem and found this link http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation.
I began following the instructions. I tried to enable annotation processing, but it was already enabled. I tried to add the requestfactory-apt.jar to the factory path, but it was already there too.
Apparently now I need to run something called an Annotation Processor. I've never used Maven before but I right click on my android project->configure->convert to Maven project. I do a clean build and a POM file appears. I then copy all of the XML from that link to the line right above the /project line in the POM file. I copy the second bit too because I'm using indigo. Clean and build again. New error.
"/TestProjectThree-Android/gen already exists but is not a source folder. Convert to a source folder or rename it."
No idea what that one means either, but I see right click gen->build path->convert to source folder so I click that too. Clean and build again. NO ERRORS!! YAYAYAY!!!
Debug as local app engine connected android project. Got a black screen on the phone, and some sort of error in eclipse. “Source not found”. Looked for a more detailed error message but the console just has the app engine url on it and logcat looks empty.
I went back to the link about the validation tool and read all the comments. A lot of people seemed confused. I have no idea if I did it right, or did any of it right, and am very lost now. Please please please help me!!!
This sounds very similar to a problem I had, although not exactly.
I think the code generated by the AppEngine project that is used by the Android project is either not generated correctly, or needs a refresh.....and clean doesn't do it.
Try this:
First, make sure the requestfactory-apt.jar was in the "Factory Path" of "Annotation Processing" in the "Java Compiler" section of Project Properties.
In AppEngine project.
Properties-> Java Build Path, Source section. Select the ".apt_generated" entry and then "edit…" and rename it, by putting a "1" at the end of the name (or whatever).
Project -> Clean
then in Android Project
Properties-> Java Build Path, Source section.
Select the "apt_generated" source folder that is linked to the ".apt_generated" source folder in the AppEngine project.
"Edit…", then in the first line "Linked Folder Location" navigate to the NEWLY named folder in the AppEngine project (the one with the "1" at the end……)
Then Project -> Clean
Then build & run your Android project, it should now have newly generated RequestFactory code from AppEngine project and validate OK at runtime.
It's possible that closing and opening projects and cleans were also required.
Use parse. I tried using AppEnging for my app's backend, but parse seems to take care of a lot of backend jobs and makes life extremely easy https://parse.com