Search Issue Tracker

Fixed in 2017.2

Votes

5

Found in

5.6.0f3

Issue ID

902234

Regression

Yes

[WSA] WorldAnchorStore.GetAsync throws an exception when starting deployed HoloLens app built

Windows Store Apps

-

Steps to reproduce:
1. Open the attached project (AnchorTestRepro.zip)
2. Switch platform to Windows Store
3. Build for WSA Universal 10 SDK, Target device - HoloLens, Build type - D3D (C# Project and Development build checked)
4. Open Visual Studio solution
5. Deploy on emulator or HoloLens (Debug x86)
6. Observe the Output:
WinRTScriptingObjectWrapper::InternalAddRef Reference Count cannot be zero

Expected result: Unity should not throw an exception
Actual result: Unity throws exception

Reproduced with:5.6.0p1, 2017.1.0b1
Not reproduced with: 5.5.3p1

Fixed in: 2017.2.0a1
Backported to: 2017.1.0b9, 5.6.1p4

Comments (11)

  1. E716e696fc67eb6f0d9c48cc77a79fb9?d=mm

    jschutz

    Jun 23, 2017 18:50

    Fixed in 5.6.1p4

  2. 791d8458efe00527092a283b85114daf?d=mm

    Reeley

    Jun 07, 2017 06:34

    FYI we had a discussion about this here: https://github.com/Microsoft/HoloToolkit-Unity/issues/640
    currently a workaround is to move the GetAsync call from Awake to the Start method. Maybe this will help someone :)

  3. 2d2ad57a2a86d76f9cfdf242000f1558?d=mm

    dvroegop

    Jun 04, 2017 14:35

    I am still waiting for this to be fixed. It's not enough to say it will be fixed in future versions: we depend on this tooling to get our projects done.
    Any idea on the timeline?

  4. E716e696fc67eb6f0d9c48cc77a79fb9?d=mm

    jschutz

    Jun 02, 2017 17:54

    Still happens in 5.6.1p2

  5. 72551da693fe59626301477ddf22b902?d=mm

    mats_larsson

    May 31, 2017 10:29

    Still an issue on 2017.1.0b7

  6. 35e30c06d2a7e9f320ab11b287bc6d70?d=mm

    kurbuntu

    May 30, 2017 22:39

    I am experiencing this in Unity 5.6.1f1, Holotoolkit-Unity 1.5.7, and Visual Studio 2017.

  7. Aba6e1147702f89f672dfcb2ebfdf206?d=mm

    FejZa

    May 30, 2017 07:09

    This is still an issue in 5.6.1f1

  8. 877da6b22f31d11c48618884d8d6e4d7?d=mm

    dixoncb

    May 28, 2017 13:16

    When will this fix be released? The button above says that the issue has been resolved, but I can confirm it's still there with Beta 2017.1.0b7.

  9. A95095c7c751221421cff1e0bd689b73?d=mm

    brunogsimoes

    May 26, 2017 11:52

    I confirm having this issue with Unity 2017.1.0b6 (64-bit) and Unity 5.6.1f1 (64-bit)

  10. 72551da693fe59626301477ddf22b902?d=mm

    mats_larsson

    May 23, 2017 07:04

    Having this issue on Unity 2017.1.0b5 and Visual Studio Community 2017 version 15.1

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.