Post

Replies

Boosts

Views

Activity

iOS App Crashes with SIGABRT and XCTest.framework Not Loaded (Xcode 16.2, SwiftUI 6)
Hello Apple Developer Community, I’m experiencing an issue with my iOS app, "WaterReminder," where it builds successfully in Xcode 16.2 but crashes immediately upon launch in the iPhone 16 Pro Simulator running iOS 18.3.1. The crash is accompanied by a "Thread 1: signal SIGABRT" error, and the Xcode console logs indicate a dyld error related to XCTest.framework/XCTest not being loaded. I’ve tried several troubleshooting steps, but the issue persists, and I’d appreciate any guidance or insights from the community. Here are the details: Environment: Xcode Version: 16.2 Simulator: iPhone 16 Pro, iOS 18.3.1 App: WaterReminder (written in SwiftUI 6) Build Configuration: Debug Issue Description: The app builds without errors, but when I run it in the iPhone 16 Pro Simulator, it shows a white screen and crashes with a SIGABRT signal. The Xcode debugger highlights the issue in the main function or app delegate, and the console logs show the following error: dyld[7358]: Library not loaded: @rpath/XCTest.framework/XCTest Referenced from: <549B4D71-6B6A-314B-86BE-95035926310E> /Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/WaterReminder.debug.dylib Reason: tried: '/Users/faytek/Library/Developer/Xcode/DerivedData/WaterReminder-cahqrulxghamvyclxaozotzrbsiz/Build/Products/Debug-iphonesimulator/XCTest.framework/XCTest' (no such file), '/Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/Frameworks/XCTest.framework/XCTest' (no such file), '/Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/XCTest.framework/XCTest' (no such file), '/Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/Frameworks/XCTest.framework/XCTest' (no such file), '/Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/XCTest.framework/XCTest' (no such file), '/Users/faytek/Library/Developer/CoreSimulator/Devices/2A51383F-D8EA-4750-AE22-4CDE745164CE/data/Containers/Bundle/Application/56D8B44F-6613-4756-89F0-CB33991F0821/WaterReminder.app/Frameworks/XCTest.framework/XCTest' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_22D8075/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.3.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/XCTest.framework/XCTest' (no such file) What I’ve Tried: ◦ Verified that FBSnapshotTestCase is correctly added to the "Embed Frameworks" build phase. ◦ Confirmed that the Framework Search Paths in build settings point to the correct location. ◦ Ensured that all required frameworks are available in the dependencies folder. ◦ Cleaned the build folder (Shift + Option + Command + K) and rebuilt the project. ◦ Checked the target configuration to ensure XCTest.framework isn’t incorrectly linked to the main app target (it’s only in test targets). ◦ Updated Xcode and the iOS Simulator to the latest versions. ◦ Reset the simulator content and settings. Despite these steps, the app continues to crash with the same dyld error and SIGABRT signal. I suspect there might be an issue with how XCTest.framework is being referenced or loaded in the simulator, possibly related to using SwiftUI 6, but I’m unsure how to resolve it. Could anyone provide advice on why XCTest.framework is being referenced in my main app (since it’s not intentionally linked there) or suggest additional troubleshooting steps? I’d also appreciate any known issues or workarounds specific to Xcode 16.2, iOS 18.3.1, and SwiftUI 6. Thank you in advance for your help! Best regards, Faycel
0
0
241
5d
Xcode Code Signing Issues – Team Name Mismatch, Certificate & Provisioning Profile Errors
Hi everyone, I'm encountering several issues with Xcode's code signing and provisioning that I haven’t been able to resolve despite several attempts. I’m hoping someone here might have some insights or workarounds. Issues Encountered: Team Name Mismatch: My Apple Developer Program team is registered as Faycel Ayech (Team ID: 3K7UP6P2LQ), but in Xcode, only “Faycel Ayech” is displayed (the Team ID is missing). This seems to be affecting code signing and provisioning. Incorrect Certificate Association: The Apple Development Certificate in Xcode appears to be associated with my MacBook’s name (FayTek's MacBook Pro) rather than my personal Apple ID (Faycel Ayech). Despite revoking and recreating the certificate multiple times on both the Apple Developer Portal and within Xcode, the issue persists. Provisioning Profile Errors: I receive the following errors in Xcode: No profiles for 'com.Faycel.DrawCraft' were found. Invalid trust settings. Restore system default trust settings for certificate "Apple Development: Faycel Ayech (JW6VLM8FNS)". Simulator Issues: Due to the above issues, I am unable to run my app on the Simulator (using an iPhone 16 Pro simulator). Steps I’ve Already Taken: Deleted and recreated the Apple Development Certificate in both Xcode and the Apple Developer Portal. Enabled “Automatically manage signing” in Xcode. Verified that the correct team and bundle ID are selected under the Signing & Capabilities tab. Cleaned the build folder, restarted Xcode, and rebooted my Mac. Deleted Derived Data and manually downloaded the provisioning profiles. Environment Details: Team ID: 3K7UP6P2LQ Bundle ID: com.Faycel.DrawCraft Xcode Version: 16.2 macOS Version: macOS Sequoia 15.2 Device: Simulator (iPhone 16 Pro) My Questions: Has anyone experienced similar issues where the team name in Xcode does not include the Team ID? Is this a known bug or a configuration issue? How can I ensure that my Apple Development Certificate is generated and associated with my personal Apple ID rather than my MacBook’s name? What steps can be taken to resolve the provisioning profile errors and restore the proper trust settings for the certificate? I appreciate any guidance or suggestions you might have. Thanks in advance for your help! Best regards, Faycel
2
0
123
2w