Search Issue Tracker

Status: Fixed in Unity 5.6.0

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

-

-

Priority: 7Not yet prioritized for a release

-

Severity: 1Crash or major loss of functionality

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 (111)

  1. 3ea0aae0e4f6ecd6c2b75503a437ba33?d=mm

    H-Alex

    Feb 23, 2017 15:32

    Working confirmed in 5.5.1p4

  2. 78f4debf14ab9850e224d2747b2227a8?d=mm

    ASPePeX

    Feb 17, 2017 23:42

    5.5.1p4 is out and works (https://unity3d.com/unity/qa/patch-releases).

  3. 78f4debf14ab9850e224d2747b2227a8?d=mm

    ASPePeX

    Feb 16, 2017 11:40

    The fix will also be in 5.5.1p4, which should be coming this week.

    https://forum.unity3d.com/threads/5-5-released.443545/page-5#post-2959433

  4. 76538e1e59bd6db1ad28bfd318c8609e?d=mm

    ITSTH

    Feb 14, 2017 19:41

    Same here. Seems to work with 5.6.0b8.

  5. 78f4debf14ab9850e224d2747b2227a8?d=mm

    ASPePeX

    Feb 14, 2017 10:25

    Even tho it is not mentioned in the release notes it seems to be fixed in 5.6.0b8.

  6. 87fec6499406e63e03117df161d53150?d=mm

    SpudRat3

    Feb 14, 2017 07:01

    Wow. This is really getting annoying.

  7. 98c2c2eac39bb3f6cc4e3e7e39307a93?d=mm

    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.

  8. 06301a02c761d4f59e0616e0259f079d?d=mm

    AppDesignDave

    Feb 11, 2017 00:52

    Its still crashing on v5.6.0b7

  9. 0b07b2e9367c0fde31ab95bee8644ac7?d=mm

    toobaditsdestiny

    Feb 09, 2017 15:48

    Why is this marked as resolved when it's clearly not?

  10. 0b07b2e9367c0fde31ab95bee8644ac7?d=mm

    toobaditsdestiny

    Feb 09, 2017 15:44

    Still not fixed in 5.6.0 or any of the betas.

All about bugs

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