question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Android] Build emits a lot of Gradle warnings

See original GitHub issue

When building an app using react-native-google-sign-in with a recent Gradle version, the logs are full (a few dozen occurences) of those Gradle warnings:

- Gradle detected a problem with the following location: '/Users/renchap/dev/project/node_modules/@react-native-google-signin/google-signin/android/build/intermediates/aapt_friendly_merged_manifests/release/aapt'. Reason: Task ':react-native-google-signin_google-signin:verifyReleaseResources' uses this output of task ':react-native-google-signin-google-signin:processReleaseManifest' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '/Users/renchap/dev/project/node_modules/@react-native-google-signin/google-signin/android/build/intermediates/merged_res/release'. Reason: Task ':react-native-google-signin_google-signin:verifyReleaseResources' uses this output of task ':react-native-google-signin-google-signin:mergeReleaseResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Steps to Reproduce

Building any RN app with this package and a recent Gradle version (for example with RN 0.68) is enough.

Expected Behavior

No warnings are emitted

Actual Behavior

The above warnings are emitted 😃

Environment

Please provide

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:5
  • Comments:7

github_iconTop GitHub Comments

0reactions
shamilovtimcommented, Dec 13, 2022

Also getting these here. Changing the gradle command doesn’t do anything.

Read more comments on GitHub >

github_iconTop Results From Across the Web

gradle build fails on lint task - android - Stack Overflow
When I run the application from Android Studio, the build runs fine and executes correctly on my devices. But when I try (from...
Read more >
LintOptions | Android Developers
If you have a project with a large number of existing warnings, this lets you set a baseline and only see newly introduced...
Read more >
How we reduced our Gradle build times by over 80%
3. Enable configuration on demand · 4. Enable parallel execution · 5. Enable build caching · 7. If you're using the Firebase Performance...
Read more >
Upgrading your build from Gradle 7.x to the latest
Alternatively, you could run gradle help --warning-mode=all to see the deprecations in the console, though it may not report as much detailed information....
Read more >
Ability to selectively suppress warnings during D8 desugaring
Note that in the IDE build output a warning is emitted: AGPBI: {"kind":"warning" ... compileSdkVersion 28 com.android.tools.build:gradle:3.4.0-alpha02 ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found