EAS Build - Execution failed for task ':app:checkDebugAarMetadata'. #59
Comments
|
@hridoy43 Thanks for reporting, can you make sure you are using onesignal-expo-plugin@1.0.0-beta10 or newer? This special case should be handled by onesignal-expo-plugin/support/androidConstants.ts Lines 6 to 11 in d8e9912 |
|
@jkasten2 Yeah, I'm using build.gradle after running |
|
@hridoy43 Thanks for checking, sorry I forgot to mention that there are more than one buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.10, 0.99.99]'
}
}
apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
apply plugin: "com.android.application"
import com.android.build.OutputFile
/**
* The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
* and bundleReleaseJsAndAssets). |
|
@jkasten2 there is no here are the dependencies which exist there. |
|
@hridoy43 I have a few more idea of some directions we can go to find out why this isn't being added to your DebuggingCan you run Check for any errors if you don't see this entry in the log, or share the whole log here. Environment & ProjectCould share your results of running Also if possible please share a project reproducing this issue. Other pluginsIn the |
|
@jkasten2 There's no Also, I have already mentioned about the custom plugin |
|
@hridoy43 Thanks for the log, it seems none of the I found these entries to confirm which config file is being used. I see it is Next I checked your "Evaluated config" section, it is missing a This seems to be the root cause of why To confirm you have it fixed you can run |
|
@jkasten2 Thanks for your kind reply. The issue has been resolved now. It was my fault that I had added the However, Idk how the other plugins were working like Anyway... I'm facing a new issue after solving this. After sending push/in-app notification from the one-signal panel, I'm getting two notifications at the same time (one with title and the other one with title and body Also, the first one only appears as a pop-up notification. I can see the second one If I only expand the notification panel. Idk It's an SDK related issue or not. So, that's why asking for the workaround/solution here!
|
|
@hridoy43 The title only notification is a common problem we have seen when another SDK / library attempts to display a notification from OneSignal. Check the other packages in your project that support notifications and remove or disable that part of them. (This is an Android only issue, due to the way Android handles push vs iOS) |
After removing "Expo-notifications" from the project dependency. everything works fine. Thank you for your support. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
After adding onesignal-expo-plugin in app.config.json when I run eas build command. The build failed with the following error:
It is related to this issue, OneSignal/react-native-onesignal#1318
I have tried to create a custom plugin with the solution found there. But It doesn't work
Build Error:
Custom Plugin Code:
app.config.json:
The text was updated successfully, but these errors were encountered: