-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add flag indicating which package version is used (GitHub or Marketplace) #479
Conversation
|
{ | ||
if(!FPaths::FileExists(GetHandlerPath())) | ||
{ | ||
UE_LOG(LogSentrySdk, Log, TEXT("Crashpad executable couldn't be found so Breakpad will be used instead. " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get how we fall back to Breakpad
. Is that an implicit fallback during initialization due to a missing Crashpad
executable? Because the non-existing path still gets set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We determine which backend sentry-native
should be using by checking whether the crashpad_handler
executable exists within the package during the plugin's build. If at some point user decides to switch to Breakpad
simply deleting the crashpad_handler
executable won't be enough and plugin rebuild will be required. In this case handler path will be ignored during the initialization and won't affect its result.
FPlatformMisc::SetCrashHandlingType(settings->EnableAutoCrashCapturing | ||
? ECrashHandlingType::Disabled | ||
: ECrashHandlingType::Default); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a fallback to still keep the built-in crash reporter functional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, without it we won't be able to restore normal crash reporter behavior within the same editor session even after disabling EnableAutoCrashCapturing
in plugin's settings.
plugin-dev/Source/Sentry/Private/Desktop/SentrySubsystemDesktop.cpp
Outdated
Show resolved
Hide resolved
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
This PR introduces the following changes:
IsMarketplace
flag value is set in CI during the plugin packagingIsMarketplace
flag added to the default event's contextsentry-native
initialization logic