I've recently updated the android studio IDE to 0.8 to work with the new android L SDK. To start I imported a finished android project that receives no errors in the older version of android studio. In version 0.8 i lines such as
import android.support.v4.app.Fragment;
get: Support cannot be resolved causing the rest of the code to have errors. The logcat returns 101 instances of
Error:(8, 30) error: package android.support.v4.app does not exist
1 for each time I call the support library in an import statement.
I've tried
not entirely sure what's left to do.
This question is related to
java
sdk
ide
android-studio
android-support-library
In my case the problem was solved by appending the string cordova.system.library.2=com.android.support:support-v4:+
to platforms/android/project.properties
file
My solution was creating a project with Use legacy support library
option checked
. after the project creation is successfully completed, just delete
the src
folder in the app directory and copy
the src
folder from your main project. Finally, Sync
project with Gradle files.
Ok, so I had the same problem and found a solution in a udacity forum:
In Android Studio:
@boernard 's answer solves this from the Android Studio IDE, but if you want to understand what's happening under the covers, it's a simple gradle build file update:
You can edit the build.gradle file from within the IDE (left pane: Gradle Scripts -> build.gradle (Module: app)
) or use the raw path (<proj_dir>/app/build.gradle
)
and add/update the following dependency section:
dependencies {
//
// IDE setting pulls in the specific version of v4 support you have installed:
//
//compile 'com.android.support:support-v4:21.0.3'
//
// generic directive pulls in any available version of v4 support:
//
compile 'com.android.support:support-v4:+'
}
Using the above generic compile directive, allows you to ship your code to anyone, provided they have some level of the Android Support Libraries v4
installed.
error: package android.support.v4.content does not exist import android.support.v4.content.FileProvider;
using jetify helped to solve .
from jcesarmobile' s post --- >https://github.com/ionic-team/capacitor/pull/2832
Error: "package android.support.* does not exist" This error occurs when some Cordova or Capacitor plugin has old android support dependencies instead of using the new AndroidX equivalent. You should report the issue in the plugin repository so the maintainers can update the plugin to use AndroidX dependencies.
As workaround you can also patch the plugin using jetifier
npm install jetifier
npx jetify
npx cap sync android
Delete
/.idea/libraries
Then sync gradle to build project.
In my case the error was on a module of my project.I have resolved this with adding
dependencies {
implementation 'com.android.support:support-v4:20.0.+'
}
this dependency in gradle of corresponding module
For me the problem was caused by a gradle.properties file in the list of Gradle scripts. It showed as gradle.properties (global) and refered to a file in C:\users\.gradle\gradle.properties. I right-clicked on it and selected delete from the menu to delete it. It deleted the file from the hard disk and my project now builds and runs. I guess that the global file was overwriting something that was used to locate the package android.support
None of the above solutions worked for me. What finally worked was:
Instead of
import android.support.v4.content.FileProvider;
Use this
import androidx.core.content.FileProvider;
This path is updated as of AndroidX (the repackaged Android Support Library).
IN ECLIPSE LUNA I ve resolved this issue by using contet menu on my Project : ANdroid Tools > Add support Library ...
tl;dr Remove all unused modules which have a dependency on the support library from your settings.gradle
.
Long version:
In our case we had declared the support library as a dependency for all of our modules (one app module and multiple library modules) in a common.gradle
file which is imported by every module. However there was one library module which wasn't declared as a dependency for any other module and therefore wasn't build. In every few syncs Android Studio would pick that exact module as the one where to look for the support library (that's why it appeared to happen randomly for us). As this module was never used it never got build which in turn caused the jar file not being in the intermediates folder of the module.
Removing this library module from settings.gradle
and syncing again fixed the problem for us.
Source: Stackoverflow.com