Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

[Solved] Google UnityIAP added permissions for read write storage

Discussion in 'Unity IAP' started by deepesh, Aug 30, 2017.

Thread Status:
Not open for further replies.
  1. deepesh

    deepesh

    Joined:
    Sep 24, 2013
    Posts:
    11
    Hi All,

    After integrating UnityIAP in oou project, the following permissions are been added to the manifest.

    I am guessing basically for Amazon sdk tester

    uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"

    Since Android 6.0, Google play is particular about permissions asked to the end user. This is affecting our GooglePlay feature release.

    Q1. Are these mentioned permissions are required specific to GooglePlay IAP in any way? If not can we remove them? If Yes, what will affect on client side regarding UnityIAP?

    1. If user denies the permission, do we have to look for a native way to ask the user that permission again, Or is there functionality provided in Unity or UnityIAP which we might not be aware off?
    Q2. We know a sort of hack way mentioning that permission with a MaxSdk version, something like following:

    1. uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="1"
    2. Is there any other neat way?
    Thanks,
    Deepesh
     
    Last edited: Aug 31, 2017
  2. deepesh

    deepesh

    Joined:
    Sep 24, 2013
    Posts:
    11
    Hi All,

    Just an update:

    Even after denying the read/write permission, there was no issue found with UnityIAP at least for what functionality we are using for google play.

    So we are planning to remove that permission..

    For our second question, we found a plugin mentioned follow:

    https://github.com/Over17/UnityAndroidPermissions

    Seems to be working fine! for asking user run-time permissions on android :)

    -Deepesh
     
    nicholasr likes this.
Thread Status:
Not open for further replies.