-
Notifications
You must be signed in to change notification settings - Fork 28
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
Support for AGP 8.0.0 and above #142
Comments
I've already forked the project and solved the issue on my fork, lmk which branch to target and I'll open a PR |
Hi @M4dhav Thanks for your interest and also the possible solution. |
Merged
Okay, submitted |
could this be related to
this error? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently encountered a problem where if I use any Gradle Distribution above 8.0.0, the build continuously fails with the message:
FAILURE: Build failed with an exception.
What went wrong:
A problem occurred configuring project ':bdk_flutter'.
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.
If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.
Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 23s
Error: Gradle task assembleDebug failed with exit code 1
Exited (1).
I believe the fix itself is simple enough, and a namespace needs to be added to the build.gradle file
The text was updated successfully, but these errors were encountered: