D Duncan williamson Member Licensed User Longtime User Nov 23, 2017 #1 Hi all I have built an app which is being distributed to quite a few of our customers.. however during install of the app the customer is told it will get access to modify or delete the contents of their SD card and read the contents of their SD card. In the app I have set #CanInstallToExternalStorage: False Several customers are now refusing to install the App due to what they perceive as a major security problem. Interestingly I receive the same message when I install it on my own Phone ( a samsung s7 ) and I dont have an SD card installed. Can anyone tell me how to overcome this problem ? Regards Duncan
Hi all I have built an app which is being distributed to quite a few of our customers.. however during install of the app the customer is told it will get access to modify or delete the contents of their SD card and read the contents of their SD card. In the app I have set #CanInstallToExternalStorage: False Several customers are now refusing to install the App due to what they perceive as a major security problem. Interestingly I receive the same message when I install it on my own Phone ( a samsung s7 ) and I dont have an SD card installed. Can anyone tell me how to overcome this problem ? Regards Duncan
KMatle Expert Licensed User Longtime User Nov 24, 2017 #2 Do you write/read files (from assets maybe?). "SD-Card" doesn't mean the external SD-Card as even the internal memory is handled as/called "SD-Card". Note that you can't access the external SD-card anyway. So there's no issue here. Upvote 0
Do you write/read files (from assets maybe?). "SD-Card" doesn't mean the external SD-Card as even the internal memory is handled as/called "SD-Card". Note that you can't access the external SD-card anyway. So there's no issue here.
Erel B4X founder Staff member Licensed User Longtime User Nov 24, 2017 #3 They are talking about the WRITE_EXTERNAL_STORAGE permission. There are several ways to avoid it: 1. Use File.DirInternal instead of File.DirRootExternal or File.DirDefaultExternal 2. Switch to runtime permissions and use RuntimePermissions.GetSafeDirDefaultExternal: https://www.b4x.com/android/forum/threads/runtime-permissions-android-6-0-permissions.67689/#content Upvote 0
They are talking about the WRITE_EXTERNAL_STORAGE permission. There are several ways to avoid it: 1. Use File.DirInternal instead of File.DirRootExternal or File.DirDefaultExternal 2. Switch to runtime permissions and use RuntimePermissions.GetSafeDirDefaultExternal: https://www.b4x.com/android/forum/threads/runtime-permissions-android-6-0-permissions.67689/#content
D Duncan williamson Member Licensed User Longtime User Nov 26, 2017 #4 Thank you KMatle and Erel, the app creates and uses a sqlite database and I am using File.DirRootExternal so I guess that is the cause. I will look at moving it to File.DirInternal to escape getting the permission message. Upvote 0
Thank you KMatle and Erel, the app creates and uses a sqlite database and I am using File.DirRootExternal so I guess that is the cause. I will look at moving it to File.DirInternal to escape getting the permission message.
