Search Issue Tracker

Fixed in 5.6.0f3

Fixed in 5.5.X, 5.6.X



Found in


Issue ID




[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

Comments (115)

  1. H-Alex

    Jan 17, 2017 17:33

    For those willing to use a plugin, I've made one available for free here :
    It's pretty straightforward and should be very easy to remove when Unity solve this. Cheers !
    Do not hesitate to leave me mail if you found it useful.

  2. Bright-Yeo

    Jan 17, 2017 06:44

    We keen for fixing this issue.. we are going to publish in some week but it is totally suspended.

  3. AurekSkyclimber

    Jan 17, 2017 04:52

    This is currently the eighth most voted item of all time, and two votes away from becoming number seven. Twenty-six more votes and it will be number five. I honestly didn't think that there were this many other people doing Android location based apps. Here's hoping for an update from Unity sooner than later.

  4. italomarques

    Jan 17, 2017 03:06

    Location service not update correctly on android , please fix this

  5. italomarques

    Jan 17, 2017 03:06

    Location service not update correctly, please fix this

  6. Emperor

    Jan 16, 2017 19:04

    Anyone found a workaround other than writing a plugin?

  7. PrismKDog

    Jan 16, 2017 17:40

    This is getting ridiculous! Unity this deserves immediate attention.

  8. maynull

    Jan 16, 2017 13:57

    Unity can you please let us know if we can do anything to solve or if you have any plans on fixing it ? 5.5 just become unusable for us.

  9. Phantom75

    Jan 16, 2017 12:44

    Most vote on all active tickets and it's still on lowest priority/no plans for fix after 45 days. Looking into to this wouldn't be overhasted now.

  10. ASPePeX

    Jan 16, 2017 08:53

    5.4.4p1 is broken too, 5.4.4f1 seem to be fine tho.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.