Search results for

“translate scheme”

6,658 results found

Post

Replies

Boosts

Views

Activity

How I can localize an array ?
Hello, I am trying to localize my app in other languages. Most of the text are automatically extracted by Xcode when creating a string catalog and running my app. However I realized few texts aren't extracted, hence I find a solution for most of them by adding For example I have some declared variable as var title: String = Continue Hence for them to be trigger I changed the String by LocalizedStringResource which gives var title: LocalizedStringResource = Continue But I still have an issue with some variables declared as an array with this for example @State private var genderOptions = [Male, Female, Not Disclosed] I tried many things however I don't success to make these arrays to be translated as the word here Male, Female and Not Disclosed. I have more array like that in my code and I am trying to find a solution for them to be extracted and be able to be localized Few things I tried that doesn't worked @State private var genderOptions : LocalizedStringResource = [Male, Female, Not Disclosed] @St
2
0
154
Jun ’25
Reply to Technical Inquiry Regarding DriverKit USB Serial Communication Issues on iPadOS
One other suggestion on all this. If you're starting on macOS, the other approach here would be to actually start by using the IOUSBHost Framework (instead of a DEXT) to sort out the basic control/command process, then porting that code into a DEXT. The framework says it: Create host-mode user space drivers for USB devices. ...but that's a very wordy way of saying lets an app directly talk to USB devices. The IOUSB Framework has the same API structure as USBDriverKit and IOKit, so it's relatively straightforward to translate the framework code you write into a DEXT. However, using the framework means: You're code is running in a standard app which you can directly debug. This also removes all DEXT loading issues/friction. Some of the code you'll be writing is code you'll end up writing anyway. For example, the IOKit code used to find the USB device you want to work with is exactly the same code you'd using on iPadOS to find and open your own user client. And, just like I discussed earlier, this code
Topic: App & System Services SubTopic: Drivers Tags:
Jun ’25
Reply to PKPassKitErrorDomain Code 2
I tried to make a new post but the forum doesn't allow it. let's try here..... I'm working on adding a card to Apple Wallet using push provisioning and facing a challenge during the final step. Here’s the overall flow I’m following: I initialize PKAddPaymentPassViewController using a properly configured PKAddPaymentPassRequestConfiguration, including properties such as: encryption scheme payment network cardholder name localized description primary account suffix style I receive the required input parameters and pass them through a service, which returns three base64-encoded strings: activation data, ephemeral public key, and encrypted data. I decode these strings into Data objects and use them to populate a PKAddPaymentPassRequest, then call the handler like this: swift let request = PKAddPaymentPassRequest() request.activationData = ... request.ephemeralPublicKey = ... request.encryptedPassData = ... handler(request) However, instead of completing the process, the user is presented with a message s
Jun ’25
openURL:options:completionHandler: Not Opening tel:// Link on iPad with Cellular Data
We are using openURL:options:completionHandler: to open a tel:// number in the dialer to place a call. This works on iPhones and WiFi-only iPads (tested with a iPad Mini 6th Gen), but it is failing to open on an iPad 8th Gen (WiFi + Cellular) running iPadOS 18.5 being used by a customer. Prior to updating the iPad to iPadOS 18, the call worked on iPadOS 15.2 and opened the call in FaceTime as expected. Despite not opening the dialer in iPadOS 18, the completionHandler returns the success parameter as true. canOpenUrl also returns true. We created a small test application that reproduces the issue using the code snippet below in a new application, with the tel schema added to the info.plist Queried URL Schemes. We are currently using Xcode 16.3. Test Steps: Create a new blank application and replace ContentView.swift with the code snippet below Run the test app on a physical iPad 8th Gen (WiFi + Cellular) Tap the place a test call button Expected Results: The user is prompted to call the number and is
0
0
180
Jun ’25
Cannot get Instruments to profile my apps
Hi, I need help to get Instruments running to profile my application. I tried to profile my main app (Qt-5.15-Framework, c++, Intel-arch only) from Xcode. My app starts and Instruments runs time profiler or Leaks for about 15 seconds and the quits. No crash, no message nothing. This has been happening for a while on my Mac Studio M1 Max running macOS 14.7.6 and Xcode 15.4 IDE with a toolchain from Xcode 14.3 for the qmake (qt) project. However, this also happens if i set up a new vanilla Swift UI project from scratch wihtout any Qt stuff. In addition to the Mac Studio I also have Mac Book Pro M4 running macOS 15.5 and Xcode 16.4. On that machine I get the same results, no matter if I try Instruments on my qt project or a vanilla SwiftUI project. Also it does not make a difference if I change the toolchain with: sudo xcode-select -s /Applications/Xcode_143.app or sudo xcode-select -s /Applications/Xcode_164.app. Same results in either case. I also tried switching to Debug build in the editing the scheme
4
0
386
Jun ’25
Reply to Duplicate apps launched when debugging in Xcode?
Confirmed on Xcode 16.4 (16F6). Bug symptoms are the same as previously mentioned: Xcode frequently launches duplicate processes when schema Run action is performed on a macOS command line tool executable that creates UI windows. It is a bug in Xcode due to following: The bug occurs when Debug executable is set under the Scheme -> Run -> Info tab. When Debug executable is unset, no duplicate processes are launched. No duplicate processes are launched when the executable is launched on terminal. Also confirmed that adding 350 ms delay in program main() is a workaround. For example, using SDL2 add SDL_Delay(350) at the top of the main() function. To Xcode team, let me know if you want a test app for this. Cheers.
May ’25
Workspace with multiple targets for same framework
Hi ! I'm currently stuck with an issue on Xcode, I'll try explain to the best I can :-) I have a workspace (that I need to keep that way, I can't split projects) that contains multiple projects. I have 2 frameworks : Core and Draw. Draw depends on Core. So far so good. I needed to create a test application that can be modular and link my framewok, but also other drawing frameworks. To that extend, I created a CardLIbrary framewok, and a CardAdapter framewok, and I linked them into the test application. Test App └── DrawCardAdapter │ └── CardAdapter │ └── CardLibrary │ └── Core │ └── TCA (SPM) │ └── Draw │ └── Core Here, all dependencies are local ones if not stated otherwise (for the SPM). CardLibrary is a framework that generates only UI (linked to Core for logging purposes, nothing fancy). I also added TCA which is a SPM dependency, it may generate some issues after. CardAdapter is an abstraction for CardLibrary. Basically, it acts as an interface between CardLibrary and Test Application. DrawCardAdapter is
1
0
189
May ’25
Reply to CIContext sporadically crashes on macOS 15.4/15.5, iOS 18.4/18.5
Hi, I’ve encountered the exact same crash in my project when calling: CIContext().render(...) Just like the original post, I'm getting: Thread 4: EXC_BAD_ACCESS (code=1, address=...) What I’ve noticed is that the crash completely disappears when I uncheck Debug Executable in the scheme settings. With it disabled, the app runs smoothly without any EXC_BAD_ACCESS at that line. This suggests the crash might be related to debug-mode memory checks or internal CIContext rendering behavior. I’ve double-checked that the CVPixelBuffer, CIImage, and CGColorSpace are all valid before rendering. Would appreciate any insights or explanations from Apple engineers or anyone who has managed to resolve this. Thank you!
Topic: UI Frameworks SubTopic: General Tags:
May ’25
Objective-C headers build fine with swift but not with Xcode
On my M4 Mac running macOS 15.5 using Xcode 16.4 & Xcode CLT 16.4, Swift code in my Swift Package Manager 5.9 project (https://github.com/mas-cli/mas) builds fine against some included Objective-C headers via the following command line: swift build -c release But cannot find modules for the included Objective-C headers when building inside Xcode 16.4 or with the following command line on the same Mac: xcodebuild -scheme mas -configuration Release -destination platform=macOS,arch=arm64,variant=macos The error is: Sources/mas/AppStore/AppleAccount.swift:9:16: error: no such module 'StoreFoundation' How can I get Xcode / xcodebuild to work? Note that the project is normally built by running: Scripts/build which runs: swift build -c release after running the following script, which must be run before any build (swift, Xcode, or xcodebuild) because it generates a necessary file (Sources/mas/Package.swift): Scripts/generate_package_swift I've tried moving the Objective-C headers into include subfolders
0
0
143
May ’25
WatchOS app - installation not working
Hi everyone, I’ve been trying since yesterday to set up an Apple Watch app alongside my iOS app, but it’s not working at all. I created the app by adding a new target, selected watchOS > App, and linked it to my iOS project. When I run the Apple Watch scheme directly, the app works, but if I try to install it on my Apple Watch via the iOS app, it doesn’t work. Every time I tap install, I get a message saying that the installation failed. While reading the documentation, they mention an Info.plist file that is supposed to be generated with the watchOS app, but when I check, I don’t see any .plist file. Is that normal? Thanks for your help.
0
0
67
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Bingo. Xcode Version 16.3 (16E140) New iOS App project, iOS 18.4, edit Scheme, switch on: address sanitizer, detect use of stack after return, undefined behavior sanitizer, main thread checker thread performance checker malloc scribble zombie objects api validation And you get (iPhone 13 iOS 18.4 simulator): `libclang_rt.asan_iossim_dynamic.dylib`__sanitizer::MemoryMappingLayout::Next: 0x1100d9e50 <+0>: cmpl $-0x1, 0x8(%rdi) 0x1100d9e54 <+4>: jl 0x1100d9e7b ; <+43> 0x1100d9e56 <+6>: pushq %rbp 0x1100d9e57 <+7>: movq %rsp, %rbp 0x1100d9e5a <+10>: pushq %r15 0x1100d9e5c <+12>: pushq %r14 ... 0x1100d9f54 <+260>: movl 0x4(%r13), %eax 0x1100d9f58 <+264>: addq %rax, %r13 -> 0x1100d9f5b <+267>: movl (%r13), %eax 0x1100d9f5f <+271>: cmpl $0xc, %eax 0x1100d9f62 <+274>: jne 0x1100d9f50 ; <+256> ` If you modify the App to run on iOS 18.0 (minimum deployment), add a simulator for iOS 18.0, you will find it runs fine on 18.0, with al
May ’25
iOS Camera access issues in Developer mode on real device - PermissionStatus.permanentlyDenied
Xcode Version 16.3 (16E140) App developed in Flutter Flutter 3.29.3 Test iPhone device: iPhone 16 Pro running iOS 18.5 I have an app that requires Camera access. This used to work before with iOS 18.4.x. I have dumbed down my app to just get Camera permission. Even then it fails flutter: Camera permission: PermissionStatus.denied flutter: Photos permission: PermissionStatus.denied flutter: Microphone permission: PermissionStatus.denied flutter: --- End Debug Info --- flutter: Loaded translations from asset for en_US container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_b
1
0
174
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Thanks Quinn, I'm sure a new and clean empty project runs, but this is a (big) existing project, objective-c, no storyboard but XIBs, that has run fine before 18.4, for years. As the crash happens before my code is even entered I don't even know where to start! Does this Sanitizer message mean anything to you? What is the problem with MemoryMappingLayout? libclang_rt.asan_iossim_dynamic.dylib__sanitizer::MemoryMappingLayout::Next: 0x10f2dae50 <+0>: cmpl $-0x1, 0x8(%rdi)` With the sanitizers switched off in the Run Scheme the app runs fine in the Simulator, but I have a user that experiences an actual crash on device. That crash is different from what I experience: the app crashes on simulator before entering my code, after displaying the splash screen, while the user has an app that does startup, and can be used for a few seconds, but crashes on a certain input. As is, I cannot even establish if these crashes are related. In the App Analytics in AppstoreConnect I see no increase in the number o
May ’25
Reply to Mac Catalyst App can't launch, reason: Library not loaded: /usr/lib/libc++.1.dylib
Thanks for the full crash report. That confirms that the program is being run under Rosetta: Code Type: X86-64 (Translated) I played around with this here in my office. Consider: Using Xcode 16.3, I created a new project from the iOS > App template. I removed the Mac > Designed for iPad destination and replaced it with the Mac > Mac Catalyst one. I changed the deployment target to iOS 18.0 (hence macOS 15.0). I set the run destination to Any Mac (Mac Catalyst, arm64, x86_64). I built the app. And copied the app over to a macOS 15.3.2 VM [1]. I launched it from the Finder. It launched just fine. I quit it. In Finder > File > Get Info, I enabled Open Using Rosetta. I launched the app. The system offered to install Rosetta. I ran through that process. I launched the app again. It crashed at launch, and the resulting crash report is very similar to yours. I’ve included my crash report below, just for your reference. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Appl
Topic: App & System Services SubTopic: Core OS Tags:
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Have you tried reproducing this with a small test project? I just tried this here in my office and didn’t have a problem. Specifically: Using Xcode 16.3 on macOS 15.4, I created a new app from the iOS > App template. I ran it on the iPhone 16 simulator, simulating iOS 18.4. It launched successfully. In the scheme editor I enabled Address Sanitizer. I ran it again. It launched successfully. In the scheme editor I disabled Address Sanitizer and enable Thread Sanitizer. It launched successfully. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
May ’25
How I can localize an array ?
Hello, I am trying to localize my app in other languages. Most of the text are automatically extracted by Xcode when creating a string catalog and running my app. However I realized few texts aren't extracted, hence I find a solution for most of them by adding For example I have some declared variable as var title: String = Continue Hence for them to be trigger I changed the String by LocalizedStringResource which gives var title: LocalizedStringResource = Continue But I still have an issue with some variables declared as an array with this for example @State private var genderOptions = [Male, Female, Not Disclosed] I tried many things however I don't success to make these arrays to be translated as the word here Male, Female and Not Disclosed. I have more array like that in my code and I am trying to find a solution for them to be extracted and be able to be localized Few things I tried that doesn't worked @State private var genderOptions : LocalizedStringResource = [Male, Female, Not Disclosed] @St
Replies
2
Boosts
0
Views
154
Activity
Jun ’25
Reply to Technical Inquiry Regarding DriverKit USB Serial Communication Issues on iPadOS
One other suggestion on all this. If you're starting on macOS, the other approach here would be to actually start by using the IOUSBHost Framework (instead of a DEXT) to sort out the basic control/command process, then porting that code into a DEXT. The framework says it: Create host-mode user space drivers for USB devices. ...but that's a very wordy way of saying lets an app directly talk to USB devices. The IOUSB Framework has the same API structure as USBDriverKit and IOKit, so it's relatively straightforward to translate the framework code you write into a DEXT. However, using the framework means: You're code is running in a standard app which you can directly debug. This also removes all DEXT loading issues/friction. Some of the code you'll be writing is code you'll end up writing anyway. For example, the IOKit code used to find the USB device you want to work with is exactly the same code you'd using on iPadOS to find and open your own user client. And, just like I discussed earlier, this code
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reply to PKPassKitErrorDomain Code 2
I tried to make a new post but the forum doesn't allow it. let's try here..... I'm working on adding a card to Apple Wallet using push provisioning and facing a challenge during the final step. Here’s the overall flow I’m following: I initialize PKAddPaymentPassViewController using a properly configured PKAddPaymentPassRequestConfiguration, including properties such as: encryption scheme payment network cardholder name localized description primary account suffix style I receive the required input parameters and pass them through a service, which returns three base64-encoded strings: activation data, ephemeral public key, and encrypted data. I decode these strings into Data objects and use them to populate a PKAddPaymentPassRequest, then call the handler like this: swift let request = PKAddPaymentPassRequest() request.activationData = ... request.ephemeralPublicKey = ... request.encryptedPassData = ... handler(request) However, instead of completing the process, the user is presented with a message s
Replies
Boosts
Views
Activity
Jun ’25
openURL:options:completionHandler: Not Opening tel:// Link on iPad with Cellular Data
We are using openURL:options:completionHandler: to open a tel:// number in the dialer to place a call. This works on iPhones and WiFi-only iPads (tested with a iPad Mini 6th Gen), but it is failing to open on an iPad 8th Gen (WiFi + Cellular) running iPadOS 18.5 being used by a customer. Prior to updating the iPad to iPadOS 18, the call worked on iPadOS 15.2 and opened the call in FaceTime as expected. Despite not opening the dialer in iPadOS 18, the completionHandler returns the success parameter as true. canOpenUrl also returns true. We created a small test application that reproduces the issue using the code snippet below in a new application, with the tel schema added to the info.plist Queried URL Schemes. We are currently using Xcode 16.3. Test Steps: Create a new blank application and replace ContentView.swift with the code snippet below Run the test app on a physical iPad 8th Gen (WiFi + Cellular) Tap the place a test call button Expected Results: The user is prompted to call the number and is
Replies
0
Boosts
0
Views
180
Activity
Jun ’25
Cannot get Instruments to profile my apps
Hi, I need help to get Instruments running to profile my application. I tried to profile my main app (Qt-5.15-Framework, c++, Intel-arch only) from Xcode. My app starts and Instruments runs time profiler or Leaks for about 15 seconds and the quits. No crash, no message nothing. This has been happening for a while on my Mac Studio M1 Max running macOS 14.7.6 and Xcode 15.4 IDE with a toolchain from Xcode 14.3 for the qmake (qt) project. However, this also happens if i set up a new vanilla Swift UI project from scratch wihtout any Qt stuff. In addition to the Mac Studio I also have Mac Book Pro M4 running macOS 15.5 and Xcode 16.4. On that machine I get the same results, no matter if I try Instruments on my qt project or a vanilla SwiftUI project. Also it does not make a difference if I change the toolchain with: sudo xcode-select -s /Applications/Xcode_143.app or sudo xcode-select -s /Applications/Xcode_164.app. Same results in either case. I also tried switching to Debug build in the editing the scheme
Replies
4
Boosts
0
Views
386
Activity
Jun ’25
Reply to Duplicate apps launched when debugging in Xcode?
Confirmed on Xcode 16.4 (16F6). Bug symptoms are the same as previously mentioned: Xcode frequently launches duplicate processes when schema Run action is performed on a macOS command line tool executable that creates UI windows. It is a bug in Xcode due to following: The bug occurs when Debug executable is set under the Scheme -> Run -> Info tab. When Debug executable is unset, no duplicate processes are launched. No duplicate processes are launched when the executable is launched on terminal. Also confirmed that adding 350 ms delay in program main() is a workaround. For example, using SDL2 add SDL_Delay(350) at the top of the main() function. To Xcode team, let me know if you want a test app for this. Cheers.
Replies
Boosts
Views
Activity
May ’25
Workspace with multiple targets for same framework
Hi ! I'm currently stuck with an issue on Xcode, I'll try explain to the best I can :-) I have a workspace (that I need to keep that way, I can't split projects) that contains multiple projects. I have 2 frameworks : Core and Draw. Draw depends on Core. So far so good. I needed to create a test application that can be modular and link my framewok, but also other drawing frameworks. To that extend, I created a CardLIbrary framewok, and a CardAdapter framewok, and I linked them into the test application. Test App └── DrawCardAdapter │ └── CardAdapter │ └── CardLibrary │ └── Core │ └── TCA (SPM) │ └── Draw │ └── Core Here, all dependencies are local ones if not stated otherwise (for the SPM). CardLibrary is a framework that generates only UI (linked to Core for logging purposes, nothing fancy). I also added TCA which is a SPM dependency, it may generate some issues after. CardAdapter is an abstraction for CardLibrary. Basically, it acts as an interface between CardLibrary and Test Application. DrawCardAdapter is
Replies
1
Boosts
0
Views
189
Activity
May ’25
Reply to CIContext sporadically crashes on macOS 15.4/15.5, iOS 18.4/18.5
Hi, I’ve encountered the exact same crash in my project when calling: CIContext().render(...) Just like the original post, I'm getting: Thread 4: EXC_BAD_ACCESS (code=1, address=...) What I’ve noticed is that the crash completely disappears when I uncheck Debug Executable in the scheme settings. With it disabled, the app runs smoothly without any EXC_BAD_ACCESS at that line. This suggests the crash might be related to debug-mode memory checks or internal CIContext rendering behavior. I’ve double-checked that the CVPixelBuffer, CIImage, and CGColorSpace are all valid before rendering. Would appreciate any insights or explanations from Apple engineers or anyone who has managed to resolve this. Thank you!
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’25
Objective-C headers build fine with swift but not with Xcode
On my M4 Mac running macOS 15.5 using Xcode 16.4 & Xcode CLT 16.4, Swift code in my Swift Package Manager 5.9 project (https://github.com/mas-cli/mas) builds fine against some included Objective-C headers via the following command line: swift build -c release But cannot find modules for the included Objective-C headers when building inside Xcode 16.4 or with the following command line on the same Mac: xcodebuild -scheme mas -configuration Release -destination platform=macOS,arch=arm64,variant=macos The error is: Sources/mas/AppStore/AppleAccount.swift:9:16: error: no such module 'StoreFoundation' How can I get Xcode / xcodebuild to work? Note that the project is normally built by running: Scripts/build which runs: swift build -c release after running the following script, which must be run before any build (swift, Xcode, or xcodebuild) because it generates a necessary file (Sources/mas/Package.swift): Scripts/generate_package_swift I've tried moving the Objective-C headers into include subfolders
Replies
0
Boosts
0
Views
143
Activity
May ’25
WatchOS app - installation not working
Hi everyone, I’ve been trying since yesterday to set up an Apple Watch app alongside my iOS app, but it’s not working at all. I created the app by adding a new target, selected watchOS > App, and linked it to my iOS project. When I run the Apple Watch scheme directly, the app works, but if I try to install it on my Apple Watch via the iOS app, it doesn’t work. Every time I tap install, I get a message saying that the installation failed. While reading the documentation, they mention an Info.plist file that is supposed to be generated with the watchOS app, but when I check, I don’t see any .plist file. Is that normal? Thanks for your help.
Replies
0
Boosts
0
Views
67
Activity
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Bingo. Xcode Version 16.3 (16E140) New iOS App project, iOS 18.4, edit Scheme, switch on: address sanitizer, detect use of stack after return, undefined behavior sanitizer, main thread checker thread performance checker malloc scribble zombie objects api validation And you get (iPhone 13 iOS 18.4 simulator): `libclang_rt.asan_iossim_dynamic.dylib`__sanitizer::MemoryMappingLayout::Next: 0x1100d9e50 <+0>: cmpl $-0x1, 0x8(%rdi) 0x1100d9e54 <+4>: jl 0x1100d9e7b ; <+43> 0x1100d9e56 <+6>: pushq %rbp 0x1100d9e57 <+7>: movq %rsp, %rbp 0x1100d9e5a <+10>: pushq %r15 0x1100d9e5c <+12>: pushq %r14 ... 0x1100d9f54 <+260>: movl 0x4(%r13), %eax 0x1100d9f58 <+264>: addq %rax, %r13 -> 0x1100d9f5b <+267>: movl (%r13), %eax 0x1100d9f5f <+271>: cmpl $0xc, %eax 0x1100d9f62 <+274>: jne 0x1100d9f50 ; <+256> ` If you modify the App to run on iOS 18.0 (minimum deployment), add a simulator for iOS 18.0, you will find it runs fine on 18.0, with al
Replies
Boosts
Views
Activity
May ’25
iOS Camera access issues in Developer mode on real device - PermissionStatus.permanentlyDenied
Xcode Version 16.3 (16E140) App developed in Flutter Flutter 3.29.3 Test iPhone device: iPhone 16 Pro running iOS 18.5 I have an app that requires Camera access. This used to work before with iOS 18.4.x. I have dumbed down my app to just get Camera permission. Even then it fails flutter: Camera permission: PermissionStatus.denied flutter: Photos permission: PermissionStatus.denied flutter: Microphone permission: PermissionStatus.denied flutter: --- End Debug Info --- flutter: Loaded translations from asset for en_US container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled container_create_or_lookup_app_group_path_b
Replies
1
Boosts
0
Views
174
Activity
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Thanks Quinn, I'm sure a new and clean empty project runs, but this is a (big) existing project, objective-c, no storyboard but XIBs, that has run fine before 18.4, for years. As the crash happens before my code is even entered I don't even know where to start! Does this Sanitizer message mean anything to you? What is the problem with MemoryMappingLayout? libclang_rt.asan_iossim_dynamic.dylib__sanitizer::MemoryMappingLayout::Next: 0x10f2dae50 <+0>: cmpl $-0x1, 0x8(%rdi)` With the sanitizers switched off in the Run Scheme the app runs fine in the Simulator, but I have a user that experiences an actual crash on device. That crash is different from what I experience: the app crashes on simulator before entering my code, after displaying the splash screen, while the user has an app that does startup, and can be used for a few seconds, but crashes on a certain input. As is, I cannot even establish if these crashes are related. In the App Analytics in AppstoreConnect I see no increase in the number o
Replies
Boosts
Views
Activity
May ’25
Reply to Mac Catalyst App can't launch, reason: Library not loaded: /usr/lib/libc++.1.dylib
Thanks for the full crash report. That confirms that the program is being run under Rosetta: Code Type: X86-64 (Translated) I played around with this here in my office. Consider: Using Xcode 16.3, I created a new project from the iOS > App template. I removed the Mac > Designed for iPad destination and replaced it with the Mac > Mac Catalyst one. I changed the deployment target to iOS 18.0 (hence macOS 15.0). I set the run destination to Any Mac (Mac Catalyst, arm64, x86_64). I built the app. And copied the app over to a macOS 15.3.2 VM [1]. I launched it from the Finder. It launched just fine. I quit it. In Finder > File > Get Info, I enabled Open Using Rosetta. I launched the app. The system offered to install Rosetta. I ran through that process. I launched the app again. It crashed at launch, and the resulting crash report is very similar to yours. I’ve included my crash report below, just for your reference. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Appl
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
May ’25
Reply to EXC_BAD_ACCESS if Address or Thread Sanitizer is enabled
Have you tried reproducing this with a small test project? I just tried this here in my office and didn’t have a problem. Specifically: Using Xcode 16.3 on macOS 15.4, I created a new app from the iOS > App template. I ran it on the iPhone 16 simulator, simulating iOS 18.4. It launched successfully. In the scheme editor I enabled Address Sanitizer. I ran it again. It launched successfully. In the scheme editor I disabled Address Sanitizer and enable Thread Sanitizer. It launched successfully. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
May ’25