Please can you explain us why since UCB use Android SDK 26 we have read_phone_state permission automatically added?
Maybe related to Facebook SDK 7.9 ?
Thanks
Please can you explain us why since UCB use Android SDK 26 we have read_phone_state permission automatically added?
Maybe related to Facebook SDK 7.9 ?
Thanks
This is a known issue with the SDK that has been resolved for 2017.2 release.
Ok thanks
This can also be caused by a plugin not declaring the target SDK version in their manifest files.
@unity-tuesday Is this going to be resolved in a 5.6.x release or patch? I’m seeing this with 5.6.3p1 on Cloud Build (but not locally). I’m using 26.0.1 toolchain locally.
@pfleetwood22 This will eventually be fixed for 5.6.3, but I don’t have an ETA on this yet. It’s currently resolved in 2017.x.
Hello,seems that is not fixed in Unity 2017.2f3.
Just build with it and my phone require it.
@unity-tuesday I saw this was fixed for me on CloudBuild with 5.6.4p1.
However, now I am seeing local editor non-export-gradle-based builds with a res folder targeting API 25 failing to build with an AndroidManifest merge warning. Basically, whether I put an AndroidManifest file in Plugins/Android/res or not, the targetSdkVersion is overwritten with 26, and this causes me to get an error about a library targeting 26 when the main project is targeting 25. (I have made sure the Target API Level drop down in build settings is for 25).
How do I get Unity to write a proper API 25 targeting AndroidManifest.xml file for the Plugins/Android/res folder? Weirdly, when I export first, and then do a gradle build manually everything works. Cloud build also works.
I tried deleting my Library folder (as we took our project back from 26 to 25, which might be a bit unusual) in hopes that would help, but it didn’t.