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

Windows Native: Add call to sentry_init in the main function at compile time #628

Open
bruno-garcia opened this issue Mar 10, 2022 · 4 comments
Assignees
Labels

Comments

@bruno-garcia
Copy link
Member

Follow up from #527

The Native SDK is currently initialized via C# (after the Unity C# layer runs). It works well to capture crashes after the game boots properly. The one downside is that we don't capture crashes of the engine bootstrapping itself. Our docs are written to indicate it works this way because we built it like that for Android and iOS.

Until this task is completed we need to update the docs to mention the early crash detection is for mobile only.

@bruno-garcia
Copy link
Member Author

#527 (comment)

@bruno-garcia
Copy link
Member Author

PR tackling #622

@vaind
Copy link
Collaborator

vaind commented Apr 29, 2022

This is on hold now, @bitsandfoxes can you please add a comment with details/status and move to "blocked" or "backlog" in the project? We may also need to update the priority

@bitsandfoxes
Copy link
Contributor

We've got a draft exploring how we'd make it work #622
Unity ships with pre-built playback engines but provides the source code. The idea is to add Sentry Native to the playback engine and build it ourselves. Why we're currently not going forward with this: The draft relies on finding the correct package to locate vswhere to locate msbuild and there is a whole lot of uncertainty and risk with this approach.

Maybe we could do it like Unity and ship with pre-built playback engines and provide the source for signing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Archived in project
Development

No branches or pull requests

3 participants