Yes, thank you, I’ve actually reviewed this file again, and found some more details.
As I’ve already mentioned, some permissions come from admob, but now I see the reason:
uses-permission#android.permission.WRITE_EXTERNAL_STORAGE
IMPLIED from …\bin\android\bin\app\src\main\AndroidManifest.xml:2:1-29:12 reason: com.admobex has a targetSdkVersion < 4
uses-permission#android.permission.READ_PHONE_STATE
IMPLIED from …\bin\android\bin\app\src\main\AndroidManifest.xml:2:1-29:12 reason: com.admobex has a targetSdkVersion < 4
uses-permission#android.permission.READ_EXTERNAL_STORAGE
IMPLIED from …\bin\android\bin\app\src\main\AndroidManifest.xml:2:1-29:12 reason: com.admobex requested WRITE_EXTERNAL_STORAGE
uses-permission#android.permission.ACCESS_NETWORK_STATE
ADDED from [com.google.android.gms:play-services-ads-lite:19.5.0] …gradle\caches\transforms-2\files-2.1\31c131232a6e4629187bfdd4c8fff82f\play-services-ads-lite-19.5.0\AndroidManifest.xml:24:5-79
Still, I don’t know where exactly this permission comes from:
uses-permission#android.permission.RECEIVE_BOOT_COMPLETED
ADDED from [androidx.work:work-runtime:2.1.0] …gradle\caches\transforms-2\files-2.1\8b34ffa1d2135fbc82c7193fb1dd165d\work-runtime-2.1.0\AndroidManifest.xml:27:5-81
Well it is the opposite for me, I had to put <uses-sdk android:minSdkVersion="4" /> to extension-admob (I put 9 not 4) to get rid of some permissions.
And I don’t have any gradle build errors.
Once I had an issue with android build caused by <uses-sdk android:minSdkVersion="4" /> got to generated project.
When I tried to figure out where it came from I had found that it is extension-api located in lime repo.
Maybe increasing version in given file would affect permissions somehow.
On the other hand, dependencies like com.google.android.gms may affect permission itself, so did you check how behaves raw android studio project with such dependencies like those in gradle files of project generated by lime?