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

-[SentryProfilerState appendBacktrace:]_block_invoke #3510

Closed
zhou934381967 opened this issue Dec 19, 2023 · 8 comments
Closed

-[SentryProfilerState appendBacktrace:]_block_invoke #3510

zhou934381967 opened this issue Dec 19, 2023 · 8 comments

Comments

@zhou934381967
Copy link

Platform

iOS

Environment

Production

Installed

Swift Package Manager

Version

8.9.6

Did it work on previous versions?

No response

Steps to Reproduce

have a crash.

Expected Result

no crash

Actual Result

Have a Crash.
截屏2023-12-19 12 09 13

Are you willing to submit a PR?

No response

@philipphofmann
Copy link
Member

Thanks for reporting this @zhou934381967. We see a couple of crashes in our internal SDK crashes.

@zhou934381967
Copy link
Author

Authentication error: The domain for your Google account (gmail.com) is not allowed to authenticate with this provider. Yes You cannot view the internal SDK crashes.

@kahest
Copy link
Member

kahest commented Dec 20, 2023

@zhou934381967 This is intended, it's a Sentry internal resource with additional context for this issue - you will not be able to open this.

@zhou934381967
Copy link
Author

I can't see these internal crashes, and I don't know what other crashes are at present, and whether the crashes encountered by our project have been solved. Is there another way to get it? I also found that v8.17.2 performance monitoring data is not reported. What is the cause of this?

@kahest
Copy link
Member

kahest commented Dec 20, 2023

@zhou934381967 Correct, you cannot see these internal crashes. Currently, no further action is required from your side for the crashes you reported. We will investigate and let you know if we need more information from you.

If you miss performance data with 8.17.2, you can create a new issue, but make sure you provide sufficient information and be as specific as possible.

@philipphofmann
Copy link
Member

@indragiek, could #3522 could also fix this issue?

@zhou934381967
Copy link
Author

Has the problem been solved?

@philipphofmann
Copy link
Member

@zhou934381967, yes, I think #3522 should fix the issue, which will be in the next release 8.19.0. Please reopen if it doesn't fix the issue.

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

No branches or pull requests

3 participants