Search results for

“Visual Studio Maui IOS”

109,079 results found

Post

Replies

Boosts

Views

Activity

Reply to How to store certificate to `com.apple.token` keychain access group.
Thanks for bringing this to the forums. The com.apple.token keychain access group, aka kSecAttrAccessGroupToken, isn’t a normal keychain access group. Rather, it’s a special group that holds all of the credentials that the system finds in CryptoTokenKit (CTK) tokens. Given that, you can’t add credentials to this group directly. It is possible to create a persistent CTK token, that is, one that’s not tied to smart card hardware. If you do that then the credentials published by that token will be available to all apps that are set up to use token-based credentials. It’s not clear whether this approach will work for your ultimate goal: [quote='819445021, h-noto, /thread/819445, /profile/h-noto'] so that Microsoft Edge for iOS … can … use it for client certificate authentication [/quote] My advice is that you first prototype this with an actual smart card [1]. If you can get that working, it’d be worth exploring the virtual token option. Finally, if you’re curious how an app can work with token-based cre
Topic: Privacy & Security SubTopic: General Tags:
1w
Reply to Background upload issue in WatchOS
[quote='819449021, Team Tank Wars, /thread/819449, /profile/Team+Tank+Wars'] the remaining uploads do not proceed in the background and appear to be suspended. [/quote] Suspended forever? Or just a delayed? If you leave the watch in that state for a day, does it eventually attempt these stalled uploads? For context, there are URLSession and watchOS aspects to this. On the URLSession front, the system is free to delay background session transfer until an opportune time. While I have a lot less experience with this on the watchOS side, on iOS this often means that the transfer is deferred until overnight, when the device has both Wi-Fi and mains power. So I’m curious if the same thing is happening on the watch. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Reply to Different transaction IDs for the same purchase between SKPaymentTransaction and receipt latest_receipt_info
Please submit a feedback assistant ticket (http://feedbackassistant.apple.com), and we can assist further. Please provide as much information as possible, ie a sysdiagnose, app apple ID, in-app apple IDs, sandbox account apple ID (if applicable), transactions IDs, steps to reproduce and other relevant details. File ticket under iOS & iPadOS, macOS, tvOS, watchOS, or visionOS and ensure you select “App Store” for the question “Which area are you seeing an issue with?” Categorize the type of feedback Please attach all available files needed to verify After submitting the feedback, please regularly check the ticket as we'll only communicate through it from then on. Once you open the Feedback Assistant Ticket report, please post the FB number here for reference. If you have any questions about filing a report, take a look at Bug Reporting: How and Why?
Topic: App & System Services SubTopic: StoreKit Tags:
1w
CXCallUpdate not working for outgoing calls
I try to update remoteHandle using CXCallUpdate for outgoing call, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). This problem actual only for outgoing calls, but for incoming calls update works fine. func startOutgoingCall(with callID: UUID, userID: String) { let handle = CXHandle(type: .generic, value: userID) let action = CXStartCallAction(call: callID, handle: handle) callController.requestTransaction(with: action) { [weak self] error in // ... } } func updateOutgoingCall(with callID: UUID, groupID: String) { let update = CXCallUpdate() update.remoteHandle = CXHandle(type: .generic, value: groupID) provider.reportCall(with: callID, updated: update) } I also tried phoneNumber type but it seems initial handle that I set to CXStartCallAction not possible to change (value or even type). I use this handle value to implement recall by tap on call in Recents tab of system address book. But since my calls can transform from p2p to group call, I need to update handle value or find som
3
0
410
1w
hapticpatternlibrary.plist error with Text entry fields in Simulator only
When I have a TextField or TextEditor, tapping into it produces these two console entries about 18 times each: CHHapticPattern.mm:487 +[CHHapticPattern patternForKey:error:]: Failed to read pattern library data: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}} <_UIKBFeedbackGenerator: 0x600003505290>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnd
4
0
721
1w
Instruments Malfunction
I’m reporting a severe reproducible issue in Instruments, specifically when using the SwiftUI instrument and opening Show Cause & Effect Graph. What happens: • Instruments becomes extremely laggy/unresponsive • The graph/detail area can turn solid magenta/pink • Memory usage rapidly increases (I observed around 18 GB, 25 GB, and up to 34 GB) • My Mac has crashed/restarted during this, or in other terms, had a kernel panic, where my Mac froze, and everything unresponsive. The Trackpad wouldn't even click. Important detail: • I could not find a generated kernel panic log after the crash/restart. Repro context: • SwiftUI iOS app profiled from Xcode • Trigger is specifically entering Show Cause & Effect Graph • Recordings can be short and still trigger it • Issue is much less severe or absent if I avoid that view What I already tried: • Rebooting • Short captures / fewer instruments • Clearing Xcode/Instruments caches/preferences • Retesting after cleanup • Reinstalling Xcode Is this a known Inst
2
0
125
1w
Reply to HealthKit on macOS
Looking at the docs ( https://developer.apple.com/documentation/healthkit ) shows that HealthKit is supported from 14.0+ but can add that capability to on the Identifiers tab and the info shows that only iOS, visionOS, and watchOS. I am guessing the docs are wrong but just wanted to know if HealthKit will ever make to maOS. I can't be the only one that dealt with data on a Mac when working at the desk.
1w
Third-party credential manager not appearing in Apple Passwords "Export Data to Another App" list — iOS 26
Hi, I'm building a third-party credential manager app and trying to get it listed as an eligible destination in Apple Passwords → Export Data to Another App on iOS 26 / macOS 26. The app never appears in the list, even on a physical device. What I've implemented so far: The main app and the Credential Provider Extension both have the com.apple.developer.authentication-services.autofill-credential-provider entitlement set. The extension's Info.plist has ASCredentialProviderExtensionCapabilities nested correctly under NSExtension → NSExtensionAttributes, with ProvidesPasskeys and ProvidesPasswords both set to true. Both targets share the same App Group. The extension is visible and selectable under Settings → General → AutoFill & Passwords — so the extension itself is working. I've also added ASCredentialImportManager and ASCredentialExportManager support to the app based on the AuthenticationServices SDK interfaces in Xcode 26. The specific question: What is the actual eligibility criteria for app
Topic: UI Frameworks SubTopic: General
2
0
175
1w
Reply to Implementation of Screen Recording permissions for background OCR utility
One thing worth considering: even if the Broadcast Extension technically works in the background, the UX friction will be significant. Users see the persistent red recording indicator in the status bar, which creates a surveillance perception regardless of your actual intent. For the text suggestion use case, you might want to explore an alternative approach — an accessibility-based solution using the Accessibility API (if targeting macOS) or a keyboard extension that analyzes context within the text field directly (iOS). The keyboard extension route avoids screen capture entirely and might align better with both user expectations and App Review guidelines.
Topic: Graphics & Games SubTopic: General Tags:
1w
CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
Hi everyone, We noticed a readability issue with the CallKit incoming call UI on the lock screen in iOS 26. In our case, the “slide to answer” text appears too faint and unclear, making it difficult to read. The arrow button is visible, but the text itself has very low contrast against the background, especially on certain wallpapers or under lower brightness conditions. From the screenshot, you can see that: the caller name is clear, the overall incoming call UI is shown correctly, but the “slide to answer” label is barely visible. This seems to be a system UI / CallKit presentation issue rather than something controlled by the app, since we are using the standard CallKit incoming call flow. We would like to know: Has anyone else seen this issue on iOS 26? Is this considered a known UI regression or contrast issue in the new system design? Is there any supported way to improve the visibility of this text, or is it fully managed by the system? Any confirmation or related reports would be ver
Topic: Design SubTopic: General Tags:
2
0
1.3k
1w
Reply to CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
I've noticed the same contrast issue on iOS 26 with dark wallpapers. This appears to be a Liquid Glass regression — the frosted material doesn't adapt well to certain background luminance levels. Since the slide to answer text is entirely system-managed through CallKit, there's no app-side workaround. I'd recommend filing a Feedback (if you haven't already) under UIKit > System UI with a screenshot showing the low contrast scenario. Referencing the WCAG 2.1 AA contrast ratio requirement (4.5:1 for normal text) in your report might help prioritize it, since this is a core accessibility concern for incoming calls.
Topic: Design SubTopic: General Tags:
1w
File Export from iOS - eventually import too
iOS 15 - iOS 26.x, SwiftUI, Xcode 26.1.1 (rewritten without links) I’m attempting to add the capability to export a file from CoreData. Since ShareLink requires iOS16+, I found an article showing how to create a UIKit wrapper for 'UIActivityViewController' This does work, but I end up with multiple files instead of one. How do I merge this into one file? Note: I don’t think I want to write to the app’s document directory – rather I’d like to allow the user to export to iCloud. Eventually, I’d like to share a list of dates with descriptions and if someone puts a sensitive date in there – I don’t want it to be left in a directory. I would include a warning that the file that they export needs to be handled with care if there are any sensitive dates. Some might consider birthdays as private information, right? I'd also like to be able to name the file - so far when the share sheet comes up, I select Save to Files and it uses a default name of text.txt My next step is to be able to import a CSV
Topic: UI Frameworks SubTopic: SwiftUI
6
0
319
1w
Reply to The iOS CallKit end my call without user action.
By analysis the log, seems the following 3 calls has been ended by system callkit (Not mainly trigger the end call): I'm not sure I follow the meaning of your log data. How do you know no user action was involved? Both calls are ending ~1s after the report which is with the range of human action, particularly if some kind of hardware action like pushing the side button of the phone or blocking through a headset's physical button is involved. @apple Do you have similar report that the iOS CallKit End the call withtour user action? No, not that I'm aware of. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: General Tags:
1w
Could not resolve host: static.rust-lang.org
This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the in
3
0
159
1w
Reply to Xcode 26.3 not rendering Unicode/Emoji in Simulator or Canvas
Thanks so much for this post and thanks for your patience on my replay. When Unicode characters and emojis render perfectly on a physical device but appear as blank spaces or empty boxes in the Simulator and SwiftUI Canvas, in my opinion it means the Color Emoji font is missing and this is corrupted, or failing to load inside the Simulator Runtime. Because the SwiftUI Canvas uses the exact same underlying simulator infrastructure as the standalone Simulator app, both break at the same time. We identified this a bug and I would encourage you to use the physical device or to download the latest beta simulators iOS 24.4 RC https://developer.apple.com/download/os/ and let me know it the issue has been fixed. Here are the most effective ways to resolve this issue: Open Xcode and go to Xcode > Settings (or Preferences) > Platforms. Find the iOS Simulator runtime you are currently using (e.g., iOS 26.3). Right-click (or Control-click) it and select Delete. Once deleted, click the + b
1w
Reply to How to store certificate to `com.apple.token` keychain access group.
Thanks for bringing this to the forums. The com.apple.token keychain access group, aka kSecAttrAccessGroupToken, isn’t a normal keychain access group. Rather, it’s a special group that holds all of the credentials that the system finds in CryptoTokenKit (CTK) tokens. Given that, you can’t add credentials to this group directly. It is possible to create a persistent CTK token, that is, one that’s not tied to smart card hardware. If you do that then the credentials published by that token will be available to all apps that are set up to use token-based credentials. It’s not clear whether this approach will work for your ultimate goal: [quote='819445021, h-noto, /thread/819445, /profile/h-noto'] so that Microsoft Edge for iOS … can … use it for client certificate authentication [/quote] My advice is that you first prototype this with an actual smart card [1]. If you can get that working, it’d be worth exploring the virtual token option. Finally, if you’re curious how an app can work with token-based cre
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Background upload issue in WatchOS
[quote='819449021, Team Tank Wars, /thread/819449, /profile/Team+Tank+Wars'] the remaining uploads do not proceed in the background and appear to be suspended. [/quote] Suspended forever? Or just a delayed? If you leave the watch in that state for a day, does it eventually attempt these stalled uploads? For context, there are URLSession and watchOS aspects to this. On the URLSession front, the system is free to delay background session transfer until an opportune time. While I have a lot less experience with this on the watchOS side, on iOS this often means that the transfer is deferred until overnight, when the device has both Wi-Fi and mains power. So I’m curious if the same thing is happening on the watch. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Reply to Different transaction IDs for the same purchase between SKPaymentTransaction and receipt latest_receipt_info
Please submit a feedback assistant ticket (http://feedbackassistant.apple.com), and we can assist further. Please provide as much information as possible, ie a sysdiagnose, app apple ID, in-app apple IDs, sandbox account apple ID (if applicable), transactions IDs, steps to reproduce and other relevant details. File ticket under iOS & iPadOS, macOS, tvOS, watchOS, or visionOS and ensure you select “App Store” for the question “Which area are you seeing an issue with?” Categorize the type of feedback Please attach all available files needed to verify After submitting the feedback, please regularly check the ticket as we'll only communicate through it from then on. Once you open the Feedback Assistant Ticket report, please post the FB number here for reference. If you have any questions about filing a report, take a look at Bug Reporting: How and Why?
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
1w
CXCallUpdate not working for outgoing calls
I try to update remoteHandle using CXCallUpdate for outgoing call, but this works only on iOS 15 but not on 17 or 18 (16 didn't test). This problem actual only for outgoing calls, but for incoming calls update works fine. func startOutgoingCall(with callID: UUID, userID: String) { let handle = CXHandle(type: .generic, value: userID) let action = CXStartCallAction(call: callID, handle: handle) callController.requestTransaction(with: action) { [weak self] error in // ... } } func updateOutgoingCall(with callID: UUID, groupID: String) { let update = CXCallUpdate() update.remoteHandle = CXHandle(type: .generic, value: groupID) provider.reportCall(with: callID, updated: update) } I also tried phoneNumber type but it seems initial handle that I set to CXStartCallAction not possible to change (value or even type). I use this handle value to implement recall by tap on call in Recents tab of system address book. But since my calls can transform from p2p to group call, I need to update handle value or find som
Replies
3
Boosts
0
Views
410
Activity
1w
hapticpatternlibrary.plist error with Text entry fields in Simulator only
When I have a TextField or TextEditor, tapping into it produces these two console entries about 18 times each: CHHapticPattern.mm:487 +[CHHapticPattern patternForKey:error:]: Failed to read pattern library data: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnderlyingError=0x600000ca1b30 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}} <_UIKBFeedbackGenerator: 0x600003505290>: Error creating CHHapticPattern: Error Domain=NSCocoaErrorDomain Code=260 The file “hapticpatternlibrary.plist” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSURL=file:///Library/Audio/Tunings/Generic/Haptics/Library/hapticpatternlibrary.plist, NSUnd
Replies
4
Boosts
0
Views
721
Activity
1w
Instruments Malfunction
I’m reporting a severe reproducible issue in Instruments, specifically when using the SwiftUI instrument and opening Show Cause & Effect Graph. What happens: • Instruments becomes extremely laggy/unresponsive • The graph/detail area can turn solid magenta/pink • Memory usage rapidly increases (I observed around 18 GB, 25 GB, and up to 34 GB) • My Mac has crashed/restarted during this, or in other terms, had a kernel panic, where my Mac froze, and everything unresponsive. The Trackpad wouldn't even click. Important detail: • I could not find a generated kernel panic log after the crash/restart. Repro context: • SwiftUI iOS app profiled from Xcode • Trigger is specifically entering Show Cause & Effect Graph • Recordings can be short and still trigger it • Issue is much less severe or absent if I avoid that view What I already tried: • Rebooting • Short captures / fewer instruments • Clearing Xcode/Instruments caches/preferences • Retesting after cleanup • Reinstalling Xcode Is this a known Inst
Replies
2
Boosts
0
Views
125
Activity
1w
Reply to HealthKit on macOS
Looking at the docs ( https://developer.apple.com/documentation/healthkit ) shows that HealthKit is supported from 14.0+ but can add that capability to on the Identifiers tab and the info shows that only iOS, visionOS, and watchOS. I am guessing the docs are wrong but just wanted to know if HealthKit will ever make to maOS. I can't be the only one that dealt with data on a Mac when working at the desk.
Replies
Boosts
Views
Activity
1w
Third-party credential manager not appearing in Apple Passwords "Export Data to Another App" list — iOS 26
Hi, I'm building a third-party credential manager app and trying to get it listed as an eligible destination in Apple Passwords → Export Data to Another App on iOS 26 / macOS 26. The app never appears in the list, even on a physical device. What I've implemented so far: The main app and the Credential Provider Extension both have the com.apple.developer.authentication-services.autofill-credential-provider entitlement set. The extension's Info.plist has ASCredentialProviderExtensionCapabilities nested correctly under NSExtension → NSExtensionAttributes, with ProvidesPasskeys and ProvidesPasswords both set to true. Both targets share the same App Group. The extension is visible and selectable under Settings → General → AutoFill & Passwords — so the extension itself is working. I've also added ASCredentialImportManager and ASCredentialExportManager support to the app based on the AuthenticationServices SDK interfaces in Xcode 26. The specific question: What is the actual eligibility criteria for app
Topic: UI Frameworks SubTopic: General
Replies
2
Boosts
0
Views
175
Activity
1w
Reply to Implementation of Screen Recording permissions for background OCR utility
One thing worth considering: even if the Broadcast Extension technically works in the background, the UX friction will be significant. Users see the persistent red recording indicator in the status bar, which creates a surveillance perception regardless of your actual intent. For the text suggestion use case, you might want to explore an alternative approach — an accessibility-based solution using the Accessibility API (if targeting macOS) or a keyboard extension that analyzes context within the text field directly (iOS). The keyboard extension route avoids screen capture entirely and might align better with both user expectations and App Review guidelines.
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
Hi everyone, We noticed a readability issue with the CallKit incoming call UI on the lock screen in iOS 26. In our case, the “slide to answer” text appears too faint and unclear, making it difficult to read. The arrow button is visible, but the text itself has very low contrast against the background, especially on certain wallpapers or under lower brightness conditions. From the screenshot, you can see that: the caller name is clear, the overall incoming call UI is shown correctly, but the “slide to answer” label is barely visible. This seems to be a system UI / CallKit presentation issue rather than something controlled by the app, since we are using the standard CallKit incoming call flow. We would like to know: Has anyone else seen this issue on iOS 26? Is this considered a known UI regression or contrast issue in the new system design? Is there any supported way to improve the visibility of this text, or is it fully managed by the system? Any confirmation or related reports would be ver
Topic: Design SubTopic: General Tags:
Replies
2
Boosts
0
Views
1.3k
Activity
1w
Reply to CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
I've noticed the same contrast issue on iOS 26 with dark wallpapers. This appears to be a Liquid Glass regression — the frosted material doesn't adapt well to certain background luminance levels. Since the slide to answer text is entirely system-managed through CallKit, there's no app-side workaround. I'd recommend filing a Feedback (if you haven't already) under UIKit > System UI with a screenshot showing the low contrast scenario. Referencing the WCAG 2.1 AA contrast ratio requirement (4.5:1 for normal text) in your report might help prioritize it, since this is a core accessibility concern for incoming calls.
Topic: Design SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
File Export from iOS - eventually import too
iOS 15 - iOS 26.x, SwiftUI, Xcode 26.1.1 (rewritten without links) I’m attempting to add the capability to export a file from CoreData. Since ShareLink requires iOS16+, I found an article showing how to create a UIKit wrapper for 'UIActivityViewController' This does work, but I end up with multiple files instead of one. How do I merge this into one file? Note: I don’t think I want to write to the app’s document directory – rather I’d like to allow the user to export to iCloud. Eventually, I’d like to share a list of dates with descriptions and if someone puts a sensitive date in there – I don’t want it to be left in a directory. I would include a warning that the file that they export needs to be handled with care if there are any sensitive dates. Some might consider birthdays as private information, right? I'd also like to be able to name the file - so far when the share sheet comes up, I select Save to Files and it uses a default name of text.txt My next step is to be able to import a CSV
Topic: UI Frameworks SubTopic: SwiftUI
Replies
6
Boosts
0
Views
319
Activity
1w
Reply to The iOS CallKit end my call without user action.
By analysis the log, seems the following 3 calls has been ended by system callkit (Not mainly trigger the end call): I'm not sure I follow the meaning of your log data. How do you know no user action was involved? Both calls are ending ~1s after the report which is with the range of human action, particularly if some kind of hardware action like pushing the side button of the phone or blocking through a headset's physical button is involved. @apple Do you have similar report that the iOS CallKit End the call withtour user action? No, not that I'm aware of. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Could not resolve host: static.rust-lang.org
This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the in
Replies
3
Boosts
0
Views
159
Activity
1w
Reply to Xcode 26.3 not rendering Unicode/Emoji in Simulator or Canvas
Thanks so much for this post and thanks for your patience on my replay. When Unicode characters and emojis render perfectly on a physical device but appear as blank spaces or empty boxes in the Simulator and SwiftUI Canvas, in my opinion it means the Color Emoji font is missing and this is corrupted, or failing to load inside the Simulator Runtime. Because the SwiftUI Canvas uses the exact same underlying simulator infrastructure as the standalone Simulator app, both break at the same time. We identified this a bug and I would encourage you to use the physical device or to download the latest beta simulators iOS 24.4 RC https://developer.apple.com/download/os/ and let me know it the issue has been fixed. Here are the most effective ways to resolve this issue: Open Xcode and go to Xcode > Settings (or Preferences) > Platforms. Find the iOS Simulator runtime you are currently using (e.g., iOS 26.3). Right-click (or Control-click) it and select Delete. Once deleted, click the + b
Replies
Boosts
Views
Activity
1w