Hi, I have multiple suspicious crashes happening shortly after application startup. They are all EXC_BAD_ACCESS/KERN_INVALID_ADDRESS coming from objc_autoreleasePoolPop. I already looked through all suspicious places which operate with unsafe pointers etc, but all that code is never executed during application startup. I'm not able to reproduce the crash myself, but it happens quite often for AppStore build. I tried using instruments, testing code compiled locally in release mode, but without any luck. 2022-06-01_13-38-07.9896_+0200-6c7cf9d2fbe48e7f5156b686f0fa29ef8c1e7be6.crash 2022-06-02_16-28-55.6355_+0200-b93559cecc702efecb2d60b40fd613eb9f7e3684.crash 2022-06-08_10-54-10.9202_+0200-de392db1bdbd100601fd51ec095ae2684762a173.crash

Hi there, I have following crash during application start on iOS below 15.0, even in simulator dyld: Symbol not found: _$s10Accelerate4vDSPO3dotySfx_q_tAA0A6BufferRzAaER_Sf7ElementRtzSfAFRt_r0_lFZ Referenced from: /Users/Nikita/Library/Developer/CoreSimulator/Devices/21071B75-CC1F-46E5-94B3-5E01072B90C6/data/Containers/Bundle/Application/73D74763-449A-4E20-B7EB-8807008B335B/vDSP test.app/vDSP test Expected in: /usr/lib/swift/libswiftAccelerate.dylib Sample code is very simple and looks like this:         let vector1: [Float] = [0, 1, 2, 3, 4, 5, 6, 7]         let vector2: [Float] = [0, 1, 2, 3, 4, 5, 6, 7]         // Causes crash on application start         let result = vDSP.dot(vector1, vector2)         // Works fine         let resultMul = vDSP.multiply(vector1, vector2)         let result1 = vDSP.sum(resultMul) According to docs, vDSP.dot is available since iOS 13.0.

After upgrading to Xcode 14 I face weird issue with PDF assets. PNGs generated from PDF assets have transparent background instead of fancy gradient. Issue is present in both Xcode 14.0.1 and 14.1 See attached images

Hello there. Since Xcode 12 I'm facing issue with Sent events section disappearing in Interface Builder when set up as custom class and module. public class TestButton: UIButton {} Problem appears when custom class is part of another binary framework. When custom class is part of source code dependency, all events are appearing just fine. Of course, there is a workaround to use Sent Events by changing button class to default UIButton, assigning events and then changing back to custom class and module. However, it would be nice if I could use Sent Events without those unnecessary extra steps.