|Portable class library in visual studio 2013 (wp7/win8)|
Keep in mind that VS 2013 is still a preview. So maybe it will be available
later but for the moment it looks like you can only create a PCL project
with support for both Windows Phone 7 and Windows Store apps by using
Visual Studio 2012
|how to make visual studio project portable? (where to set includes/libs/preprocessor definitions etc.)|
cmake might fit your needs: it's a cross platform build system that allows
to configure your project in a compiler-independent way. For Windows, it is
then able to generate Visual Studio Project files based on that
|Visual studio 2012 portable class library and System.ComponentModel.DataAnnotations.Schema refrence|
Simply because ForeignKeyAttribute is only supported in .net 4.5 and not
Portable Class Library. Check compatibility here (icons).
Because Silverlight is "going" to die, this will never be supported.
There were many addition in .net 4.5 and for
System.ComponentModel.DataAnnotations namespace, there are also unsupported
new attributes in PCL.
|different between class library and portable class library in visual studio|
The Portable Class Library project type enables you to write and build
managed assemblies that work on more than one Microsoft platform, whereas
the "normal" Class Library project type doesn't.
"Microsoft platforms" include .NET Framework, Windows Phone, .NET for
Windows Store Apps, Silverlight, Xbox; all in various versions or flavors.
Go through this for converting from one class library to another type. (See
also: this relevant SO question.)
|Add xamarin.ios and xamarin.android to portable class library|
Here is what you need to do. Follow the thread here, if you hit any issues.
Open an explorer window to C:Program Files (x86)Reference
Create a new file in the folder named 'MonoTouch.xml' and put in the
<?xml version="1.0" encoding="UTF-8"?>
<Framework MinimumVersion="4.0" MaximumVersion="*" Profile="*"
Create a new file in the folder named 'MonoAndroid.xml' and put in the
<?xml version="1.0" encoding="UTF-8"?>
<Framework MaximumVersion="*" MinimumVersion="1.6" Profile="*"
Identifier="MonoAndroid" DisplayName="Mono for Android"/>
Restart Visual Studio if it is still open
The options for MonoT
|Android: How can I open an older android project in Android Studio?|
Look at this links.
How do I open my existing Eclipse projects in Android Studio?
|Android Studio 0.2.2 + ActionBarSherlock setttings: Could not find class 'android.support.v4.app.FragmentActivity'|
As you requested my settings to be shared, I here post my project settings
Hope that you can help.
1. ActionBarSherlock project.
Note that only android-support-v4 is checked to be exported.
2. My personal project settings windows.
Nothing special but only ActionBarSherlock project is referenced.
|Android Studio & Gradle: Add outside java classes to Android main project|
you might want to make your Dir a own module
add include 'Dir' to your settings.gradle
create a build.gradle inside your Dir directory with this content apply
now you can go into your main projects build.gradle and add to
dependencies: compile project(':Dir')
if your Dir uses android related stuff, you might want to use the New >
Module(right click on your project in Android Studio) Function of Android
Studio to create an Android Library.
But i haven't tested that feature yet. If Android Studio throws an
Exception when trying to use the New Module, you should try to update
Android Studio, in the latest Version it works for me.
You might also want to check the Gradle User Guide and the DSL Reference
both are very helpfull in getting into Gradle and understanding i
|Maven repository and "Android support library", revision 18 for Android Studio 0.2.x|
Install fresh Android Studio 0.2.x. Upgrade from pre 0.2 doesn't work as
Reason is that new Android Studio is shipped with maven repo for serving
Alternatively edit build.gradle and replace
then copy support jar to libs folder.
|How do I add the library android-support-v7 in IntelliJ IDEA (Not Android Studio/Gradle)?|
You just need to add "@string/abc_action_mode_done" in your
appcompat/res/values/strings.Do not "set mediarouter as a dependency for
appcompat library".(In my case,"@string/abc_action_mode_done" already
exists in the appcompat/res/values/strings.I don't know why you miss it.)
"add depenency appcompat to mediarouter" is necessary.
|How to setup and test an Android Library Project with Gradle and Android-Studio?|
i think this tutorial will help you :
|Android Studio: Android Manifest doesn't exists or has incorrect root tag|
I ran into a similar problem. Looks like my .../src directory for whatever
reason moved under my .../lib directory. I moved it out of the /lib
directory. Now both /lib and /src are at the same level. After a couple of
clean rebuilds and restarts of Android studio everything is back to normal.
My emulator started up fine.
You might want to check your directory structure. Compare the directory
structure with a working project. You might be able to see the difference.
|Android Studio Error: "You must install the Android Support Repository though the SDK Manager"|
you must manualy run SDK Manager
android or android-sdk
new Support Repository must be already selected, and need only click
|Automatically versioning Android project from git describe with Android Studio/Gradle|
After some further reading and several false starts, I ended up with this,
added to the bottom of build.gradle in the project directory (that is,
MyAppProject/MyApp/build.gradle, not MyAppProject/build.gradle --
confusing, I know, but the former directory is projectDir in Gradle so
that's how I refer to it here). It depends on no external utilities other
than Git, which is assumed to be in the path, so it should work on any OS
(even though I used forward slashes in the paths, they get converted to
backslashes on Windows).
It could probably stand to be improved, I'm sure, as my understanding of
Gradle is pretty rudimentary and my Groovy may not be very idiomatic
(though that in particular is less of a concern). I have a feeling that my
approach is suboptimal because it involves generatin
|Wrong build being deployed on Android device using Visual Studio 2012 Xamarin.Android|
I have no idea why it does this, I had this issue before. I also noticed
that the device log was somewhat behind (ie, at 3.30pm, the last record on
the device log was 11.00am).
Uninstalling the app from the device and re-deploying it seems to correct
Note: I had this issue in VS, didn't check with XS.
I would look at the difference in your deployment settings in VS and XS (I
think it may have something to do with the Fast Deployment option).
|Android Studio - Build an Android project with Android library which depends on another Android Library|
The manifest files for the library must currently have a <application
/> node, even if it's empty.
It's a restriction we'll remove at some point but for now, just add it.
|How to navigate/view/edit android platform sources (AOSP) using Intellij IDE (Android Studio preferably)?|
Well, first you have to install Android studio from here:
Then, if you already have a project in Eclipse here is how you export it to
|How to open android documentation and samples of code in android studio|
First you need to make sure the documentation is added to Android Studio.
Go to File -> Project Structure. Under the Platform Settings heading, add
or select an Android Platform. Go to the Documentation Paths tab and make
sure the path to your SDK's documenation folder is added there - it should
eference, where [SDK] is the full path to your SDK
installation. If it is not there add it manually.
Once this is done, use Ctrl+F1 while your cursor is on the item you want to
display help for.
The samples have not been ported to Android Studio yet, but I'm sure google
will get around to it at some point. For now follow the instructions in the
comments by androidika (you will need a copy of Eclipse installed).
|Android: Emulator in Android Studio doesn't start/launch|
Well, Android Studio is waiting for you to start the virtual device.
You can do that from AVD Manager --> 'Select the device you chose in
Android Studio' --> Start.
I hope this answers your question
|Is it possible to test In App Billing in an Android App connected to and running from Android Studio|
Except for the static purchase test items, you are generally no longer able
to test in-app billing features while in debug mode. You have to use a
release version of the app and complete the app setup on Play Developer
Console to do so.
So to answer your main question, while you can track the overall flow of
your purchase feature in debug mode on your app, you won't be able to test
a successful transaction while using the debugger.
|Android Logcat is empty when debug with device in android studio|
As of 0.4.0 I have noticed that the logcat tab does not work in the
debugger window - only in the Android DDMS window (hit Alt+6 to bring up
the working logcat while debugging). Awkward I know :)
|How do I migrate my Android Eclipse project to using Gradle and Android Studio?|
You should create a folder in you project's root and name it libs.
Then copy your jar file to that folder and add
compile fileTree(dir: 'libs', include: '*.jar')
to your build.gradle file.
If above won't work. You may need to try this post
|Android Studio - Export Android library aar with pure gradle|
You should try updating/upgrading your build tools and gradle through
AndroidStudio. Once you do this, or if you have already done it, you should
be able to modify your build file to reflect the updates:
NOTE: I am still unable to generate aar files even with this setup,
although compiling is fine. At least this might get you past this hurdle.
|How to create the best Android app project structure with Android Studio and Gradle?|
You should look at the multiproject example for the layout attached in the
Essentially you want a top level settings.gradle that tie all the pieces
together. Ideally they should be in one single git repo to make your life
easier. However you probably can use symlink to tie them into a common
build repo that contain your top level settings.gradle.
|Android Studio "Cannot resolve symbol XXX" on basic Android tutorial|
so, it turns out that Studio is (understandibly) buggy, and that these
errors are false negatives...
I can also add the hierarchical parent by hand in the code so the question
about the popup is moot too :/
|No Android facet found, issues compiling with Android Studio 0.2|
Add an android facet to your module by following below steps.
1) Go To File Menu -> Project Structure, or press (Ctrl+Alt+Shift+S)
shortcut to open "Project Structure".
2) Select "Facets" which is under the "Project Settings" tab. (First
3) Click on "+" button which is at the top of the Second Column to add new
4) Select "Android" facet from that "Add "menu which will prompt another
dialog box to select a module. (Select a module to which you want to apply
5) Select your module and that's it. :)
Hope this will solve your problem.
|Questions about calabash-android support in Android Studio: Ruby, Editing features and steps, Launching tests|
Very good question. Xamarin had a webinar on using Calabash tests in their
Test Cloud product. Towards the end of the talk there is quite a bit of
hands-on with setting up the testing ecosystem and running Calabash tests
for Android. There's lots in there that don't apply to your environment,
but some very good tips and insights from Karl Krukow - one of the main
contributors to calabash-android.
|Import an Android Project from Eclipse to Android Studio and I have this error message "failed to find Build Tools revision 8.0.0"|
Your build.gradle is trying to use Android SDK tools 8 which isn't
installed on your machine.
If you look at your build.gradle file you probably have this line
buildToolsVersion "8". You want your build.gradle file to point to the
Android SDK tools that you currently have installed (preferably the
latest). Just open the Android SDK manager and see which tools you have
installed and change the buildToolsVersion "8" to the right version.
|Android studio - Failed to find target android-18|
I solved the problem by changing the compileSdkVersion in the Gradle.build
file from 18 to 17.
apply plugin: 'android'
|Android testing in Android Studio using Robolectric issue|
I have temporary solution. The problem seems to be that the
android-test-plugin in unable to read an aar file. My solution is to add a
dependency to the jar file instead only to testCompile, like this
Like this I'm able to run a simple test, for example creating a LatLng and
checking if it's not null, without errors. Hope it helps.
A better solution thanks to SuperJugy on github is to apply the fix in this
|Creating a Phonegap based Android ap in Android Studio|
Ric is really easy to work with Phonegap and ANDROID Studio.
Here is what i am doing:
Creating Phonegap project: phonegap create testproject com.testproject.name
Enter Project directory: cd testproject;
Add Android platform: phonegap build android;
You have your phonegap project ready. Now open Android Studio. Select
Import project and follow instructions. If you don't have any plugins added
in your project it's preaty pushing NEXT till you get to the end.
That's all. If you need more information tell me will be happy to help you.
If you prefer snapshot you can find a very easy to follow tutorial here:
Phonegap and Android studio
|Android AddThis sdk + Facebook sdk won't build in Android Studio|
I was able to resolve this issue:
Since the Facebook SDK is a module and not a jar, I referenced
AddThis0.8.8.jar from the Facebook SDK module, and removed the reference to
it from my project directly.
After doing so, there was still a conflict between com.facebook.android.*
in the Facebook SDK and the duplicate ( com.facebook.android.* ) in the
AddThis jar. So, I deleted the com.facebook.android package along with it's
contents - from the Facebook SDK - then included com.addthis in ( class
path, I think? Android Studio suggested to include it when I typed
"ATButton" in code. I said "Heck yea, thanks JetBrains!" ).
I am now able to use AddThis as well as the Facebook SDK without any
I hope this process can help someone out there in some way.
There were still problem
|How to compile Android native library with Android Studio?|
NDK integration is very basic, limited, and not documented (per the New
Build System page) at the time of this writing. There a couple of examples
in the samples at the bottom of that page that illustrate how this can be
done. You can also check the Gradle Plugin User Guide periodically to see
if any additional documentation is available.
|Android copy existing project with new name in Android Studio|
The steps in the link you specified should also work for Android Studio.
Just make a copy (using a file manager) of the entire module folder and
give it a new name. Now open it up and use Refactor -> Rename (right
click on the item you want to rename) to rename your module and package.
See this for details about refactoring in IntelliJ/Android Studio.
|Android device is not connected to USB for debugging (Android studio)|
If you are on windows, many times it will not recognize the device fully
and because of driver issues, the device won't show up.
go to settings
hardware and sound
And look for any devices showing an error.
Many androids will show as an unknown USB device.
Select that device and try to update the drivers for it.
|Android Studio: Plugin with id 'android-library' not found|
Instruct Gradle to download Android plugin from Maven Central repository.
You do it by pasting the following code at the beginning of the Gradle
Replace version string 1.0.+ with the latest version. Released versions of
Gradle plugin can be found in official Maven Repository or on MVNRepository
|How to include "Android" folder to Android Studio (ZXing)|
I fallowed this tutorial:
which worked fine for me
|Android Studio: how to import Android library project|
Go back to Project Structure window where you added the new module. Click
on your main module, go to Dependencies tab, click the plus icon and select
|Analyse performance of android app using Android Development Studio|
From Android Studio Tips and Tricks, on developer.android.com:
When you build and run your app with Android Studio, you can view adb
and device log messages (logcat) in the DDMS pane by clicking Android
at the bottom of the window.
If you want to debug your app with the Android Debug Monitor, you can
launch it by clicking Monitor in the toolbar. The Debug Monitor is
where you can find the complete set of DDMS tools for profiling your
app, controlling device behaviors, and more. It also includes the
Hierarchy Viewer tools to help optimize your layouts.
So, have you tried clicking on the monitor button? It looks like a little
green android. From there you can use all the regular tools.
As for the downvote, I can only assume it was for one of two reasons
|Missing the android.os.handler object from Android Studio|
Make sure that your Android SDK is added properly to Android studio. To do
this go to File -> Project Structure and check the SDKs item under
Platform Settings. Also make sure that you have selected a Project SDK
under the Project item.
See the IntellJ documentation for more information.