I was using OCmock for my tests and after rebuilding it with same Xcode version as all my other libs the coverage started to generated.

Same issue

Same issue on Xcode 16.4 and Xcode 26

@DTS Engineer Okay, so Xcode 15 SDK builds on Sequoia won't work for clients on older Xcodes, That's a major problem due to Swift forward incompatibility. Any workarounds? Can we use xcode-select with an older Xcode install on Sequoia for CLI builds? will that work?

We need build a xcframework if I build it with new Xcode version and the app is build with old Xcode version that will not work

@App Review Yes I still need a help with that question where in this link: contact us I should update my phone number? I used Membership & Account -> Account Information update and send you a message with my phone number

@App Review I have tried to schedule a meeting but was rejected in the end Amy chance we can answer the question in the thread so it will be also visible for other developers?

I have the same issue @DTS Engineer was it resolved, if yes any insight on what was wrong?

My issue was not matching deployment targets between extension and hosting app

@DTS Engineer you have mentioned the issue under the following ticket: (r. 32863680). Do we as developers have the right to access that ticket? For instance the following http://www.openradar.me/32863680, http://www.openradar.me/FB32863680 Doesnt lean to anything, my guess is that its internal apple issues, can you please confirm

We see the similar logs on just iOS app

@DTS Engineer We have similar issues any insight about that crash or how to prevent it. In our case we have the following stack trace: What the OUTLINED_FUNCTION means ? how it can be prevented? 0 libswiftCore.dylib 0x37445c __swift_allocate_boxed_opaque_existential_0 + 28 1 libswiftCore.dylib 0x1797d4 swift_getAtKeyPath + 100 2 SwiftUI 0x5a6520 OUTLINED_FUNCTION_23 + 532 3 SwiftUI 0x244114 OUTLINED_FUNCTION_651 + 88 4 SwiftUI 0x17c394 __swift_memcpy25_8 + 2024 5 SwiftUI 0xce172c OUTLINED_FUNCTION_12 + 1084 6 SwiftUI 0xce19c8 OUTLINED_FUNCTION_12 + 1752 7 SwiftUI 0x7a7538 OUTLINED_FUNCTION_28 + 3104 8 SwiftUI 0x15dc268 OUTLINED_FUNCTION_39 + 6700 9 SwiftUI 0x15de2ac OUTLINED_FUNCTION_39 + 14960 10 SwiftUI 0x15de308 OUTLINED_FUNCTION_39 + 15052 11 Pendo 0x13d5bc UIView.extensionMethod() + 5364 12 Pendo 0x13d620 @objc UIView.extensionMethod() + 5464

@DTS Engineer Thanks for you answer (I was pretty sure that was the reason but just wanted a confirmation.) If possible I would like to ask a follow up question. Some time arg1, arg2 doesnt work correctly for some frames: So for instance I have the following frame: frame #0: 0x000000010587ef98 Pendo`-[PNDScreenManager mymethod:arg1:arg2:](self=0x000060000176b300, _cmd="PNDScreenManager mymethod:arg1:arg2:", dict=0 key/value pairs, window=0x000000010370a400, rootViewController=0x000000010450b350) at PNDScreenManager.m:313:9 and those are the registers: register read General Purpose Registers: x0 = 0x0000000000000002 x1 = 0x000000000000000d x2 = 0x000060000029ed80 x3 = 0x0000000000000000 x4 = 0x000000010450b350 x5 = 0x0000000000000000 x6 = 0x0000000000000000 x7 = 0x0000000000000000 x8 = 0x0000000105b5b4df "PNDScreenManager mymethod:arg1:arg2:" x9 = 0x0abc76522d81005b x10 = 0x000000010371f948 x11 = 0x000000000000001f x12 = 0x000000010371f940 x13 = 0x0000000000000000 ... arg1 , and arg2 will print x0 and x1 as u suggested BUT not self and SEL and so on with rest of the parameters(as I would like). (only x4 the last parameter can be spotted). My question is: What will be the accurate and easy alternative for arg1, arg2 and etc (as it seems like x1,x2 are not consistent in that sense ) Thanks (if you could share any documentation about arm64 registers and how to work/debug with them will be appreciated )

I have the same issue here is my gist: gist

@DTS Engineer Thanks BUT that not what I am asking. I will try to make it more clear: GIVEN: @interface User2 : NSObject @property (nonatomic) NSString * firstName; @end AND firstName will NOT have assignment of ANY mutable subclasses like NSMutableString i.e the only assignment is of type NSString. QUESTION: Will the following be a "thread safe" (For current context thread safe definition: NO crash AND correct Result). If the following is NOT "thread safe" by the definition above could you please provide a reproducible snippet of code that breaks thread safety (not theoretical retain/release explanation)? (a side question. what is the Apple definition of thread safety?)