Bug 1258452 - Explicitly request READ_EXTERNAL_STORAGE permission. r=sebastian

This permission was added in API 16, and is only enforced in API 19+.
(It's benign to add it to APKs installed on API 15.)

We want to declare it explicitly so that the bouncer APK and the main
APK have the same permission set.  There appears to be some fanciness
with Gradle's implied permission system where the bouncer APK does not
request READ implicitly where-as the main APK does request READ
implicitly.  This just makes things explicit (and uniform).

MozReview-Commit-ID: LBblAPa0duV

--HG--
extra : rebase_source : 616fa58ccd9063088abb14240265a20ac4e48da7
extra : histedit_source : abf6211896e99cc7b53f9c36714d056f0d44d63f
This commit is contained in:
Nick Alexander 2016-03-14 14:23:56 -07:00
parent 8204c8154a
commit 0b9f03564c

View File

@ -29,6 +29,10 @@
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.INTERNET"/>
<!-- READ_EXTERNAL_STORAGE was added in API 16, and is only enforced in API
19+. We declare it so that the bouncer APK and the main APK have the
same set of permissions. -->
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="com.android.launcher.permission.INSTALL_SHORTCUT"/>
<uses-permission android:name="com.android.launcher.permission.UNINSTALL_SHORTCUT"/>