Skip to content
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

Error in Namespace #139

Open
securexperts opened this issue Aug 6, 2024 · 3 comments
Open

Error in Namespace #139

securexperts opened this issue Aug 6, 2024 · 3 comments

Comments

@securexperts
Copy link

Hello,

Is there a way to use the plugin with API 34/35 ?

I got the Error:

AILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring project ':flutter_beacon'.

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: /Users/devaccount/.pub-cache/hosted/pub.dev/flutter_beacon-0.5.1/android/build.gradle. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

Would it be possible to Help me

Many Thanks

Roman

@a1819644
Copy link

Same error encountered.
What I have tried so far:

  • changing and confirming the name of the project.
  • problem starts coming soon after installing the package.
  • no solution is available on elsewhere
> 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.

@a1819644
Copy link

@securexperts, This problem has been resolved on my side.

You need to locate the Flutter_beacon folder inside the dependency folder as shown below.
image

Once you are there, simply add the selected line shown below and then rebuild the project.

image

Hopefully it resolves your issues.

@sayedmoataz
Copy link

check this useful one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants