Search Issue Tracker
Fixed in 5.6.0f3
Fixed in 5.5.X, 5.6.X
Votes
234
Found in
5.5.0f3
Issue ID
856773
Regression
Yes
[Android] Location app crashes due to error 'jstring has wrong type: android.location.Location'
How to reproduce:
1. Open the attached project
2. Build and Run Test scene on Android device (it has only one line Input.location.Start() in script)
3. When app launches, select "Allow" in the permission dialog
4. App will start and location service will start to initialize
5. Notice that app will crash in several second after beginning of location init
Reproducible: 5.5.0f1, 5.5.0f3, 5.6.0a5
Not reproducible: 5.5.0b11
Issue is not device specific
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
kniewolewski
Feb 13, 2017 01:36
Any news when this fix will be released? It still doesn't work in any new 5.5 and 5.6 Unity versions.
AppDesignDave
Feb 11, 2017 00:52
Its still crashing on v5.6.0b7
toobaditsdestiny
Feb 09, 2017 15:48
Why is this marked as resolved when it's clearly not?
toobaditsdestiny
Feb 09, 2017 15:44
Still not fixed in 5.6.0 or any of the betas.
DavidConsolo
Feb 08, 2017 22:21
Still broken in 5.6.0b4
11maxed11
Feb 07, 2017 19:46
Another confirmation; 5.6.0b7 still crashes on Windows 10.
Let's hope we get the fix asap
ASPePeX
Feb 07, 2017 16:12
Can confirm, 5.6.0b7 crashes.
I didn't expect b7 THIS early in my last post. But lets hope for b8.
@REDBREAD beta release builds eat kittens. 5.4.4f1 would be the last working version, 5.4.4p1+2 are broken tho.
redBread
Feb 07, 2017 15:48
5.6.0b7 still crashes. Maybe it's fixed in the next beta or in the final release.
Currently I'm not sure if waiting or going back to the last working 5.?.? is the way to go.
ASPePeX
Feb 07, 2017 10:21
5.6.0b6 was release before this issue was marked as fixed. I guess it is coming with b7 which should be around the corner if they keep up with their release cycle (https://unity3d.com/unity/beta/archive).
cmbellman
Feb 07, 2017 09:15
When can we get 5.6.0?