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

[Problem/Bug]: IsCustomCrashReportingEnabled inconsistently documented #4965

Closed
pushkin- opened this issue Dec 3, 2024 · 3 comments · Fixed by MicrosoftDocs/edge-developer#3329
Labels
bug Something isn't working

Comments

@pushkin-
Copy link

pushkin- commented Dec 3, 2024

What happened?

This page says:

To prevent crash dumps from being sent to Microsoft, set the IsCustomCrashReportingEnabled property to false.

However the docs say that that property defaults to false and:

When IsCustomCrashReportingEnabled is set to true, Windows won't send crash data to Microsoft endpoint.

Fix one or the other to be consistent.

Importance

Low. My app is not very affected, or this only affects development.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

No response

Framework

Winforms

Operating System

Windows 11

OS Version

No response

Repro steps

see above

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

@pushkin- pushkin- added the bug Something isn't working label Dec 3, 2024
Copy link

github-actions bot commented Dec 3, 2024

Hi, @pushkin-!

It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?

WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.

Thank you for your cooperation!

@sivMSFT
Copy link

sivMSFT commented Dec 10, 2024

Hi @pushkin-,

Thank you for bringing this to our attention. The CoreWebView2EnvironmentOptions.IsCustomCrashReportingEnabled is accurate. We will fix the other one to make it consistent.

@mikehoffms
Copy link
Contributor

@sivMSFT - i entered AB#55445097 internal item suggesting to clarify Ref docs.

PR has been merged/published to make regular docs
https://learn.microsoft.com/microsoft-edge/webview2/concepts/data-privacy?tabs=dotnetcsharp#custom-crash-reporting
match Ref docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants