Calling AppInstance.GetInstances() before calling AppInstance.GetCurrent() causes a read access violation.

[jlaanstra]

Describe the bug
Calling AppInstance.GetInstances() before calling AppInstance.GetCurrent() causes a read access violation.

Steps to reproduce the bug

1. Create a new Reunion app.
2. in main call AppInstance.GetInstances() before calling AppInstance.GetCurrent().

Expected behavior
No crash.

Version Info
Preview

Additional info
Exception thrown: read access violation.
winrt::Microsoft::Windows::AppLifecycle::implementation::AppInstance::s_current.m_ptr was nullptr.

[andrewleader]

@andreww-msft looks like an AppInstance bug?

[koenvd]

Similar crash seems to happen when calling AppInstance::FindOrRegisterForKey.
Calling AppInstance::GetCurrent() before it seems to fix the crash.

(I'm on WindowsAppSDK 1.0.0-experimental1 released yesterday).

[andreww-msft]

Apologies for the delay in replying - and thanks for reporting this!
Yes, I'm seeing the same behavior - we'll get it fixed.

[andrewleader]

Fixed by #1416 which will be released in 1.0 Preview 2.