Replies: 2 comments 8 replies
-
Hi @Alex293, I'm still investigating this, but at the very least it seems that this crash only happens with an empty string. So these will all not crash: @Test func foo() {
reportIssue(" ")
reportIssue("1")
reportIssue(/*nil message*/)
} Do you ever run into this crash when specify a non-empty message? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Also, FWIW, this crash affects just plain Swift Testing: import Testing
@Test func foo() {
Issue.record("") // 🛑
} So it doesn't look like this is an issue with our library, but it is something we can workaround. I am going to convert this to a discussion for now and we can continue the conversation over there. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm hitting a crash while running tests on iOS 15,16 and 17 since 1.2.4. The error vary a bit version by version but seems to be always a bad memory access. A full reproducer with a test case is joined below.
is enough to reproduce though.
I haven't spent much time but I'm pretty sure it either the unsafe cast that doesn't work which would mean the symbol is not mangled the same between iOS 18 and below or maybe the isolation of the auto-closure ?
I'll try to investigate more but I afraid this is beyond my skills for now :)
All this is using the latest App Store Xcode Version 16.3 (16E140) with the provided toolchain.
CrashIssueReporting.zip
Beta Was this translation helpful? Give feedback.
All reactions