Closed NeoPCl closed 1 year ago
A patch for this:
diff --git a/node_modules/react-native-notifications/lib/android/app/build.gradle b/node_modules/react-native-notifications/lib/android/app/build.gradle
index d049e84..383984e 100644
--- a/node_modules/react-native-notifications/lib/android/app/build.gradle
+++ b/node_modules/react-native-notifications/lib/android/app/build.gradle
@@ -96,9 +96,9 @@ android {
testOptions {
unitTests.all { t ->
- reports {
- html.enabled true
- }
+ //reports {
+ // html.enabled true
+ //}
testLogging {
events "PASSED", "SKIPPED", "FAILED", "standardOut", "standardError"
}
This is also happening with react-native-navigation from wix
A patch for this:
diff --git a/node_modules/react-native-notifications/lib/android/app/build.gradle b/node_modules/react-native-notifications/lib/android/app/build.gradle index d049e84..383984e 100644 --- a/node_modules/react-native-notifications/lib/android/app/build.gradle +++ b/node_modules/react-native-notifications/lib/android/app/build.gradle @@ -96,9 +96,9 @@ android { testOptions { unitTests.all { t -> - reports { - html.enabled true - } + //reports { + // html.enabled true + //} testLogging { events "PASSED", "SKIPPED", "FAILED", "standardOut", "standardError" }
Hey @callaars It worked thanks! I also found in gradle docs (https://docs.gradle.org/7.3/javadoc/org/gradle/api/reporting/Report.html) that it suggests changing the enabled
to required().set()
. So I replaced it also worked just fine:
diff --git a/node_modules/react-native-notifications/lib/android/app/build.gradle b/node_modules/react-native-notifications/lib/android/app/build.gradle
index d049e84..6456e81 100644
--- a/node_modules/react-native-notifications/lib/android/app/build.gradle
+++ b/node_modules/react-native-notifications/lib/android/app/build.gradle
@@ -97,7 +97,7 @@ android {
testOptions {
unitTests.all { t ->
reports {
- html.enabled true
+ html.required.set true
}
testLogging {
events "PASSED", "SKIPPED", "FAILED", "standardOut", "standardError"
Is this planned to be fixed or does exists a workaround that doesn't need to soil the dependencies ?
Just faced the same issue, also interested in a long-term fix that doesn't involve applying a patch to a dependency
+1 same problem with android build.
+1 me too have this porblem
same here
After upgrading to React Native 0.72 and trying to start the App, I get this error now: