When I opened the project I only had a few errors, I know I saw one around google play services. I expected that, so I linked GPS by adding the dependency and now I have 133 errors. I tried cleaning the project and updating the SDK's. I have Android 4.0 selected. ( I also tried 4.0.3) Build tools version 22.0.1 The errors are located in Values.xml and most are versions of "no resource found that matches the given name:" Then it lists attributes , TextAppearance, things like that that all appear to be basic properties that I would think would be included in the SDK. Maybe I need to do something small that I missed? This is the first project in Studio I have tried to run on this machine. Any ideas?

It might be a plugin overwriting that.what values does it say?

I only have the BT plugins included. I tried adding additional library dependencies and got the errors down to 120. It all references appcompat-v7/22.2.0/res/values-v17/values-v17.xml I also tried deleting this one and starting a new project- same thing happened.

cool yea you shouldnt have to add any dependencies.and you only really need to add google play services if you're using the eclipse package instead of the new buzztouch studio version. you would have to add it to the new version only if using admob i believe. David Book has already added the needed imports for his plugins to run. did you follow go north west youtube tutorials? https://www.youtube.com/user/gonorthwest

I have seen these errors time after time! Different things seem to help in different projects. Try deleting and redownloading with the bare minimal plugins or if you see a particular plugins having the most errors, delete from project. If still getting the errors, I would be happy to look at your project. LA

I have the same problem with exactly the same number of errors. I only had 2 errors but one of them was not having Google Play Services. I added it and then it refreshed. If you solve the problem then let me know. I will have another go this weekend.

Hi, I've the same error to install the version 7.5 of google play service, but to install the 6.5.87 I do not have error com.google.android.gms:play-services:6.5.87

I finally had some more time to look at this. The issue was Studio was looking at an old version of the JDK (1.6) I had downloaded 1.7 but I had to set the folder location for the new JDK in project structure. Found this on SO- http://stackoverflow.com/questions/24472020/android-studio-needs-jdk-7-for-android-l-mac here is the detail solution step-by-step For Mac Download the DMG file of JDK-7 from here Click on DMG and follow the instructions . It will install and configure JDK-7 on mac . Now in your android studio go to File->Project Structure -> SDK Location . In JDK location click on browse and go to /->Library->Java->JavaVirtualMachines->jdk1.7.0_60.jdk->Contents->Home Hope this helps someone else. Jim

Awesome! LA

I'm getting the same thing. I updated my Java to the latest (1.7.80) but it still giving me those errors. The odd thing is, If I bump up the SDK to Android v5, it will work fine. But I don't want it at v5, I want it at v4, lol! Any ideas, hints, or comments? Cheers! -- Smug

What are the errors?

Pretty much the same story as everyone, lol! Import my BT Project into AS. Initial Gradle Sync comes up with 2 errors. Hit the project properties; ensure Java is referenced correctly (new java, new location) Add Google Play Services (v7.5.0) as a library dependancy Gradle Sync returns with 133 errors, mostly "No resource found that matches the given name: attr 'android:actionModeShareDrawable'. Full Error log text here: https://dl.dropboxusercontent.com/u/115208762/ASErrors.txt I'd really appreciate any assistance that could be rendered. Cheers! -- Smug

Anyone solved this? I just updated Android Studio to 1.4.1 (Google play service 8.1.0) and now have 133 errors, same as others. I installed Java 7 and checked File->Project Structure -> SDK Location. Got error: copy/app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/22.2.0/res/values-v17/values-v17.xml and copy/app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/22.2.0/res/values-v21/values-v21.xml I deleted this .xml files but are created again. Then I changed Google play service 8.1.0 to 6.5.87 in build.gradle. Now it works, but I am not sure if this is OK.

I am getting the exact same batch of errors. I am using Android Studio 1.5.1. I tried both jdk1.7.0_80.jdk and jdk1.8.0_73.jdk. I am attempting to build for API 14: Android 4.0 (IceCreamSandwich). I attempted this with Build Tools Version 23.0.2 (what showed by default). I also attempted this with Build Tools Version 22.0.1 (what I saw in posts here on the forum). The moment I add Google Play Services (8.4.0) I suddenly get a long list of errors just like the ones described above. I think perhaps 115 errors in my case. All the errors are in these paths: /app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/23.0.0/res/values-v17/values-v17.xml and /app/build/intermediates/res/merged/debug/values-v21/values-v21.xml and /app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/23.0.0/res/values-v21/values-v21.xml and /app/build/intermediates/res/merged/debug/values-v23/values-v23.xml I am willing to try Miku's trick of changing the Google play service from 8.4.0 to 6.5.87 in build.gradle, but I have no knowledge yet of how to do that. Working on it.

I've done a couple of things, primarily an edit of my 'build.gradle' file at the 'module' level. 1) Add legacy apache right underneath the 'buildToolsVersion' line: useLibrary 'org.apache.http.legacy' 2) Ensure the 'compileSdkVersion' is recent (23) 3) Add the 'gcm.jar' file to libs, and alter the build.gradle in dependancies, right underneath google play services: compile files('libs/gcm.jar') and I think that should fix you up. There 'may' be other edits needed, depending on the services required, but this should get you started. Cheers! -- Smug my 'build.gradle' file from a successful, no error build: apply plugin: 'com.android.application' android { compileSdkVersion 23 buildToolsVersion "23.0.2" useLibrary 'org.apache.http.legacy' defaultConfig { applicationId "com.smugplug" multiDexEnabled true minSdkVersion 14 targetSdkVersion 14 } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt' } } } dependencies { compile files('libs/gcm.jar') compile 'com.google.android.gms:play-services:+' }

Smug: Wow, thank you. I am going to try this, right away.

My gradle file is almost the same: apply plugin: 'com.android.application' android { compileSdkVersion 14 buildToolsVersion "23.0.2" defaultConfig { applicationId "com.duskoapp" minSdkVersion 14 targetSdkVersion 14 } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt' } } } dependencies { compile files('libs/gcm.jar') compile 'com.google.android.gms:play-services-ads:8.4.0' } I use compileSdkVersion 14 instead of his 23, but that shouldn't matter for the most part. If you want to see less errors, here is what you can put into the gradle file: android { lintOptions { // set to true to turn off analysis progress reporting by lint quiet true // if true, stop the gradle build if errors are found abortOnError false // if true, only report errors ignoreWarnings true } ... }

I have been able to finally successfully build, using Smugwimp's advice to use the lastest SDK and build tools available, even though my target device is still the older device. However, the BT Push code for Android uses an old, deprecated style of code that is not compatible with the SDK / build tools, and the code modifications I found here ( http://www.buzztouch.com/forum/thread.php?tid=56643342D49BA08BDEEB1EF ) don't work. They seem to use a mis-mash of old style code and new style code, and it crashes the app every time I send a push notification.

The headline of this thread is 133 errors after adding Google Play Services in Studio You are now asking a question about push notification, as you did in the other thread. If I were you, I'd start a new thread in order to attract more visibility. Also, search for funkeymonkey's posts in the forums, seems he has the push nailed down to the last bit.

Sorry. Thanks! Will do.