@darekdeo thanks for raising this. We'll look into it and report back here once we know more.

There's a draft PR that should address this issue: getsentry/craft#412

https://discuss.gradle.org/t/how-to-disable-using-gradle-module-metadata-then-to-use-pom-xml-to-resolve-dependencies/42995/2
a guy from gradle says

And for the future, it is almost always a bad idea to ignore the metadata or to not publish it.

FYI: For sentry-compose the gradle module metadata file generation has been disabled, see #2430 for more details.
If we want to support .module files, this needs to be re-checked again.

We still have to finalize the open craft PR getsentry/craft#412 to have this resolved. Maybe @buenaflor will take care of it when he's back again.

Need to check if that works automatically after getsentry/craft#412 is merged

@romtsn can you release a patch and see if it works? getsentry/craft#412 is merged

Currently .module files are only supported automatically through kmp configuration so for non-kmp targets it needs a bit of extra work. See: https://github.com/getsentry/craft/blob/3a136a5dbd40e9b2e7fe7ae7799cfbf71784108e/src/targets/maven.ts#L466

Noting that sentry-android 7.3.0 still does not have Gradle module metadata.

https://repo.maven.apache.org/maven2/io/sentry/sentry-android/7.3.0/