My Project crash when use Xcode16 beta 3 while Xcode15 is fine, please help!
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Posts under Xcode tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
HI, I have a app with Swift Programming language. It is built successfully on my Monterey Intel by using Xcode 14.
I am trying to built same app on Sonoma Silicon arm64 by using Xcode 15.4. But app is failing to build with below errors. Can anyone suggest reason for this?
Copy /Users/testuser/git/agent/out/Darwin/Release/TESTFileProvider.appex/Contents/Resources/swift-nio__NIOFileSystem.bundle /Users/testuser/git/agent/out/Darwin/Release/swift-nio__NIOFileSystem.bundle (in target 'TESTFileProvider' from project 'TEST')
cd /Users/testuser/git/agent/dgagent/agent/macosx/dgc/TEST
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/testuser/git/agent/out/Darwin/Release/swift-nio__NIOFileSystem.bundle /Users/testuser/git/agent/out/Darwin/Release/TESTFileProvider.appex/Contents/Resources
error: /Users/testuser/git/agent/out/Darwin/Release/swift-nio__NIOFileSystem.bundle: No such file or directory (in target 'TESTFileProvider' from project 'TEST')
Copy /Users/testuser/git/agent/out/Darwin/Release/TESTFileProvider.appex/Contents/Resources/swift-nio_NIOPosix.bundle /Users/testuser/git/agent/out/Darwin/Release/swift-nio_NIOPosix.bundle (in target 'TESTFileProvider' from project 'TEST')
cd /Users/testuser/git/agent/dgagent/agent/macosx/dgc/TEST
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/testuser/git/agent/out/Darwin/Release/swift-nio_NIOPosix.bundle /Users/testuser/git/agent/out/Darwin/Release/TESTFileProvider.appex/Contents/Resources
error: /Users/testuser/git/agent/out/Darwin/Release/swift-nio_NIOPosix.bundle: No such file or directory (in target 'TESTFileProvider' from project 'TEST')
Hello
I´ve build a game in Unreal and try to get it for sale to a webshop (not Apple Store). For that, the game needs to be notarized etc. And to sell the outside of Apple Store you need to log in manually with Developer ID application in Xcode.
Any idea why I get this error message: "Hardened Runtime is Not Enabled. "XXXXXXXX.app" must be rebuilt with support for the Hardened Runtime. Enable the Hardened Runtime capability in the project editor, test your app, rebuild your archive, and upload again.
Any help appreciated, I´ve struggled with this for a week.
All the best,
Ramili
Since I updated to Xcode 15.3, my archives have an empty dSYMs folder. I have not changed any project settings since Xcode 14.
My build settings have:
Debug Information Format: DWARF with dSYM File
Generate Debug Symbols: Yes
From my archives, if I navigate to the .xcarchive, Show Package Contents, there is a dSYMs folder. For all my archives built in Xcode 15, this folder is empty. For previous archives (Xcode 14), this folder contains a .app.dSYM file.
When I distribute my app via App Store Connect and receive crash reports from TestFlight, these are symbolicated.
So I'm confused why I don't see a local .dSYM file. Can you explain this? What do I need to change to generate this? (And does it matter if I'm getting symbolicated crash reports??)
On any project that I open or create from scratch (SwiftUI) the "prebuild" that gets kicked off never finishes which results in the fact that I can not build the project.
If I use XCode 16 beta 2 everything works fine.
We use XCode 15.2 to build our application, but we found that the app crashes on iOS 12.1.1, while it works without crashing on iOS 12.5.7. We discovered that the crash is related to ImageLoaderMachO::doModInitFunctions. We're not sure what is causing this.
I have a watchOS app written in C++, Swift and SwiftUI. This app is meant only for 64-bit architecture. I know Apple uses the arm architecture, so I thought arm64 will be the arch of latest AppleWatches.
I tested my code in x64 simulator (Intel Mac) and arm64 simulator (silicon Mac) - no trouble. Next is to test on a device - AppleWatch Series 9, model: A2984. I set the arch to arm64 and my application failed to build, with Xcode showing a popup about arch mismatch... which is due to the app's arch begin different from device's arch. When I change Xcode arch setting to arm64_32, then I don't get this popup, but my builds fail. When I read about arm64_32, I realised that this is a version of arm64 with 32 bit pointers... not the arm64 with 64 bit pointers.
Looking at the specification of AppleWatch Series 9, Apple has confirmed that it has 64 bit CPU, but the instruction set is unknown. This wiki page about different AppleWatch CPUs is marked TBC for AppleWatch Series 9. From Xcode, I got to know that this unconfirmed arch is arm64_32. This completely breaks my code. Are there any 64-bit watches with 64-bit pointer sizes? What is Apple's future in this area? Do they plan to release AppleWatches that support 64-bit pointers or it's always going to be 32?
Xcode > Target > Signing & Capabilities
Automaticaly manage signing
Mac OS Signing Certificate: Development
--> Provisioning Profile None Required
General Identity
App Category Productivity
Transporter
Asset validation failed (90242)
--> "Cannot be used with TestFlight because the bundle at “LargeNumberCalculator.app” is missing a provisioning profile.
Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight." (90889).
What is wrong: "Provisioning Profile None Required" vs "missing a provisioning profile" ?
I received an app from 3rd party and need to sign it with my cert, but after following the work flow I get errors in iResign.
Create a Distribution Certificate
Create an Apple Developer Application Identifier
Create and Install a Push SSL Certificate
Create App Distribution Certificate (1 for all Ramco Apps)
Create an Apple Developer Provisioning Profile
Sign the App with iResign
Upload to Workspace One environment
I get this error when I run iResign;
/var/folders/qd/z7m3dzs52rddmlvcpm_ghyl00000gn/T/com.appulize.iresign/Payload/RamcoEFBiOS.app: replacing existing signature
Warning: unable to build chain to self-signed root for signer "iPhone Distribution: PHI, INC."
/var/folders/qd/z7m3dzs52rddmlvcpm_ghyl00000gn/T/com.appulize.iresign/Payload/RamcoEFBiOS.app: errSecInternalComponent
/var/folders/qd/z7m3dzs52rddmlvcpm_ghyl00000gn/T/com.appulize.iresign/Payload/RamcoEFBiOS.app: invalid Info.plist (plist or signature have been modified)
In architecture: arm64
I've tried to find answers on these forms but could not find anything to help me. If anyone has some insight on this please let me know.
While coding, Xcode Version 15.4 (15F31d) is consistently breaking builds by changing both struct and class declarations in areas of code other than where I'm currently editing. Suddenly, code that was compiling a minute ago breaks with multiple "Type 'Xxxx' has no member 'getYyyy'.
For example, I'm writing code in a subclass, and suddenly calls to the superclass's methods are unrecognized by the compiler (e.g., "Type 'MeetInfoSheetReader' has no member 'getDateValue'").
Command-click on the method name takes me to the method in the superclass, and nothing is wrong at that point: I have the correct method signature, yet the code doesn't compile. I scroll up to the class declaration only to find that Xcode has changed "class" to "enum".
This can happen regardless of whether the superclass or the reference struct is in the same or a different file.
Also, this happens frequently, and it's not because I have bouts of narcolepsy and changed class or struct to enum while out. My dog doesn't even get near the laptop while I'm away from it, and I don't have a cat who types let alone a cat.
Because I cannot associate this aggravating Xcode behavior with any particular thing I'm doing (e.g., name refactoring a variable or class name, deleting commented sections of exploratory code, or anything else) I'm sure that if I file a bug with the Feedback Assistant (a really ****** bug reporting system), it will be marked closed without the slightest bit of interest in exploring the problem.
Hopefully someone else has seen this behavior and has a solution. Because it's really counterproductive.
Ever since Xcode 15 and iOS 17 came out development has quite often been a nightmare of waiting and waiting -Xcode displaying endless circles saying preparing the device, connecting to the device, installing the device.
But recently to add to this, installation and launching is just taking really forever.
I'm currently running Xcode 15.1 and various versions of iOS 17 (I have several phones) and installing the app from Xcode takes about 7 - 10 minutes (compared to the same app installing in seconds with Xcode 14 for example).
Then once its finally installed, it then takes further minutes to launch, Xcode often actually displays a dialog saying its taking longer than expected to launch the app, adding the footnote "LLDB is likely reading from device memory to resolve symbols."
What could be reasons, and solutions, for the excruciatingly slow installation time, and launch time?
I really need to find a solution to this please - making a code change tweak, running, making another, running, making another, running, just isn't possible given the length of time it takes to install and launch each time.
The iPhone is connected via physical cable to the Mac, and the Mac and iPhone are both on the same Wifi network.
Xcode 15.1
M1 Macbook Pro
Sonomo 14.0
iOS 17.2
Hi,
I have a 2017 iMac that works perfectly, and I am trying to use it to make applications using Swift with Xcode. However, I cannot use Xcode because the last update my iMac supported was Ventura, and now, Xcode requires macOS Sonoma. Is there any way to get around this?
Thanks
I am a developer working on macOS Sonoma version 14.5 using a MacBook Pro with an M3 Pro chip. I have been trying to utilize PacketLogger, included with Xcode 15.4 extensions, to monitor Bluetooth traffic between my MacBook and my Sony WH-1000XM4 headphones.
Issue Description:
Despite my device being correctly paired and connected, PacketLogger does not display any Bluetooth packet data. The expected Bluetooth packets are not shown in the PacketLogger interface, even when no filters are applied, and PacketLogger settings are configured to capture all traffic.
Troubleshooting Steps Taken:
• I have ensured all PacketLogger filters are deactivated to capture all types of Bluetooth traffic.
• I have started the PacketLogger before connecting my Bluetooth devices to capture the initial exchanges.
• Reinstallation of PacketLogger and verification of Bluetooth module functionality have been performed, with no resolution to the issue.
Request for Assistance:
Could you provide guidance or troubleshooting steps that might address this issue? Are there known compatibility issues with PacketLogger on macOS Sonoma or with the MacBook Pro M3 Pro model that might affect its functionality? Any specific settings or configurations that I might be overlooking would also be greatly appreciated.
I can provide additional information, including screenshots of my PacketLogger settings and logs, upon request. Your assistance in resolving this issue would be invaluable.
Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.)
Here is what the detailed error message shows:
The developer disk image could not be mounted on this device.
Domain: com.apple.dt.CoreDeviceError
Code: 12040
Failure Reason: Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.)
User Info: {
DDIPath = "/Library/Developer/DeveloperDiskImages/iOS_DDI.dmg";
DVTErrorCreationDateKey = "2024-07-12 19:06:25 +0000";
DeviceIdentifier = "94430B68-BA12-4F63-9EE5-48EE865738D6";
IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker;
NSURL = "file:///Library/Developer/DeveloperDiskImages/iOS_DDI.dmg";
Options = {
MountedBundlePath = "file:///private/var/tmp/CoreDevice_DDI_Staging_501/94430B68-BA12-4F63-9EE5-48EE865738D6/";
UseCredentials = 0;
};
"com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI;
}
Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.)
Domain: com.apple.mobiledevice
Code: -402652923
User Info: {
FunctionName = AMDeviceRemoteMountPersonalizedBundle;
LineNumber = 2135;
}
AMAuthInstallRequestSendSync failed: 3194 (kAMAuthInstallTATSUDeclinedAuthorization)
Domain: com.apple.mobiledevice
Code: -402652923
User Info: {
FunctionName = "-[PersonalizedImage mountImage:]";
LineNumber = 2032;
}
Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
"device_identifier" = "00008027-000164500AE2402E";
"device_isCoreDevice" = 1;
"device_model" = "iPad8,12";
"device_osBuild" = "18.0 (22A5307f)";
"device_platform" = "com.apple.platform.iphoneos";
"device_thinningType" = "iPad8,12";
"dvt_coredevice_version" = "397.3.5.2";
"dvt_coresimulator_version" = 980;
"dvt_mobiledevice_version" = "1757.0.0.101.1";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 1;
"launchSession_targetArch" = arm64;
"operation_duration_ms" = 1332838;
"operation_errorCode" = "-402652923";
"operation_errorDomain" = "com.apple.dt.CoreDeviceError.12040.com.apple.mobiledevice";
"operation_errorWorker" = IDEInstallCoreDeviceWorker;
"operation_name" = IDERunOperationWorkerGroup;
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 3;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphoneos";
"param_diag_113575882_enable" = 0;
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 1;
"param_diag_gpu_frameCapture_enable" = 0;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_queueDebugging_enable" = 1;
"param_diag_runtimeProfile_generate" = 0;
"param_diag_sanitizer_asan_enable" = 0;
"param_diag_sanitizer_tsan_enable" = 0;
"param_diag_sanitizer_tsan_stopOnIssue" = 0;
"param_diag_sanitizer_ubsan_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 1;
"param_install_style" = 2;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 99;
"param_launcher_substyle" = 0;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_structuredConsoleMode" = 1;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphoneos18.0";
"sdk_osVersion" = "18.0";
"sdk_variant" = iphoneos;
}
System Information
macOS Version 14.5 (Build 23F79)
Xcode 16.0 (23037.4) (Build 16A5171r)
Timestamp: 2024-07-12T12:06:25-07:00
I’m writing UI tests for biometrics in iOS. For a failing case, I encounter an alert that needs to be dismissed by the user. How can I tap a button in this alert?
XCTest has the addUIInterruptionMonitor method (https://developer.apple.com/documentation/xctest/xctestcase/1496273-adduiinterruptionmonitor). Is this what I need? If so, what description should I use? Or do I need some other functionality?
For Touch ID, I can simply simulate a failure twice, and the alert will be dismissed. However, for Face ID and Optic ID, this approach is not suitable—the alert buttons need to be tapped. Additionally, there is an old method to handle the alert using the Springboard app (with the bundle ID “com.apple.springboard”). However, this only works for iOS and iPadOS, while VisionOS does not have this bundle ID.
I came across a useful repo on GitHub:
https://github.com/GianniCarlo/DirectoryWatcher/blob/master/Sources/DirectoryWatcher/DirectoryWatcher.swift
self.queue = DispatchQueue.global()
self.source = DispatchSource.makeFileSystemObjectSource(fileDescriptor: descriptor, eventMask: .write, queue: self.queue)
self.source?.setEventHandler {
[weak self] in
self?.directoryDidChange()
}
self.source?.setCancelHandler() {
close(descriptor)
}
self.source?.resume()
How do I translate this to OC version? I have an app that was written in OC and I plan to incorporate this directory watcher into the project.
I made a project with MacOS/Bundle/Objective-C. I added main.m as like:
#import <Foundation/Foundation.h>
int main (int argc, const char * argv[]) {
printf("Test\n");
}
Built it and the generated bundle. I open the bundle with Finder and located the binary in the MacOS directory within the bundle. The file command returned as like:
<path...>TestProject: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit bundle x86_64] [arm64:Mach-O 64-bit bundle arm64]
<path...>TestProject (for architecture x86_64):Mach-O 64-bit bundle x86_64
<path...>TestProject (for architecture arm64): Mach-O 64-bit bundle arm64
It apparently generated the Universal binary. Of course, no error were reported on building.
I tried to execute the binary with drag&drop the file into Terminal, but shell reported as like:
zsh: exec format error: <path..>TestProject
These are reproducing my trouble. My target project is so old but it can generate executable x86_64 only binary. I want to be universal binary. My Xcode is 15.4 on Sonoma.
It was fantastic news to hear, last year, that Xcode was getting a Vim mode. Apple's implementation of it was a great first step, but it was missing a bunch of key features. Most importantly the dot command (and by, extension, macros) and creating marks in files, which are functions that I use/rely on on a daily basis.
I thought I would finally be able to stop having to self-sign Xcode (which causes problems) in order to use XVim2 plugin, but no such luck.
Will these features get added in for Xcode 14 (they don't seem to be in the beta) or are they far out on the roadmap?
I am currently running my Flutter app using macOS 15 beta (I accidentally upgraded and now I can't opt-out) and Xcode 15 beta on my iPhone 11 running iOS 17.5. While the app launches, it gets stuck on a black screen and I encounter the following error in Xcode:
Thread 1: signal SIGABRT
(lldb) bt
• thread #1, stop reason = signal SIGABRT
▪ frame #0: 0x00000001ad9eecd8 dyld__abort_with_payload + 8
frame #1: 0x00000001ad9fa450 dyld_abort_with_payload_wrapper_internal + 104
frame #2: 0x00000001ad9fa484 dyld_abort_with_payload + 16
frame #3: 0x00000001ad987e00 dyld4::halt(char const*, dyld4::StructuredError const*) + 304
frame #4: 0x00000001ad99559c dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 4088
frame #5: 0x00000001ad9b9c48 dyld_start + 1724
Note: This app functions correctly when distributed through TestFlight.
here is my case:
i add the AppIntent to both your app and widget extension targets. the intent will run my app process when app is running.
it works perfectly on iOS 17. but iOS 18, my app process never called.
i download app's demo, https://developer.apple.com/documentation/widgetkit/emoji-rangers-supporting-live-activities-interactivity-and-animations
it looks like the same issue. it runs well because even it runs in the widget extension target, it still can present expected UI. but in real case, we need to run the app process to do some work. by debugging, i found the app process never called(set breakpoint).
i add openAppWhenRun, it works well on iOS 18. but it will open the app when the widget is running. it is not what i want.