I'm want to try out the new androidx fragment testing library from
https://developer.android.com/training/basics/fragments/testing
In my app/build.gradle I add the dependencies as described in the docs
debugImplementation 'androidx.fragment:fragment-testing:1.1.0-alpha01'
After syncing the project with gradle files I'm getting this error:
Could not resolve androidx.fragment:fragment-testing:1.1.0.
Did I missed something there?
Solved, in my Android Studio I have the wrong HTTP Proxy Configuration. Now everything works fine.
Related
At first i did npm install --save #react-native-firebase/app then cd ios and then pod install and get error like that..
[!] The following Swift pods cannot yet be integrated as static libraries:
The Swift pod FirebaseCoreInternal depends upon GoogleUtilities, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.
then i use my pod file use_modular_headers! globally...then pod install done ,but when i ran the project from xcode it gives me the Error..."glog.glog.log_severity' appears within namespace 'google" please help i dont know xcode and can't solve the issue ...please help ...thanks advance
I just initialized a bare react native project yesterday and ran into this exact same problem when setting up Firebase. I can't remember the exact sequence of steps I took to fix it, but my current Podfile doesn't include use_modular_headers!. Instead, I used "use_frameworks!" globally in my Podfile, and commented out the use_flipper!() at the bottom as recommended in the comments. If you get the same initial error about static libraries, try switching the environment you're running from. I.E. if you've been trying from terminal by "npx react-native run..." use Xcode to compile the build, and vice versa. Hopefully that works, it did for me!
I am trying to run my emulator after adding the firebase and google sign in plug ins/dependencies to my gradle.build files and now I am receiving the error
"Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0"
anyone know if I am doing something wrong this is a react native firebase app.
I am not sure what to try. This is my first app I am doing for a project at school and I do not really know what I am doing. I have just been following tutorials online
Solve this issue by deleting the .gradle folder from <NameOfProject>/android and again run npm run android
I think I just had this same problem. I don't have any idea what your error logs are though so I am not certain however this is my error log right here:
`> Task :react-native-gradle-plugin:compileKotlin FAILED
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11) jvm targeta version. 1 actionable task: 1 executed`
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':react-native-gradle-plugin:compileKotlin'. Failed to query the value of task ':react-native-gradle-plugin:compileKotlin' property 'compilerRun Kotlin could not find the required JDK tools in the Java installation. Make sure Kotlin compilat
This error however I fixed by editing the gradle-wrapper.properties file's distributionUrl variable. I changed the distributionUrls gradle version to 7.4.2 the file is in Project-Name\android\gradle\wrapper\gradle-wrapper.properties
My error log is saying that gradle's version of JVM want's to be version 11 and is not but you can check gradle's jvm version by using cd android in the project root directory and after that run ./gradlew --version Change JVM's version from the version it is showing to the version that it says is required like in my case v 11. The way I changed gradle's JVM version required chocolatey which is a package manager. This is where you can require it https://chocolatey.org/install and after you have setup chocolatey open a new terminal that has administrative privileges and run this choco install -y nodejs-lts openjdk11 with the JVM version it is asking for inside your error logs
and finally run npm start and after that npm run android inside a refreshed and new terminal and gradle's JVM version and gradle's version will be updated to the specified versions
We could better help if you could you show us your android/build.gradle and android/app/build.gradle files, but here are more specific instructions than you find in the docs:
In android/build.gradle, dependencies should look something like this:
dependencies {
classpath 'com.android.tools.build:gradle:4.2.1'
classpath 'com.google.gms:google-services:4.3.10'
classpath("com.android.tools.build:gradle:<version>")
classpath("com.facebook.react:react-native-gradle-plugin")
classpath("de.undercouch:gradle-download-task:<version>")
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
see: https://github.com/gyani-sunkara/rn-firebase-login-starter/blob/main/android/build.gradle
It is known this works with the classpaths at the beginning.
--
Also in android/app/build.gradle, it is known that the google-services dep works at the end of the file.
apply plugin: 'com.google.gms.google-services'
and make this the last "implementation" under dependencies (around line 272)
implementation 'androidx.swiperefreshlayout:swiperefreshlayout:1.0.0' // <-- add this; newer versions should work too
see: https://github.com/gyani-sunkara/rn-firebase-login-starter/blob/main/android/app/build.gradle
Then, delete android/.gradle and run npx react-native run-android in the root directory.
Could not parse the Android Application Module's Gradle config. Resolve gradle build issues and/or resync.
I have tried many of the solutions but finally I have resolved this error
Check out my Screenshots and configure it in similar way.
If you are using new Android Studio or any recent version you will not find jcenter in recent version in your build-gradle file.
build-gradle[project]
build-gradle[app]
Dependencies in App level gradle
In settings.gradle comment out jcenter
Settings.gradle
Project Structure Settings
Project Structure Settings
Project Structure Settings 2
Hope this will solve your error.
I have updated all the firebase and google gms dependencies and still am getting this error, I don't know what's wrong?
Error-The library com.google.android.gms:play-services-base is being requested by various other libraries at [[11.0.1,11.0.1], [15.0.1,16.0.0), [15.0.1,15.0.1]], but resolves to 15.0.1. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.
You must use firebase-ui:3.3.1 for compatibility with the Firebase SDK and Support Lib versions you are using
I'm setting up the spring webmvc project using spring boot 2.0.0 version. If i run the application inside the embedded tomcat, it runs fine. I tried deploying it in external standalone tomcat-8 server, it is working fine over there too. But i if package the war and deploy it in the tomcat-8 server configured within eclipse, then it throws below exception.
The absolute uri: http://tiles.apache.org/tags-tiles cannot be
resolved in either web.xml
I included the dependency in the pom file as below.
<dependency>
<groupId>org.apache.tiles</groupId>
<artifactId>tiles-jsp</artifactId>
<version>3.0.4</version>
</dependency>
I ensured that the tiles-jsp jar is present inside the WEB-INF/lib folder. But still its failing as it is not able to scan the jar for TLD. I tried changing the catalina.properties to include tiles-jsp*.jar. But it is still failing.
Please help me to fix this error.
Does your IDE automatically import dependencies?
Try cleaning your maven dependencies.
Maven clean.
Or try the more brutal command dependency:purge-local-repository.
By the way notice that there's a newer version of your dependency 3.0.8 of 2017. The one that you are trying to use, the 3.0.4, is of 2014.
For me, war file when deployed works perfect. Had an issue where, when I run it under tomcat from inside IDE(Eclipse/STS), it threw error. Maven clean really helped, no other change needed. MAven clean-->build--> restart eclipse/sts tomcat. it works like a charm. Answer by desoss prompted me to perform maven clean. Thanks #desoss.