Search Unity

READ_PHONE_STATE permission added when using SDK tools 26.0.2

Discussion in 'Android' started by pep_dj, Jul 4, 2017.

  1. pep_dj

    pep_dj

    Joined:
    Nov 7, 2014
    Posts:
    179
    I've updated Android SDK tools to 26.0.2, and now game builds ask for READ_PHONE_STATE permission (and READ_EXTERNAL_STORAGE also). Switching back to 25.2.3 solves the problem. But, I would like to use latest SDK tools.

    This issue is also listed in Unity Issue Tracker: https://issuetracker.unity3d.com/is...fest-dot-xml-file-using-latest-26-dot-0-2-sdk

    Do you know how can we fix it?

    EDIT: The issue has been solved after I added
    <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="25" /> to everyplay manifest.xml file
     
    Last edited: Jul 5, 2017
    pep_dj, Jul 4, 2017
    #1
    Yury-Habets, tomerpeledNG and vrfurl like this.

  2. vrfurl

    vrfurl

    Joined:
    Feb 10, 2017
    Posts:
    1
    this worked for me. Thanks for sharing
     
    vrfurl, Jul 22, 2017
    #2

  3. tomerpeledNG

    tomerpeledNG

    Joined:
    Jul 14, 2017
    Posts:
    81
    Worked for me as well.
    Thanks
     
    tomerpeledNG, Aug 22, 2017
    #3

  4. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    Plugins with manifests where targetSdkVersion is missing will cause this undesired behavior. The correct fix is to add this entry to the manifest - @pep_dj is correct.
     
    Yury-Habets, Aug 25, 2017
    #4
    rsodre likes this.

  5. Don_K

    Don_K

    Joined:
    May 31, 2016
    Posts:
    8
    I fix my project,
    For all AndroidManifest.xml in the Asset folder
    <uses-sdk android: minSdkVersion = "16" android: targetSdkVersion = "25" />
    I added it and built it with UnityCloudBuild.

    But, the READ_PHONE_STATE permission remained.

    Can you give me some advice?
     
    Don_K, Aug 30, 2017
    #5

  6. Voxel-Busters

    Voxel-Busters

    Joined:
    Feb 25, 2015
    Posts:
    1,965
    @Yury-Habets : What if multiple manifest files specify different SDK Targets?
    Isn't it dependent on main root manifest file? Please suggest.

    Thanks,
    Ayyappa
     
    Voxel-Busters, Aug 30, 2017
    #6

  7. pfleetwood22

    pfleetwood22

    Joined:
    Jun 6, 2016
    Posts:
    28
    @Yury-Habets I have been unable to resolve the unwanted addition of READ_PHONE_STATE in Cloud Builds. I cannot reproduce the introduction of that permission locally. I have ensured that I have buildToolsVersion of 26.0.1 in my locally exported build.gradle file. So, my first concern is that Cloud Build is doing something differently than I am locally. I'm using 5.3.6p1 both locally and on Cloud Build.

    I've also made sure that every AndroidManifest has specified a minSdkVersion in the uses-sdk block of at least 9. My understanding from the documentation (https://developer.android.com/reference/android/Manifest.permission.html#READ_PHONE_STATE) (though it is slightly ambiguous) is that if minSdkVersion is specified greater than 3, the READ_PHONE_STATE will not be implicitly added. I have introduced targetSdkVersion when it was missing in my loose AndroidManifest files, but many of the google AARs contain AndroidManifest files inside them that only specify a minSdkVersion.

    Can you help me to determine why Cloud Build is introducing this permission?
     
    pfleetwood22, Sep 13, 2017
    #7

  8. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    If the google AARs are missing targetSdkVersion - that's bad. Can you please tell me which ones?
    In that case, it has probably nothing to do with the cloud build. Pinging @dannyd in case this is something known.
     
    Yury-Habets, Sep 15, 2017
    #8

  9. pfleetwood22

    pfleetwood22

    Joined:
    Jun 6, 2016
    Posts:
    28
    Just to reiterate, my local gradle builds do not introduce the READ_PHONE_STATE permission, but the Cloud Builds do.

    All these AARs in my project have a minSdkVersion but not a targetSdkVersion:

     
    pfleetwood22, Sep 15, 2017
    #9

  10. pfleetwood22

    pfleetwood22

    Joined:
    Jun 6, 2016
    Posts:
    28
    pfleetwood22, Sep 18, 2017
    #10

  11. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    This issue was fixed in all Unity versions starting 17.1 (in one of the patch releases), 5.6 patch release pending.
     
    Yury-Habets, Sep 19, 2017
    #11

  12. pfleetwood22

    pfleetwood22

    Joined:
    Jun 6, 2016
    Posts:
    28
    @Yury-Habets Any word on the 5.6 patch release with this fix?
    Thanks
     
    pfleetwood22, Oct 9, 2017
    #12

  13. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    5.6.4p1 should be the one.
     
    Yury-Habets, Oct 10, 2017
    #13
    mayucy likes this.

  14. hutch_jl

    hutch_jl

    Joined:
    Jan 8, 2013
    Posts:
    40
    Hi @Yury-Habets , I've just seen that 5.6.4p1 has been released but there doesn't seem to be an obvious entry in the changelog referencing this bug, do you know if it made it in?
     
    hutch_jl, Oct 23, 2017
    #14

  15. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    Yes it should be there - looks like I missed to add the release note entry.
     
    Yury-Habets, Oct 23, 2017
    #15

  16. hutch_jl

    hutch_jl

    Joined:
    Jan 8, 2013
    Posts:
    40
    Great thanks, will give it a go.
     
    hutch_jl, Oct 24, 2017
    #16

  17. Aurigan

    Aurigan

    Joined:
    Jun 30, 2013
    Posts:
    291
    This is still happening in 2017.1.2p2

    Adding

    <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="25" />

    To each manifest in my project fixed it.
     
    Aurigan, Oct 31, 2017
    #17
    Dazo1985 likes this.

  18. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    @Aurigan please read carefully - the fix I've been talking of is about having Assets/Plugins/Android/res folder present. In this case, we generate an Android library, and it was missing targetSdkVersion in the manifest. I fixed that.

    However, if you have any plugins (libraries) added with NO targetSdkVersion in the manifest - you automatically get the dangerous permission in question. The only fix for this issue is to fix your plugins' manifests.
     
    Yury-Habets, Nov 3, 2017
    #18

  19. Aurigan

    Aurigan

    Joined:
    Jun 30, 2013
    Posts:
    291
    @Yury-Habets Hi, the issue for me came from including the IronSource Ad SDK. While I *could* fix this by adding a target SDK version myself after some wasted minutes or hours of my day I view this as something that Unity *could* do for me ... especially given that there's a minimum and target API already set in Player Settings ...
     
    Aurigan, Nov 7, 2017
    #19

  20. Yury-Habets

    Yury-Habets

    Unity Technologies

    Joined:
    Nov 18, 2013
    Posts:
    1,167
    @Aurigan no - this is what the plugin author must do - claim the minimum and target SDK levels he is expecting his plugin to work with. We can't decide it for him.
     
    Yury-Habets, Nov 14, 2017
    #20

  21. jknight-nc

    jknight-nc

    Joined:
    Jun 10, 2014
    Posts:
    52
    Why can't unity prevent the addition of READ_PHONE_STATE when the targetSdk is missing?
     
    jknight-nc, Jan 17, 2018
    #21

  22. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    835
    Because we collect manifests (if building with internal build system) or gradle does that and pass them to a manifest merger tool (which comes with android sdk). The tool does this while merging manifests.
     
    JuliusM, Jan 18, 2018
    #22

  23. adam_mehman

    adam_mehman

    Joined:
    Dec 11, 2014
    Posts:
    104
    i have only 2 manifests, both of them are having minsdk but unity still creates PHONE_STATE permission.

    I even tried to add <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="25" />

    I even tried to add tools:node="remove" and problem still persists

    What can I check more?

    I have a Unity 5.6.4f1
    I have few res folders
    I use Facebooks SDK and Unity Analytics.

    Should I install Unity 5.6.4p4 and try or?
     
    Last edited: Mar 28, 2018
    adam_mehman, Mar 28, 2018
    #23

  24. adam_mehman

    adam_mehman

    Joined:
    Dec 11, 2014
    Posts:
    104
    So I found it,

    Unity IAP plugin has READ_PHONE_STATE permission and Unity Channel (within their aar files).

    I will try to remove it now.
     
    adam_mehman, Mar 28, 2018
    #24

  25. adam_mehman

    adam_mehman

    Joined:
    Dec 11, 2014
    Posts:
    104
    Nope, didn't help.

    I lost all the ideas :/
     
    adam_mehman, Mar 29, 2018
    #25