-
Notifications
You must be signed in to change notification settings - Fork 31
[SOLVED] Release Build Failure, "Task :notifee_react-native:bundleReleaseAar FAILED" #151
Comments
I am using the latest notifee release, gradle 4.0.1, as well as multiple other modules that use kotlin (react-native-apple-authentication, react-native-webview) without issue, so this is unexpected If you could post a reproduction on github based off a clean project from You may want to define |
Thank you for your response. I tried again using Gradle 4.0.1 and updating Kotlin to 1.4.10. I received the same error. I created a clean and barebones instance of the project that can be reviewed at https://github.com/joebarrero/notifee-test and this version also produced the same error. I added all of the relevant information regarding my build in the Readme.md file. I appreciate your help. |
How unfortunate! I'll give it a shot and see what I can see. Sorry you've run in to this trouble |
🤔 Does not reproduce:
How are you launching it? Via Android Studio or the command line? |
It runs just fine. It's when I try to create the APK that it fails.
|
My apologies - you noted that in the first line (or so) of your report. I was moving too quickly while attempting to diagnose. I have reproduced the problem! Which is bad (there's a problem...) but also great because now I see it. |
I knew this reminded me of something! Use Can you confirm this works @joebarrero ? (it worked for me when I did that command in your repro repo) |
That worked! Thank you. |
I am still baffled why Glad you're moving forward! |
Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle"
depending on it as a direct file is anti-gradle, this is the right way to do it Fixes Fixes invertase/react-native-notifee#151 Fixes notifee/documentation#8 BREAKING CHANGE: this requires users to add a new maven repository definition to their build.gradle
Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle"
depending on it as a direct file is anti-gradle, this is the right way to do it Fixes Fixes invertase/react-native-notifee#151 Fixes notifee/documentation#8 BREAKING CHANGE: this requires users to add a new maven repository definition to their build.gradle
Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle"
depending on it as a direct file is anti-gradle, this is the right way to do it Fixes Fixes invertase/react-native-notifee#151 Fixes notifee/documentation#8 BREAKING CHANGE: this requires users to add a new maven repository definition to their build.gradle
Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle"
Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle"
) * fix(deps, android)!: switch to local maven repo for aar dependency Fixes #151 Fixes notifee/documentation#8 BREAKING CHANGE: add "maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }" to "repositories" in "android/build.gradle" * docs(example): add new local maven repo for notifee to example config Co-authored-by: Helena Ford <helenaellieford@gmail.com>
…107) * docs(README): explain how to test local react-native changes in e2e * build(deps): update gradle to 7.2 + wrapper re-generation * build(deps): update native android dependencies * fix(deps, android)!: generate aar into react-native local maven repo depending on it as a direct file is anti-gradle, this is the right way to do it Fixes Fixes invertase/react-native-notifee#151 Fixes notifee/documentation#8 BREAKING CHANGE: this requires users to add a new maven repository definition to their build.gradle Co-authored-by: Helena Ford <helenaellieford@gmail.com>
Fixed in release v2.0.0 (https://notifee.app/react-native/docs/release-notes#200) |
Should be noted this became mandatory with the move to android targetSdkVersion 30, not sure why? But this should keep everyone moving along as they move those targets up |
[EDIT TO ADD SOLUTION: Use
./gradlew :app:assembleRelease
not./gradlew assembleRelease
]I'm using React Native version 0.63.2 with Notifee 0.12.3
When using classpath('com.android.tools.build:gradle:4.0.1') in the build.gradle file, ./gradlew assembleRelease fails with the following error and message:
Changng the to build.grade file to, classpath('com.android.tools.build:gradle:3.6.4'), seemed to fix the issue.
I'm not sure if this is a bug, my lack of experience, or a combination of both but I thought it might be important enough to post my experience here.
The error seems to imply that creating a release bundle with the earlier version Grade Tools can lead to a broken bundle. Is there something that I should do to assemble the release build the latest version of the Gradle Tools?
The text was updated successfully, but these errors were encountered: