I'm recently started working on a school project using IntelliJ IDEA to develop an Android app. Most of the guys in my team (me included) are used to the way visual studio organizes project into .sln files. We've had all sorts of frustrations with IntelliJ mostly because we don't understand how IntelliJ organizes projects. We finally got the project to load reliably without having to make changes to each developers set up by following the steps here:
http://devnet.jetbrains.net/docs/DOC-1186. However, now anytime we get latest the Run/Debug configurations disappear. Anyone having the same problem?
Thanks,
Check this answer.
Make sure that you are sharing your configurations and files from the .idea/runConfigurations directory are added to the version control.
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
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.
Why don't we have a file similar to the .xcodeproj (for XCode applications) or an .xds (for Sencha Architect Projects) for our Android Studio Project?
I'm pretty sure a good number of you here have experienced the frustration of trying to import a project you see online in order to piece it apart better and learn how it works. I get that we are supposed to Import Android Projects built using Eclipse and Open Android Projects built using Android Studio.
However, why is it that we have to go through File -> Open -> then pick out the directory of the Android Studio app that we want to open? And the thing is, Android Studio doesn't seem to know it's an Android Studio project until it tries to open and build it. In the screenshot I have below, I have the sample Android Studio projects of ARToolKit, but I've only imported two of them.
As you can see, only those I've imported "can be seen as an Android Studio Project" as indicated that they have the Android Studio logo instead of a Folder.
This can be an issue for those just starting to develop in Android Studio on their own and they try and use existing projects (build from Eclipse or Android Studio) and they hit a snag with just trying to import the projects for reference. They might not know that they should import the folder and not the projectname/src subfolder. It adds to the "steep learning curve" that Android Development has if opening/importing projects aren't streamlined to a degree.
To sum up, my question is:
Why don't we have a single file that we can open that would in turn open Android Studio and import and build the project if it isn't built yet?
Android is not iOS. iOS development is only possible in xcode, hence it makes sense they added a shortcut to open it in xcode directly with a .xcodeproj file. Make life easier for iOS developers.
Android development however can be done outside of android studio as well. Eclipse is just one example, there may be other IDE's that support this. This is possible because android has standalone SDKs and tools that third party applications can use. iOS does not.
Imagine you are working on an android project in android studio. Then your boss tells you someone from 3000km away is going to help you. This guy may be using android studio, but maybe he isn't. When there are multiple options that developers can choose from individually, you do not want to pollute version control with files that you are using, but others may not care about. Each their environment.
This is merely a logical conclusion that you can come to by comparing. The "real" reason why this was done can only be answered by the people that created (adapted intellij) android studio.
This has been very frustrating to me too.
I try to give you a "beta" answer, waiting somebody to confirm it to me.
An Android project is just the composition of many parts that in some cases are concurrent to create the apk file.
It's just like what happens for the whole java projects: you have the main/src/java, the main/src/test, the maver or gradle files, the gradle or maven wrapper, the manifest, the configuration etc.
So you won't have a single project, but a series of folders that can contain many "flavours" or "versions" of the product itself.
The only help it is given to us is the Android studio icon that appears if a folder contains an android project in its subfolders.
I don't know if I have really answered to you, I just have given you my impressions and my thought.
Just a quick question I did not find a good answer on. We are currently working on an APP created with Eclipse ADT Bundle. I recently started exploring Android Studio, and like it. Is it possible to still collaborate with my mates using Eclipse with a shared GitHub repo?
I noticed Android Studio converts the project to its own file structure, so I guess this does not go well with Eclipse, and the repo.
Is there any solutions for this? So I can keep developing in Android Studio, push to GitHub, while the rest of the team use Eclipse?
I think you can do it, you'll just have to explicitly define a sourceSet that matches the Eclipse structure. If you use any other build variants, they can't have any sourceSets because you wouldn't be able to check those files in to source control. However, there are several useful things you can do with build variants just with the build file. I think you can check in the build.gradle and other gradle stuff and it won't mess up your coworkers.
I posted this question on the IntelliJ community forums but it seems as if they aren't very active so I'll just post it right here on S/O. I'm new to IntelliJ and I'm switching to use it from Eclipse which was really buggy and not useful to my needs. However, I'm attempting to build an Android project in IntelliJ Idea and it is only creating a .idea folder and the src directory without any inner files in them like it should. I've got the Android-SDK properly installed and I'm using JDK 1.7 and I'm even following the directions to properly start an Android project from the IntelliJ Wiki (found here) but it still leads me to no success. It seems as if I've got the Android Support plugin already installed with my program but then again I'm not really sure. Can I get some help please so I don't have to revert back to Eclipse again? Thanks.
Try to delete Android SDK and install it again, then download at least one Platform. IDEA runs SDK tools to create Android project template, for some reason it's failing on your system.
Check if it works better with JDK 1.6.
See the screencast that I've just recorded.