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'

Mobile

-

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
Log in to vote on this issue

Comments (115)

  1. E-Reg

    Jan 24, 2017 11:43

    Isn't this kind of a major bug or am I just really unlucky working with this?

  2. SpudRat3

    Jan 24, 2017 05:34

    Wow. 165 votes. Is someone working on this?

  3. sangryul

    Jan 23, 2017 03:08

    @H-ALEX maybe..
    AndroidJavaException: java.lang.ClassNotFoundException: com.singleshade.unitylocationoverride.UnityLocationOverride
    I found logcat..
    exist UnityLocationOverride.jar

  4. SpudRat3

    Jan 20, 2017 18:30

    All three are identical Fire tablets running FireOS 5.3.2.1, and all settings are identical. The only difference is that one (the one that is working) has been used for direct USB downloads from my development machine. However, I downloaded your sample app from my server and installed it in exactly the same way on each device. Clearly, there is something I am missing, and therefore not telling you :)

  5. H-Alex

    Jan 20, 2017 09:23

    What's the android version on those not working ? maybe it was not compilted with the right android target I don't know... Don't forget to enable location services as well, seems obvious but we never know... :)

  6. SpudRat3

    Jan 20, 2017 00:05

    Actually, I was wrong. It seems that it never finishes initializing. Really weird. I am testing on three identical Fire tablets, and it works on one of them, but not the other three. Checking all settings on all devices.

  7. SpudRat3

    Jan 19, 2017 22:58

    H-ALEX Never Mind, it just takes long to initialize on certain devices!

  8. SpudRat3

    Jan 19, 2017 22:54

    H-ALEX, I got your plug in, and it stopped the crash, but now all of my lats and lons are coming in at zero, zero on some devices. Any thoughts?

  9. H-Alex

    Jan 19, 2017 19:12

    No you're right I didn't go that far into the integration. However I used 0 as minDistance, so it's always updating. It's also going for the best accuracy with GPS or network depending on the sensors you have on you mobile.

  10. Zuicis

    Jan 19, 2017 19:09

    @H-ALEX not working with arguments: .start(float desiredAccuracyInMeters = 10f, float updateDistanceInMeters = 10f);

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.

Latest issues

See all new issues