You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a low number of crashes reported where the app had been in the background for some time and just being brought to foreground by the user. The crash log points inside Braze SDK running on a background queue named com.braze.core; see stack trace excerpt under Verbose Logs.
Hi @pyrtsa, could you write in to [email protected] with this stack trace along with any additional details of your Braze integration (i.e. which features you are using, any sample code you may have)? And to clarify, could you also confirm if you are seeing this same stack trace for each crash that is being reported?
Platform
iOS
Platform Version
iOS 16.7.10
Braze SDK Version
11.0.0
Xcode Version
16.0
Computer Processor
Apple (M1)
Repro Rate
Rarely
Steps To Reproduce
We have a low number of crashes reported where the app had been in the background for some time and just being brought to foreground by the user. The crash log points inside Braze SDK running on a background queue named
com.braze.core
; see stack trace excerpt under Verbose Logs.Expected Behavior
The app should not crash.
Actual Incorrect Behavior
Verbose Logs
Additional Information
No response
The text was updated successfully, but these errors were encountered: