Ensure WOLAPI COM ProgID registration and safe wide char conversion #273
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes CLIENT-26M. The issue was that: WOLAPI COM object's missing ProgID registry entry causes null pointer dereference in
wcstombsduring system lookup.safe_wcstombsfunction towchar_compat.hto provide a null-pointer-safe wrapper forwcstombs.WideCharToMultiBytemacro to usesafe_wcstombsfor improved robustness when converting wide characters to multi-byte strings.ensureWOLAPIProgIDRegistrationfunction inwolInit.cppto explicitly register WOLAPI COM object ProgIDs (WOLAPI.Chat).ensureWOLAPIProgIDRegistrationbefore COM operations incheckInstalledWolapiVersionto prevent crashes on Windows versions that strictly validate COM registry entries.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 8425323
Not quite right? Click here to continue debugging with Seer.