Fix assert msg in crashreport + update SDK #101
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wopss
previously approved these changes
May 26, 2025
WSSDude
suggested changes
May 26, 2025
WSSDude
reviewed
May 26, 2025
wopss
requested changes
Jul 18, 2025
Co-authored-by: Octavian Dima <[email protected]>
Co-authored-by: Octavian Dima <[email protected]>
psiberx
approved these changes
Jul 18, 2025
wopss
approved these changes
Jul 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The assert thing we discussed on Discord + also dragged in SDK update, just in case
Note - maybe put in
<empty>or something into fmtstr buffer if aMessage is nullptr?