Search Issue Tracker
Fixed in 2017.2.0f3
Won't Fix in 5.5, 5.6, 2017.1
Fixed in 2017.2
Votes
0
Found in
5.6.0f3
Issue ID
915891
Regression
No
[Android] ACCESS_FINE_LOCATION permission is included in the AndroidManifest.xml when it's not supposed to
Steps to reproduce:
1) Download attached project 'GPSAndroidTest56.zip' and open in Unity
2) In Build Settings, make sure Build System is set to ADT (Legacy)
3) Export 'Scene1'
4) Open the 'AndroidManifest.xml' file from the exported android project
You will see that ' <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />' permission is included in the build
Expected result: Using higher value than 500 meters should not require to turn GPS chip on
Actual result: Using higher value than 500 meters requires to turn GPS chip on (check attached image 'bug.png')
Reproduced with:
5.3.7p4, 5.4.5p2, 5.5.3p4, 5.6.1p1, 2017.1.0b7, 2017.2.0a1
--------------------------------------------------
Fixed in: 2017.3.0a1 and 2017.2.0b8
Note: 'Low Accuracy Location' option is added in the Player Settings
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Terrain inspector is proposing a shader which isn't there
- Warnings are missing when compiling for certain platforms (opengl)
- Scaling problem with PanelSetting set to ScaleWithScreen/Expand
- [Hub] Editor is shown in the "Installing" state indefinitely when the installation fails due to INVALID_DESTINATION error
- IL2CPP: Nested Try-Catch and Throw statement results in incorrect behaviour
technicat
Nov 24, 2017 20:14
I don't think it was fixed in 2017.2. I see it in 2017.2p1 and 2017.2p2. This poses a problem on the Amazon Appstore where it limits availability to devices with GPS.