-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android Build Failure When Locking Dependencies Could not resolve app.notifee:core:+.
#1079
Comments
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Bump |
Hey @Jad-Jbara Did you try:
from the doc you linked https://docs.gradle.org/current/userguide/upgrading_version_8.html#xml_parsing_now_requires_recent_parsers ? Did you try ignoring this specific dependency as described in https://docs.gradle.org/current/userguide/dependency_locking.html#ignoring_dependencies ? It is curious to me that turning on locking would cause XML secure parsing to be enabled - they seem orthogonal Unsure what to do here but happy to take a PR Things I'm unclear on:
|
Thank you for your response, @mikehardy! Due to time constraints, we decided to temporarily remove dependency locking from our repo to keep things moving. I hadn't initially noticed the part of the documentation about ignoring the dependency, so I haven't had a chance to try that approach. Regarding your first suggestion:
I did attempt to force the new XML parsers, but unfortunately, encountered several other build errors. I began looking into them but, given the tight timeline, wasn’t able to fully troubleshoot and resolve the issues. Once I have some free time, I plan to revisit this, try and create a minimal reproducer, and hopefully address the questions you've raised. Thanks again for your insights! |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Facing the same issue, using expo |
This will most likely not be possible until I change up the structure of how part of this library's source is distributed from compiled/AAR to copy-on-build / publish-all-source |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
This one is important for reproducible builds etc and I have a technical means to do it, I know it's slow-going here on the maintenance side but I swear there is progress. I've just late last week gotten the Apple information I needed to set up push notifications and stuff, and now I'm working through Firebase Console issues in order to get the testing rig here fully ready to go for development. That's just a natural pre-requisite to actually doing all these changes, so please keep bearing with me |
Description
Build fails when locking gradle dependencies.
Note
this started happening after upgrading to
"react-native": "0.74.3",
where Gradle was upgraded to version 8.Error Message
Project Specifics
Steps to Reproduce
You can follow the guide on the official Gradle docs
Steps are below:
Add the following to your root
android/build.gradle
directory.--write-locks
to the command for example in our case we are running./android/gradlew -p ./android androidDependencies --write-locks
R&D
According to Gradle, depending on version 8 will lead to builds failing in case a dependency still uses legacy xml parsers.
How to Bypass the Error
The only way I could actually bypass the error was by disabling dependency locking in the project, which is not ideal since we would like to keep this in our repo.
Any idea how this can be resolved? Thanks!
The text was updated successfully, but these errors were encountered: