android-support-library

Gradle error after add android support design library

北城以北 提交于 2019-12-07 04:27:37
问题 I'm getting this error after add compile 'com.android.support:design:22.2.0' to my gradle file: .../app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/22.2.0/res/values/values.xml with this message Error:(1) Attribute "insetForeground" has already been defined . I have this on my build.gradle file: ` compile 'com.android.support:design:22.2.0' compile 'com.android.support:cardview-v7:22.2.0' compile 'com.android.support:recyclerview-v7:22.2.0' compile 'com.google.android

Show/Hide DrawerLayout depends on current fragment

岁酱吖の 提交于 2019-12-07 03:41:33
问题 I have an Activity class that have a DrawerLayout . That layout shows a list in Drawer and let user to switch between fragments . In these Fragments , there are some URLs and when user clicsk on that, a WebviewFragment would be shown. However, I don't want to show the DrawerLayout in the WebViewFragment . Instead, I would prefer user would being redirected to previous Fragment . Is there any way for me to show/hide the DrawerLayout depends on what the current Fragment is? I try to call

Why won't Android Support Libraries work in my project?

。_饼干妹妹 提交于 2019-12-07 03:33:58
问题 Using Android Studio, I followed the steps at https://developer.android.com/tools/support-library/setup.html as acurately as I could, but it told me the following error: Error:Could not find method compile() for arguments [com.android.support:appcompat-v7:18.0.+] on org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler_Decorated@18899229. Please install the Android Support Repository from the Android SDK Manager. Open Android SDK Manager But I have already installed the

Stop Android Studio from using Support Library

ⅰ亾dé卋堺 提交于 2019-12-07 02:33:57
问题 I'm trying to get my Android project in Android Studio to NOT use the Support library. My issue is that when I use fragments it is expecting support fragments and causing the app to crash. My Min SDK is 14 and my Target SDK is 19. My understanding is that because I'm targeting these versions I should not need the support library. Correct me if I'm wrong. I'm trying to correct this error java.lang.ClassCastException: com.google.android.gms.maps.MapFragment cannot be cast to android.support.v4

android-support-v4.jar dependency error

[亡魂溺海] 提交于 2019-12-07 02:15:00
问题 I just created a new blank Android project with minsdk as 2.2 in the latest Eclipse Luna.Eclipse automatically added an android-support--v4.jar in the libs folder of the project. This is causing an error in the console : Found 2 versions of android-support-v4.jar in the dependency list, but not all the versions are identical (check is based on SHA-1 only at this time). All versions of the libraries must be the same at this time. Versions found are: Path: /home/faizal/DEV/ADT workspace

Better to use FragmentActivity (or ActionBarActivity) or system Activity when targeting min API 14 (ICS)?

牧云@^-^@ 提交于 2019-12-07 02:05:50
问题 I'm making my app to have minimum Android version of 4.0 (ICS, API level 14). First I guessed that I can get rid of using FragmentActivity as the base class for the activities, but it seems that some support library classes like FragmentStatePagerAdapter is not available on the system framework, and it needs the support Fragment instead of the system Fragment . So I wonder if I should make my activities inherit from the system Activity , or stay using FragmentActivity (or ActionBarActivity

Upgrading Android SDK causes java.lang.VerifyError crash

那年仲夏 提交于 2019-12-06 21:27:21
问题 Since upgrading my Android SDK, I get a java.lang.VerifyError crash booting my previously working application. Looking at the logs, there are a few new issues leading up the crash that were not there previously: Could not find method android.support.v4.content.LocalBroadcastManager.getInstance, referenced from method com.myapp.android.App.setOAuthLoginState 04-12 19:43:10.249: W/dalvikvm(9508): VFY: unable to resolve static method 251: Landroid/support/v4/content/LocalBroadcastManager;

Android Studio 3.1 - Exception in plugin Android Support

懵懂的女人 提交于 2019-12-06 21:14:43
问题 I have updated to the latest version of Android Studio (3.1) and I get the following error when I try to run my app. It was working with no problems before the update. I have also uninstalled Android Studio and downloaded the latest version from the official website. Nothing has changed. null java.lang.NullPointerException at com.android.tools.idea.run.tasks.InstantRunNotificationTask.<init>(InstantRunNotificationTask.java:64) at com.android.tools.idea.fd.InstantRunBuildAnalyzer

Code Analysis Error (Unexpected namespace prefix) after upgrading Android Support Library 23.2.0

一笑奈何 提交于 2019-12-06 19:03:08
问题 I upgraded to Android Support Library 23.2.0 and added vectorDrawables.useSupportLibrary = true to my build.gradle, so that I have vector drawable support for apis lower than 21. (See here for details). I also replaced android:src="@drawable/ic_create_black_24dp" with app:srcCompat="@drawable/ic_create_black_24dp" in every Imageview that uses vector drawables. The app compiles and works perfectly fine, but code analysis reports: Error:(56, 9) Unexpected namespace prefix "app" found for tag

appcompat-v7:27.1.1 conflicts with play-services:11.0.1

◇◆丶佛笑我妖孽 提交于 2019-12-06 18:49:55
问题 I am working on a new app. Presently I am trying to add dependency. implementation 'com.google.android.gms:play-services:11.0.1' When I do I get a gradle compile error on implementation 'com.android.support:appcompat-v7:27.1.1' saying: All com.android.support libraries must use the exact same version specification (mixing versions can lead to runtime crashes). Found versions 27.1.1, 26.1.0. Examples include com.android.support:animated-vector-drawable:27.1.1 and com.android.support