Search results for

“Visual Studio Maui IOS”

109,080 results found

Post

Replies

Boosts

Views

Activity

How to create ControlWidget button that opens my App
Hi, I want to create a ControlWidget button that acts as a shortcut in the control center open a specific view within my app to show a badge. Problem: I can‘t get it to open my host app. I tried a custom myapp:// protocol - did not work, I tied AppIntent with the openAppWhenRun set to true - did not work and the strange thing is the debugger breakpoint in perform will only get triggered if this is set to false. OpenIntent did not work either even if I use a dummy swift app as host to try it out. What is the current supported way (iOS 18 and 26) to open your app when a static ControlWidget button is clicked, what could I have done wrong / am missing?
1
0
74
1w
Reply to Crash on App Clip Subtitle Focus
Thanks for the post. I don’t think you have provided much information to be able to help you. Can you provide a focused sample of how you use App Clips? Are you using Xcode, can you create a new sample project that reproduces the issue using the steps below? App Clips are built as a separate target within your existing iOS app project. Open your project in Xcode. Go to File > New > Target. Select App Clip under the iOS tab. Name your App Clip and ensure it is embedded in your main application target. App Clips rely heavily on Universal Links to securely verify the relationship between your website and your app. Add the Associated Domains capability to both your main app target and your App Clip target. Add your domain using the appclips: prefix. Example: appclips:example.com Update the apple-app-site-association (AASA) file on your web server to include an appclips dictionary. { appclips: { apps: [..Clip] } } Please follow this great documentation: https://developer.apple.com/design/hu
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much with the post. Can I ask you what’s your “cloud-based device testing environment”? Because Universal Links rely on cryptographic trust between the app and the web server, the re-signing process inherently could breaks this trust? The platform signs the app with their own provisioning profile, which does not contain your com.apple.developer.associated-domains entitlement? Apple's security model intentionally prevents unauthorized third parties from claiming your domain. Therefore, there is no native Apple provisioning flag that tells iOS to ignore AASA validation for re-signed builds. Can you provide more details? However, please understand that Universal Links will only work on physical devices with the entitlement. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
1w
TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info
1
0
166
1w
Reply to TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Had the same problem, testing an iOS app on macOS via TestFlight which previously worked, did recently stop working. But I found a setting in App Store Connect, under each testing group, that says Test iPhone and iPad Apps on Apple Silicon Macs. Enabling this setting made testing on macOS work again.
1w
Reply to AXSpeech Thread Crash SEGV_ACCERR
Thanks for those crash reports. Are you able to find a JSON crash report (.ips) for this? If so, please post it, because it may allow me to learn more about the issue. In the absence of that then, yeah, at first blush this is looks like an Apple problem rather than a problem with your code. Consider the crashing thread from your first crash report: Thread 22 name: Thread 22 Crashed: 0 CoreFoundation … __CFCheckCFInfoPACSignature + 4 (CFRuntime.c:559) 1 CoreFoundation … CFRunLoopSourceSignal + 28 (CFRunLoop.c:4312) 2 Foundation … performQueueDequeue + 484 (NSThread.m:1063) 3 Foundation … __NSThreadPerformPerform + 88 (NSThread.m:1077) 4 CoreFoundation … __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1970) 5 CoreFoundation … __CFRunLoopDoSource0 + 172 (CFRunLoop.c:2014) 6 CoreFoundation … __CFRunLoopDoSources0 + 332 (CFRunLoop.c:2059) 7 CoreFoundation … __CFRunLoopRun + 840 (CFRunLoop.c:2969) 8 CoreFoundation … CFRunLoopRunSpecific + 572 (CFRunLoop.c:3434) 9 Foundation … -[NSRunLoo
1w
Xcode 26 Warning: (arm64) empty dSYM file detected despite correct build settings
Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue persists regardless of these standard
2
0
74
1w
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
2
0
1.1k
1w
Strange crash in iOS AudioToolboxCore when using AVSpeechSynthesizer in iOS 16
I'm getting Crashlytics crashes from some my users, deep in the Apple code: Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000007ec54b360 0 libobjc.A.dylib 0x3c9c objc_retain_x8 + 16 1 AudioToolboxCore 0x99580 auoop::RenderPipeUser::~RenderPipeUser() + 112 2 AudioToolboxCore 0xe6090 -[AUAudioUnit_XPC internalDeallocateRenderResources] + 92 3 AVFAudio 0x90a0 AUInterfaceBaseV3::Uninitialize() + 60 4 AVFAudio 0x4cbe0 AVAudioEngineGraph::PerformCommand(AUGraphNodeBaseV3&, AVAudioEngineGraph::ENodeCommand, void*, unsigned int) const + 768 5 AVFAudio 0x56b0c AVAudioEngineGraph::_Uninitialize(NSError**) + 132 6 AVFAudio 0x7834 AVAudioEngineImpl::Stop(NSError**) + 388 7 AVFAudio 0x636c -[AVAudioEngine dealloc] + 52 8 TextToSpeech 0x30674 _TTSNameForVoiceInformation + 20864 9 libobjc.A.dylib 0x20a4 object_cxxDestructFromClass(objc_object*, objc_class*) + 116 10 libobjc.A.dylib 0x6e00 objc_destructInstance + 80 11 libobjc.A.dylib 0x104fc _objc_rootDealloc + 80 12 TextToSpeech 0x2d2f4 _TTSNameForVoiceInfo
6
0
2.4k
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Thanks for your reply!We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware, and established multiple TCP connections. However, we still have a throughput issue: when the iOS device acts as a Subscriber, and sends an HTTP request over an already-established TCP connection to download resources from the non-iOS device, we observe slow download speeds — only around 20 MB/s. We compared iOS system logs and found: When the non-iOS device connects to iOS, the timeslot bitmap used is ff ff 00 00 ff ff. When iOS connects to iOS, all timeslots are used. Could this be the reason for the large difference in transmission rates? Is this caused by configuration, or what leads to the reduced timeslot allocation? Log 1: Non-iOS device connecting to iOS default 16:33:33.204715+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 000
1w
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstalled on dev
1
0
222
1w
Reply to Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
[quote='819926021, craigc123, /thread/819926, /profile/craigc123'] is there any way to programmatically trigger “realtime” mode? [/quote] No. Well: Not as an API that’s documented to have that effect. It might be possible to find some API that does it as a side effect, but that would be an implementation detail and thus not something you’d want to rely on. And there’s the Wi-Fi Aware option, but you’ve ruled that out. I think you should create a prototype based on Wi-Fi Aware and see if it achieves the latency goals that you need. If it does, you can then factor that into your decision as to how to proceed here. And apropos that, you wrote: [quote='819926021, craigc123, /thread/819926, /profile/craigc123'] I am looking for a solution that works … on previous OS versions. [/quote] Note that Wi-Fi Aware requires iOS 26 and specific hardware. The main framework doc page has the list. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
How to create ControlWidget button that opens my App
Hi, I want to create a ControlWidget button that acts as a shortcut in the control center open a specific view within my app to show a badge. Problem: I can‘t get it to open my host app. I tried a custom myapp:// protocol - did not work, I tied AppIntent with the openAppWhenRun set to true - did not work and the strange thing is the debugger breakpoint in perform will only get triggered if this is set to false. OpenIntent did not work either even if I use a dummy swift app as host to try it out. What is the current supported way (iOS 18 and 26) to open your app when a static ControlWidget button is clicked, what could I have done wrong / am missing?
Replies
1
Boosts
0
Views
74
Activity
1w
Reply to Crash on App Clip Subtitle Focus
Thanks for the post. I don’t think you have provided much information to be able to help you. Can you provide a focused sample of how you use App Clips? Are you using Xcode, can you create a new sample project that reproduces the issue using the steps below? App Clips are built as a separate target within your existing iOS app project. Open your project in Xcode. Go to File > New > Target. Select App Clip under the iOS tab. Name your App Clip and ensure it is embedded in your main application target. App Clips rely heavily on Universal Links to securely verify the relationship between your website and your app. Add the Associated Domains capability to both your main app target and your App Clip target. Add your domain using the appclips: prefix. Example: appclips:example.com Update the apple-app-site-association (AASA) file on your web server to include an appclips dictionary. { appclips: { apps: [..Clip] } } Please follow this great documentation: https://developer.apple.com/design/hu
Replies
Boosts
Views
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Thanks so much with the post. Can I ask you what’s your “cloud-based device testing environment”? Because Universal Links rely on cryptographic trust between the app and the web server, the re-signing process inherently could breaks this trust? The platform signs the app with their own provisioning profile, which does not contain your com.apple.developer.associated-domains entitlement? Apple's security model intentionally prevents unauthorized third parties from claiming your domain. Therefore, there is no native Apple provisioning flag that tells iOS to ignore AASA validation for re-signed builds. Can you provide more details? However, please understand that Universal Links will only work on physical devices with the entitlement. Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
Reply to SwiftUI NavigationTitle does not support Localization in iOS 18
iOS 26 still doesn't work lol
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
1w
SwiftUI NavigationTitle does not support Localization in iOS 18
NavigationTitle does not change when the app language changes. It works well in iOS 17.5 but does not in iOS 18.x
Replies
11
Boosts
0
Views
1.3k
Activity
1w
TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info
Replies
1
Boosts
0
Views
166
Activity
1w
Reply to TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Had the same problem, testing an iOS app on macOS via TestFlight which previously worked, did recently stop working. But I found a setting in App Store Connect, under each testing group, that says Test iPhone and iPad Apps on Apple Silicon Macs. Enabling this setting made testing on macOS work again.
Replies
Boosts
Views
Activity
1w
Reply to AXSpeech Thread Crash SEGV_ACCERR
Thanks for those crash reports. Are you able to find a JSON crash report (.ips) for this? If so, please post it, because it may allow me to learn more about the issue. In the absence of that then, yeah, at first blush this is looks like an Apple problem rather than a problem with your code. Consider the crashing thread from your first crash report: Thread 22 name: Thread 22 Crashed: 0 CoreFoundation … __CFCheckCFInfoPACSignature + 4 (CFRuntime.c:559) 1 CoreFoundation … CFRunLoopSourceSignal + 28 (CFRunLoop.c:4312) 2 Foundation … performQueueDequeue + 484 (NSThread.m:1063) 3 Foundation … __NSThreadPerformPerform + 88 (NSThread.m:1077) 4 CoreFoundation … __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1970) 5 CoreFoundation … __CFRunLoopDoSource0 + 172 (CFRunLoop.c:2014) 6 CoreFoundation … __CFRunLoopDoSources0 + 332 (CFRunLoop.c:2059) 7 CoreFoundation … __CFRunLoopRun + 840 (CFRunLoop.c:2969) 8 CoreFoundation … CFRunLoopRunSpecific + 572 (CFRunLoop.c:3434) 9 Foundation … -[NSRunLoo
Replies
Boosts
Views
Activity
1w
Xcode 26 Warning: (arm64) empty dSYM file detected despite correct build settings
Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue persists regardless of these standard
Replies
2
Boosts
0
Views
74
Activity
1w
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
Replies
2
Boosts
0
Views
1.1k
Activity
1w
Strange crash in iOS AudioToolboxCore when using AVSpeechSynthesizer in iOS 16
I'm getting Crashlytics crashes from some my users, deep in the Apple code: Crashed: AXSpeech EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000007ec54b360 0 libobjc.A.dylib 0x3c9c objc_retain_x8 + 16 1 AudioToolboxCore 0x99580 auoop::RenderPipeUser::~RenderPipeUser() + 112 2 AudioToolboxCore 0xe6090 -[AUAudioUnit_XPC internalDeallocateRenderResources] + 92 3 AVFAudio 0x90a0 AUInterfaceBaseV3::Uninitialize() + 60 4 AVFAudio 0x4cbe0 AVAudioEngineGraph::PerformCommand(AUGraphNodeBaseV3&, AVAudioEngineGraph::ENodeCommand, void*, unsigned int) const + 768 5 AVFAudio 0x56b0c AVAudioEngineGraph::_Uninitialize(NSError**) + 132 6 AVFAudio 0x7834 AVAudioEngineImpl::Stop(NSError**) + 388 7 AVFAudio 0x636c -[AVAudioEngine dealloc] + 52 8 TextToSpeech 0x30674 _TTSNameForVoiceInformation + 20864 9 libobjc.A.dylib 0x20a4 object_cxxDestructFromClass(objc_object*, objc_class*) + 116 10 libobjc.A.dylib 0x6e00 objc_destructInstance + 80 11 libobjc.A.dylib 0x104fc _objc_rootDealloc + 80 12 TextToSpeech 0x2d2f4 _TTSNameForVoiceInfo
Replies
6
Boosts
0
Views
2.4k
Activity
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Thanks for your reply!We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware, and established multiple TCP connections. However, we still have a throughput issue: when the iOS device acts as a Subscriber, and sends an HTTP request over an already-established TCP connection to download resources from the non-iOS device, we observe slow download speeds — only around 20 MB/s. We compared iOS system logs and found: When the non-iOS device connects to iOS, the timeslot bitmap used is ff ff 00 00 ff ff. When iOS connects to iOS, all timeslots are used. Could this be the reason for the large difference in transmission rates? Is this caused by configuration, or what leads to the reduced timeslot allocation? Log 1: Non-iOS device connecting to iOS default 16:33:33.204715+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 000
Replies
Boosts
Views
Activity
1w
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstalled on dev
Replies
1
Boosts
0
Views
222
Activity
1w
Reply to Triggering “realtime” mode for peer-to-peer WiFi via awdl to fix jitter problems
[quote='819926021, craigc123, /thread/819926, /profile/craigc123'] is there any way to programmatically trigger “realtime” mode? [/quote] No. Well: Not as an API that’s documented to have that effect. It might be possible to find some API that does it as a side effect, but that would be an implementation detail and thus not something you’d want to rely on. And there’s the Wi-Fi Aware option, but you’ve ruled that out. I think you should create a prototype based on Wi-Fi Aware and see if it achieves the latency goals that you need. If it does, you can then factor that into your decision as to how to proceed here. And apropos that, you wrote: [quote='819926021, craigc123, /thread/819926, /profile/craigc123'] I am looking for a solution that works … on previous OS versions. [/quote] Note that Wi-Fi Aware requires iOS 26 and specific hardware. The main framework doc page has the list. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Reply to iOS26.4,appStoreReceiptURL获取票据延迟
I'm encountering the same issue as you; currently, I've implemented a 1.5-second delay. I hope Apple can resolve this soon. Recently, I tried upgrading to StoreKit 2, but on iOS 26.4, Transaction.updates does not return unfinished transactions upon launch, which is causing some problems.
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
1w