AGP upgrading from 7.4.2 to 8.0.1 error "Namespace not specified. Please specify a namespace in the module's build.gradle file."

[D7766]

Hello,

I have Android Studio Flamingo 2022.2.1 Patch 1, Gradle version 7.5, AGP 7.4. If I open Androidx media 1.0.1 project and run configuration Demo - it works correctly.
The Studio offered changes in namespace in effect and extractor libraries for androidTest. I deleted the namespace parameter in lib-effect - AndroidManifest.xml (androidTest) and writed text "namespace androidx.media3.effect" in android { ... } section into builde.gradle (Module :lib-effect). I did the same for extractor library. It works correctly too.

Now AGP Upgrade Assistant offeres upgrade project's Android Gradle Plugin from 7.4.2 to 8.0.1. But during upgrading there is the error Sync Failed. The error message from sync is:

`Namespace not specified. Please specify a namespace in the module's build.gradle file like so:
android {
namespace 'com.example.namespace'
}

How do I upgrade succesfully? Is there any bug in AGP 8.0.1? I would like use new Androidx Exoplayer 1.0.1, not older version ExoPlayer v 2.

Thank you for you replay.

[icbaker]

Can you provide a bit more context about why you need to upgrade this project to AGP 8.0.1? If you want to use media3 1.0.1, you can probably just use the artifacts from maven rather than building the library yourself?

[OxygenCobalt]

Can you provide a bit more context about why you need to upgrade this project to AGP 8.0.1? If you want to use media3 1.0.1, you can probably just use the artifacts from maven rather than building the library yourself?

Personally, I have to vendor media3 to add some rejected changes like automatic FFMPEG decoder assembly, among other patches. Relying on the artifacts really isn't feasible for me.

[icbaker]

@OxygenCobalt Thanks for sharing - would your use-case be solved if you could build a local version of this project with its currently defined AGP version (7.2.2) and use something like PublishToMavenLocal to share those locally-built artifacts with your app development project?

(I'm cribbing from a similar comment from @bubenheimer in #346 (comment), who points out that PublishToMavenLocal doesn't currently work, but maybe we could fix that)

I'm aware our current instructions tell you to put everything in one Android Studio project, I'm just wondering if we should revisit those instructions.

[D7766]

@icbaker
"Can you provide a bit more context about why you need to upgrade this project to AGP 8.0.1? If you want to use media3 1.0.1, you can probably just use the artifacts from maven rather than building the library yourself?"

Thank you for your replay. My context:
I would like to create and implement my own UI interface of media3 ExoPlayer. I think when I use maven I can not make changes in Exoplayer library, that yes? I must make my own library. As I am a new one in android programming I want to start from some project with UI of Exoplayer which works correctly. Then I would like to delete redundancy parts from it and change UI parts by me. I selected Media3 project as I want to use the newest version of ExoPlayer. Standalone ExoPlayer2 library will be deprecated in favour of the Media3 implementation.
I want to my downloaded Media3 project upgrade to AGP 8.0.1 because my Android Studio recommends it.

[OxygenCobalt]

Thanks for sharing - would your use-case be solved if you could build a local version of this project with its currently defined AGP version (7.2.2) and use something like PublishToMavenLocal to share those locally-built artifacts with your app development project?

Can this be automated by gradle in some way @icbaker? One of the reasons I still vendor is that I can make all build steps be 100% executed by gradle with no extra scripting.

[icbaker]

@OxygenCobalt That's a good question. I did a bit of digging and it seems there isn't currently a good way with Gradle for one project to depend on another, with different Gradle/AGP versions, but with 'synchronized' re-building. Given that, I think we will stick with our current recommendation of putting everything into a single AS project (and unfortunately therefore requiring the same AGP version).

I'm also looking into upgrading us to AGP 8.0.1, but it requires quite a lot of changes.

@D7766 if you just want to experiment then I would not try and upgrade to AGP 8.0.1, just leave it on 7.4.2 and ignore Android Studio's recommendation for now.

I will keep this issue open to track my efforts to upgrade to AGP 8.0.1.

[bubenheimer]

@icbaker Would you still be able to look into why "publishToMavenLocal" does not work? The media3 project looks set up to publish to a repo via standard Gradle & AGP mechanisms, which generally means that it will publish to local as well; there is no extra setup required to make this work. It is puzzling that it is not working.

[icbaker]

@bubenheimer I just tried ./gradlew publishToMavenLocal on the main branch at fe66756 and it seemed to 'just work'. The task succeeded, and I see the artifacts in ~/.m2/repository/, e.g. ~/.m2/repository/androidx/media3/media3-exoplayer/1.1.0-alpha01/media3-exoplayer-1.1.0-alpha01.aar.

I then bumped the version number to 1.1.0-alpha02 locally (similar to 8c5e197), rebuilt, verified the alpha02 artifacts were created and then checked I could use that dep from a separate Android Studio project on the same computer where I had added the mavenLocal() repository in the gradle config - this must be coming from the local maven repo, since 1.1.0-alpha02 doesn't exist in https://maven.google.com/web/index.html?q=media3#androidx.media3 (which is the only place we publish media3 artifacts).

I did this in a Debian-based development environment.

If you're seeing a different behaviour when following the same steps then I suggest you file a separate issue, though I'm afraid we have limited capacity to investigate build problems that don't repro for us, so we may not be able to offer much assistance.

[icbaker]

I just pushed some commits (linked above) that update the main branch to AGP 8.0.1. If you're cherrypicking these somewhere elsewhere you'll probably need to take all of them, since there was quite a lot of pre-work before the actual Android Assistant was able to do its 'magic'.

I'm going to close this, since I think the question has been answered and we've also now updated.

[D7766]

"...@D7766 if you just want to experiment then I would not try and upgrade to AGP 8.0.1, just leave it on 7.4.2 and ignore Android Studio's recommendation for now.
I will keep this issue open to track my efforts to upgrade to AGP 8.0.1. ..."

@icbaker Thank you for your replay very much :-)

[bubenheimer]

@icbaker I tried what you did with publishToMavenLocal on the commit you referenced, but it did not put any artifacts in my local .m2 folders. I suspect there is something private in your build setup that I don't have. I remember that it also does not even seem to build the desired artifacts if I just do ./gradlew clean publishToMavenLocal. I'm on Intel Mac.