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
Unit tests using TestCurrentDateProvider, such as SentryFramesTrackerTests or SentryANRTrackerV2Tests, fail with EXC_BAD_MEMORY when accessing TestCurrentDateProvider.systemDate().
This is a known issue and some people report that a similar looking crash was fixed in Xcode Beta versions, see:
Description
Unit tests using
TestCurrentDateProvider
, such as SentryFramesTrackerTests orSentryANRTrackerV2Tests
, fail withEXC_BAD_MEMORY
when accessingTestCurrentDateProvider.systemDate()
.This is a known issue and some people report that a similar looking crash was fixed in Xcode Beta versions, see:
Xcode 16
/iOS 18
: Thread 21: EXC_BAD_ACCESS (code=1, address=0xfffffffffffffff8) in ETagManager.Response.encode(to:) RevenueCat/purchases-ios#3949On this repository, the issue persists: RevenueCat/purchases-ios#4177.
On Xcode 15.4, the unit tests run without failure.
The text was updated successfully, but these errors were encountered: