I am facing same issue

Same here

I think #102 fixes the issue which didn't make it into 10.0.0. My fix was to roll back to 9.5.0

Same issue

same issue, can we get an update to include the fix? @aaronj1335

This should be fixed by #104

Unfortunately I don't know when that fix will be released.

Unfortunately I don't know when that fix will be released.

As the current latest release is not usable, would it make sense very fast to release a patch release.
Especially as the documentation recommends using the one that is not working: https://developers.google.com/android/guides/opensource

Released in com.google.android.gms:oss-licenses-plugin:0.10.1

See https://developers.google.com/android/guides/releases#january_13_2020

Still having this issue with version 0.10.1.

I face the same problem, oss-licenses version 17.0.0 and plugin version 0.10.0 tried updating the plugin to 0.10.1 and still the same. Any help appreciated.

I face the same problem, oss-licenses version 17.0.0 and plugin version 0.10.0 tried updating the plugin to 0.10.1 and still the same. Any help appreciated.

See workaround: #119 (comment)

I face the same problem, oss-licenses version 17.0.0 and plugin version 0.10.0 tried updating the plugin to 0.10.1 and still the same. Any help appreciated.

See workaround: #119 (comment)

Hey @hnljp : The licenses related to app module dependencies are not picked up in the first place let alone the library modules. Tried the work around as suggested but still the same.

I've reverted to 0.9.4 (plugin) and 16.0.2 (oss-licenses), and it looks working but with small count of licenses.

This fix did not solve the issue for me. See: #119

This has been fixed with version 0.10.2 🎉

.