What file(s) contain project settings for Android Studio 2.2? - android

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.

Related

How do I add/open a 3rd-party Android APK file to/with Visual Studio 2017?

So far after much investigation, I got as far as finding Tools->Archive Manager in Visual Studio 2017; however, I have no idea where to put archives to be viewed in this manager.
Other than Current Solution there is an All Archives menu on the left side, which looks like a Global repository, but I cannot seems to add anything to it.
Drag-n-drop does nothing either. I even tried creating a new Android project and dropping the .apk files into the bin folder and still nothing, so I'm at a loss.
Is it not possible to open 3rd-party APK files in Visual Studio (the ones I have are unsigned) in order to sign and test it in the emulator?

[Update]:Save settings of Android studio

I am new to Android Studio IDE i want to share my project in SVN.Everything was fine i ignored files and then committed by project.Then i try to check out the project and open in Android Studio IDE but the problem i lost the settings in android studio i knew i ignore some files that contains this settings.Can anyone help me on the file that need to commit so that i can restore the settings.The following settings are missing.
dont ignore .gradle!
project settings usually reside in .iml (IDEA markup language I believe), those are settings for the IDE.
More broad and user based settings live und .idea/, usually you dont want have them in your source repository.

Exported Eclipse Android project won't run from Android Studio

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.

Can't checkout an android project in STS 2.9.1 and Subversive on Windows 7

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

Not able to create new android project in android

eclipse is working fine with importing a project which already exist. But i am facing problem while am creating a new project in the android.
And then am trying to change the path in the properties of the project which i have created then it is showing some kind of error and screen shot of it is
Can any one help me in this.
Assuming your d: drive is an actual hard drive you have the android-sdk in, and not some DVD/CD drive you tried installing the android-sdk from.
You should click on your new android project folder, right-click and click on "close unrelated projects", then the right files will get generated correctly (re-initiate a manual rebuild if you have to).
The problem was that Eclipse was trying to rebuild all the projects you had in your workspace, a number of which already contained errors in them. Not only those other projects were clogging up your error log, but when an error is detected by the packager/builder, the building process gets stopped entirely.
Now just in case this wasn't your only problem, do Help > Check updates
After that, click on the menu Window > AVD Manager and something
and make sure that you have the latest SDKs and AVD updates already installed.
Also be aware that Pulsar is not the recommended version of Eclipse for doing Android development, although this probably wasn't what was causing your problem.

Categories

Resources