Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] Fix COMException using Connectivity class #10062

Merged
merged 1 commit into from
Sep 13, 2022
Merged

[Windows] Fix COMException using Connectivity class #10062

merged 1 commit into from
Sep 13, 2022

Conversation

jsuarezruiz
Copy link
Contributor

Description of Change

Fix COMException using Connectivity class on Windows.

fix-7393

Issues Fixed

Fixes #9972

@jsuarezruiz jsuarezruiz added t/bug Something isn't working platform/windows 🪟 area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info labels Sep 12, 2022
Copy link
Member

@mattleibow mattleibow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit unfortunate this. Can we file a bug and see if this is a bug in the WASDK? This should only be accessing system things and not tied to a particular Window.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info platform/windows 🪟 t/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connectivity implementation not thread-safe on Windows, returning incorrect network status
3 participants