You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
joaomoreno opened this issue
Oct 26, 2023
· 6 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugelectronIssues and items related to ElectronupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededwindowsVS Code on Windows issues
Is VS Code calling either the Wi-Fi or Location APIs and has a use case for location? If not, this may result in end-user confusion.
As for rollout schedule:
In a Windows Insider Preview release, the changes will first take effect in October 2023.
You'll then have until the following Windows feature release in fall of 2024 to test your app's scenarios, and to make any necessary changes. After that date, Windows devices will begin getting the update that contains the behavior change described above.
The text was updated successfully, but these errors were encountered:
Prompt confirmed, affects all Electron applications.
deepak1556
added
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
electron
Issues and items related to Electron
labels
Dec 6, 2023
Got steps to retrigger the prompt for further analysis. One thing I found today, prompt does not trigger with Electron 27 based insiders. This hints positive, we might not need to make any changes in the runtime. I will confirm the details in following days.
WlanQueryInterface was being called on application startup in stable as part of creating the network context as seen in the screenshot below
The relevant code has been refactored and removed from the startup path since this CL https://chromium-review.googlesource.com/c/chromium/src/+/4485483 which first landed in Chromium 115, also validated there are no other usages of the affected api in the latest insiders based on Chromium 118. Closing this issue are resolved, next stable release 1.86 should have the changes as well.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugelectronIssues and items related to ElectronupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededwindowsVS Code on Windows issues
Due to this upcoming breaking change in Windows, it seems like VS Code is shown as an application which occasionally asks for Location:
As for rollout schedule:
The text was updated successfully, but these errors were encountered: