Closed ghost closed 1 year ago
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Hey @beppemac sorry for the late response.
Could you try altering the initNativeSdk function from Plugin.swift by adding
DispatchQueue.main.async { [weak self] in
... initialization code
}
And see if the problem still happens?
Thank you for the suggestion @lucas-zimerman
I put under DispatchQueue Async only the call to the SentrySDK.start
method and the error in XCode console seems to no longer appear.
Basically I edited the initNativeSdk function in Plugin.swift from
SentrySDK.start(options: options)
to
DispatchQueue.main.async { [weak self] in
SentrySDK.start(options: options)
}
You're welcome I'll discuss with the internal team if this is the best way to deal with this case on the official release but it should run without any issues for now.
Environment
Angular 16 Capacitor 5 Ionic 7 @sentry/angular-ivy: 7.54.0 @sentry/capacitor: 0.12.1 @sentry/tracing: 7.54.0
Steps to Reproduce
Expected Result
The app launches without reporting errors
Actual Result
The app launches without any problems for the user. But the error "OutOfMemory: The OS most likely terminated your app because it overused RAM." is logged on Sentry, without stack trace.
To see more informations about the error, I launched the app in debug mode, and below is the log from XCode console. If I remove Sentry.init call, the error doesn't show up.