Sender name is incorrect if the name is like "テスト 太郎" and the address book doesn't have the mail address. The bug exists for a long time (at least from iOS 12 or older). It is not resolved in iOS/iPadOS 17 RC. Expected: It shows "テスト 太郎". Actually: It shows "太郎テスト". I made some feedback but they are still ignored. FB6102121 FB8890556 FB8927408

Hello, I have issue when downloading and installing iOS 17 simulators. I have deleted them since the crash of iPhone 15 Pro and 15 Pro Simulators from Xcode 15 RC, and I cannot reinstall them. It's a server issue with HTTP 400 code: Bad request. Can you help me with this issue. Note: any kind of simulator cannot be downloaded actually due to this error code. Details of failure right below: Domain: DataGatheringNSURLSessionDelegate Code: 1 User Info: { DVTErrorCreationDateKey = "2023-09-19 14:25:10 +0000"; } -- System Information macOS Version 13.5.2 (Build 22G91) Xcode 15.0 (22265) (Build 15A240d) Timestamp: 2023-09-19T16:25:10+02:00 Thanks for your answer.

I cannot get an assembly language file for architecture aarch64 (iOS) to assemble. The error message is Command CompileC failed with a non-zero exit code. I have been able to compile C, C++ and Swift without problems. The assembly language file has type "Assembly". When I change the file type to "Assembly-LLVM", Xcode says that there is no rule. When I change the file type to "Assembly-NASM" Xcode says that the script must have at least one output. Do I need to load something additional for Xcode to assemble files? Thanks! Gene

Hello y'all, I would like to discuss here if anyone else is noticing that some PDF files are not rendered as expected in iOS/iPadOS 17, it seems that some text with background (screenshot attached) are not rendered and you can only see the back color. The issue is reproducible on Preview, Safari, where I guess Apple is using PDFKit framework too. We submitted different issues with Feedback Assistant, however I've not hear back from Apple yet. Is anyone else able to reproduce the issue? Thanks,

Can someone confirm that Personal Voice is available for devices running a A12 chipset ? Currently it does not appear in the Speech settings of an IPad Mini 5 or was this feature pulled from the IOS 17 rollout to be released at a later date through an Update…? There is very limited information on the Internet regarding this feature on A12 Chipsets.

I saw a similar post to this where the issue was fixed in the final iOS17 release, but I am still having a problem since my situation is slightly different. I am wondering if its a bug based on current behavior, but was hoping maybe someone knows if the issue is with my setup? I am trying to monitor an external USB camera's audio input using the new iOS17 external call for iPad, over bluetooth. func setupAudioSession() { let audioSession = AVAudioSession.sharedInstance() do { try audioSession.setCategory(.playAndRecord, mode: .default, options: [.allowBluetoothA2DP, .defaultToSpeaker] ) try audioSession.setActive(true) } catch { print("Failed to set up audio session: \(error)") } } When my execution order is: setupAudioSession() // code above // discover and connect the session AV inputs to the external USB // start an audio engine // connect audio engine output to a buffer queue and play // start the session My app does not allow routing to the headphones and directly switches to speaker. However if I change the order to this: setupAudioSession() // code above // discover and connect the session AV inputs to the external USB // start an audio engine // start the session --- !starting before connecting output! // connect audio engine output to a buffer queue and play The session stays connected to Bluetooth and plays over the headphones. However if I suspend the app and relaunch, I get switched back to speaker. I understand maybe the system is trying to prevent an audio feedback loop? But don't understand why launching the session early would get the desired behavior. Any help would be greatly appreciated.

iPad WKWebView can't load some pages on "https://www.baidu.com" website e.g. "https://www.baidu.com/s?wd=123" When load 'https://www.baidu.com/s?wd=123' in wkwebview, some wkwebview.navigationDelegate methods are always called in a loop And this problem occurs in iPad iOS16+

I'm using karabiner-elements on my macbook air. I hope this app can be used on the iPad as well. Is it possible to create a physical keyboard customization app like karabinar elements for iPad?

https://docs-assets.developer.apple.com/published/a3e438f759/EqualizingAudioWithDiscreteCosineTransformsDCTs.zip Example builds but does not run properly under Sonoma (23A344) on MBP with Intel hardware. (drum beat sound track is not played) It does run properly under iPadOS 17.0.1 on iPad Air 5 (M1 chip)

iPad Pro 12.9 、iOS15.4 (21E230) #700003 NSInternalInconsistencyException -[UINSUIKitBackgroundingController _updateAppWideBackgroundStateSlammingNotifyingDelegate:]: Called off the main thread. CoreFoundation __exceptionPreprocess CoreFoundation __exceptionPreprocess + 220 2 Foundation -[NSCalendarDate initWithCoder:] + 0 3 UIKitMacHelper -[UINSUIKitBackgroundingController _updateAppWideBackgroundStateSlammingNotifyingDelegate:] + 504 4 UIKitMacHelper -[UINSUIKitBackgroundingController transitionUIAppThroughBackgroundStateIfNecessary] + 144 5 UIKitMacHelper -[UINSApplicationLifecycleController transitionAppThroughBackgroundState] + 308 6 UIKitMacHelper -[UINSApplicationDelegate _toggleAppForegroundStateIfAppStoreURL:] + 276 7 UIKitMacHelper __54-[UINSApplicationDelegate openURL:options:completion:]_block_invoke_2 + 196 8 AppKit _NSWorkspaceHandleLSOpenResult + 164 9 LaunchServices _LSFireCompletionHandler(void (__LSASN const*, unsigned char, __CFError*) block_pointer, NSURL*, NSURL*, NSDictionary<NSString*, objc_object*>, objc_object, bool, NSError*) + 200 10 LaunchServices _LSOpenAsyncCommonDispatched(objc_object*, NSArray<NSURL*>, NSURL, objc_object*, NSDictionary<NSString*, objc_object*>, NSObject<OS_dispatch_semaphore>, void (__LSASN const*, unsigned char, __CFError*) block_pointer) + 5732 11 libdispatch.dylib _dispatch_call_block_and_release + 32 17 libsystem_pthread.dylib start_wqthread + 8 #0 Thread 0 libsystem_kernel.dylib mach_msg_trap + 8 4 CoreFoundation CFRunLoopRunSpecific + 600 5 HIToolbox RunCurrentEventLoopInMode + 292 6 HIToolbox ReceiveNextEventCommon + 564 7 HIToolbox _BlockUntilNextEventMatchingListInModeWithFilter + 72 8 AppKit _DPSNextEvent + 860 9 AppKit -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1328 10 AppKit -[NSApplication run] + 596 11 AppKit NSApplicationMain + 1132 12 AppKit +[NSWindow _savedFrameFromString:] + 0 13 UIKitMacHelper UINSApplicationMain + 1276

I'm trying to build the DriverKit template driver target in an Xcode project which contains an app targeting iPadOS 17. I've made no modifications to the DriverKit template. When building, I get this link error ld: file cannot be open()ed, errno=2 path=/Applications/Xcode 15.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a in '/Applications/Xcode 15.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a' anyone know how to fix this? My search turned up something about building llvm from sources, which seems like overkill to put a DriverKit driver into an iPad app.

Hello, I don't know if this is possible, but look for a developer who can make an application or code that allows you to show the Apple Pencil 2 pointer on the screen when you are writing or even when you lift the iPad pencil slightly and that you can put an image in this pencil pointer, an example would be the cursorfx program in Windows, the closest thing I found on the iPad is in the iPad Notes app (app that comes with the iPad as standard) it shows the pencil pointer when it is raised and scrolling across the screen, finally I want to make it compatible with goodnotes

We maintain an app that uses Automatic Assessment Configuration and WebKit, and have encountered a bug in iOS 17 that causes the app to crash when an input element is focused in AAC mode. In the console, we see the following error, which may or may not be related: RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID. This error message appears when touching an input field even when there is no crash. We've tried various "fixes" like removing our non-HTML input elements and disabling auto-complete. None of them prevented the crashing behavior. The crash only occurs when the AAC session has started. We were able to create a minimally-reproducing example app that loads a bit of static HTML: https://github.com/AllofESolutions/aac-crash-example Has anyone else encountered this issue? Is there any work-around?

macOS 14 Sonoma cifilter issue (Designed for iPad) I just updated my M1 Mac to MacOS 14 Sonoma. I ran the iOS/iPadOS app built in Xcode 15.0 on a Mac whose OS was updated using Testflight. (My app is Designed for iPad and is set to run on macOS.) When UIImage is processed using cifilter, the generated image may be grayed out. The same code does not occur on iOS and iPadOS. In other words, it does not occur on iPhone and iPad iOS/iPadOS 17. Has anyone experienced a similar issue? And I would like to know the solution ASAP. I am distributing the app as Designed for iPad. Every year, when Mac OS is updated, an issue arises. So, I am considering not allowing Vision Pro to run the current iOS/iPadOS app.

Hi there, I have a big issue and I couldn't find any solution that's why I'm here. I am developing an algorithm under Laravel, and I need to know what kind of device the user use. Before, I used to use user-agent but its not longer available under mac and probably others but I couldn't verified. Does someone could help me because I don't know what to do otherwise. Thanks

If I do this, I'll only have to submit the iOS version of the app and not have to dork with two app reviews. What do you think? What am I missing?

Body: Hello, I am facing a challenging issue with my SwiftUI iOS application, which is designed to work on an iPad and connect to an external display. The app, called "EasyJoin," is intended to provide a single-touch interface for joining conference meetings. It pulls events from a calendar and provides a "Join" button to connect to the meeting. The Goal: Mirror the app on an external display in its native aspect ratio. Also mirror any other client applications launched from EasyJoin (such as Google Meet, Teams, WebEx, Zoom) to the external display in its native aspect ratio. The Issue: While I have been successful in displaying the app on the external display, the iPad screen goes black as soon as the external display is connected. I need both the iPad and the external display to show the app simultaneously, each in their native aspect ratios. What I've Tried: Created separate UIWindow objects for the internal and external displays. Used NotificationCenter to listen for UIScreen.didConnectNotification and UIScreen.didDisconnectNotification. Tried managing windows through both AppDelegate and SceneDelegate. Explicitly set windowLevel for both internal and external windows. Despite these efforts, the issue persists. The external display works as expected, but the iPad screen remains black. Here is a snippet of my SceneDelegate.swift: // ... (Code for setting up UIWindow and listening for screen connect/disconnect) @objc func screenDidConnect(notification: Notification) { // ... (Code for setting up external UIWindow) externalWindow?.isHidden = false } @objc func screenDidDisconnect(notification: Notification) { externalWindow?.isHidden = true externalWindow = nil } I would appreciate any guidance or suggestions to resolve this issue. Thank you! Feel free to copy and paste this into a new post on the Apple Developer Forums. Hopefully, you'll get some specialized assistance that can help resolve the issue.

Incident Identifier: C7E20EA3-7315-404A-83D5-8DBD20F8406B Hardware Model: iPad13,1 Process: 月儿记账 [352] Path: /private/var/containers/Bundle/Application/1F4F62A3-A990-4094-9982-DB0CFBB82662/月儿记账.app/月儿记账 Identifier: top.bytearts.money Version: 1.6.0 (000194) AppStoreTools: 15A240a AppVariant: 1:iPad13,1:15 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: top.bytearts.money [491] Date/Time: 2023-09-28 00:34:09.5371 +0800 Launch Time: 2023-09-28 00:34:03.1161 +0800 OS Version: iPhone OS 17.0 (21A329) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: 月儿记账 [352] Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x19862a5e0 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1909abc00 objc_exception_throw + 60 (objc-exception.mm:356) 2 Foundation 0x197b944d4 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 172 (NSException.m:261) 3 UIKitCore 0x19a844904 _UIGraphicsBeginImageContextWithOptions + 568 (UIGraphics.m:407) 4 UIKitCore 0x19a8428d0 -[UIImageView(Pretiling) _updatePretiledImageCacheForImage:] + 812 (UIImageView_Pretiling.m:171) 5 UIKitCore 0x19a7920b0 -[UIImageView _updateImageViewForOldImage:newImage:] + 496 (UIImageView.m:3604) 6 UIKitCore 0x19a75c0fc -[UIImageView _resolveImagesWithPreviouslyDisplayedImage:] + 836 (UIImageView.m:3409) 7 UIKitCore 0x19a75bd74 -[UIImageView _setImage:invalidatingPendingSymbolTransitions:] + 280 (UIImageView.m:1379) 8 UIKitCore 0x19a7c1ab0 -[UIButtonLegacyVisualProvider _updateBackgroundImageView] + 124 (UIButtonLegacyVisualProvider.m:1795) 9 UIKitCore 0x19a7c02c4 -[UIButtonLegacyVisualProvider layoutSubviews] + 100 (UIButtonLegacyVisualProvider.m:2379) 10 UIKitCore 0x19a7c021c -[UIButton layoutSubviews] + 40 (UIButton.m:2811) 11 UIKitCore 0x19a7831d8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1528 (UIView.m:19754) 12 QuartzCore 0x199b9b888 CA::Layer::layout_if_needed(CA::Transaction*) + 500 (CALayer.mm:10783) 13 QuartzCore 0x199b9b410 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 144 (CALayer.mm:2594) 14 QuartzCore 0x199ba194c CA::Context::commit_transaction(CA::Transaction*, double, double*) + 464 (CAContextInternal.mm:2792) 15 QuartzCore 0x199b9ac3c CA::Transaction::commit() + 648 (CATransactionInternal.mm:432) 16 QuartzCore 0x199b9a8e4 CA::Transaction::flush_as_runloop_observer(bool) + 88 (CATransactionInternal.mm:942) 17 CoreFoundation 0x1985731dc __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 (CFRunLoop.c:1789) 18 CoreFoundation 0x198571be4 __CFRunLoopDoObservers + 548 (CFRunLoop.c:1902) 19 CoreFoundation 0x198571300 __CFRunLoopRun + 1028 (CFRunLoop.c:2983) 20 CoreFoundation 0x198570e18 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420) 21 GraphicsServices 0x1db02d5ec GSEventRunModal + 164 (GSEvent.c:2196) 22 UIKitCore 0x19a97f350 -[UIApplication _run] + 888 (UIApplication.m:3690) 23 UIKitCore 0x19a97e98c UIApplicationMain + 340 (UIApplication.m:5275) 24 月儿记账 0x10067cfcc main + 68 (main.m:18) 25 dyld 0x1bad53d44 start + 2104 (dyldMain.cpp:1269)

I just updated my iPad AIR5 and Ipad AIR5 m1 version 17.0.2

With the release of iPadOS 17 we began noticing that the AssetCacheLocator service on iOS/iPadOS was reliably returning a "no caching server" response even when we had active caching servers on the network. default 2023-09-27 18:40:17.970429 +1000 AssetCacheLocatorService #11553fbd [AssetCacheLocatorService.queue] found no caching servers This behaviour was also apparent during the beta releases of iPadOS 17 but vanished around beta 8 before returning during the production release. For a bit of back story our network environment makes use of proxy servers which devices are configured to use via PAC discovery methods. Either via specifying a pac url in config payload or via auto-discovery means via DHCP option 252 or dns. We have been compliant with https PAC file delivery since it was first brought in for the iPadOS 15 release. After continued testing the behaviour was being cause by a failure in the trust daemon to validate certificates used in SSL handshakes for the AssetCacheLocatorService. This would result in NSURLNetworkError = -999 being reported for network tasks started from the AssetCacheLocatorService. default 2023-09-27 18:40:17.961617 +1000 AssetCacheLocatorService Task <027E06F3-3994-4BE1-9F3C-EA3C22110ACA>.<1> finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, NSLocalizedDescription=<private>} I initially thought these trust failures were directly related to ocsp and crl requests needed to validate the "https://lcdn-locator.apple.com/lcdn/locate" api. However, when testing was performed utilising no PAC url or via using manual proxy settings AssetCacheLocatorservice would correctly find caching servers on the network. Puzzled by this response continued analysis of the logs generated from the trust daemon pointed in the direction of HTTPS pac file delivery. It seems that the AssetCacheLocatorService enforces certificate validation for all SSL sessions it establishes. Should a validation fail the entire process is cancelled and a "no caching server" response is returned. The problem is that this is also applying to the PAC file retrieval over HTTPS. I suspect may be causing a loop where it's unable to validate the certificate used for HTTPS pac file retrieval without having the pac file. After disabling HTTPS pac file support on our network we then observed that the AssetCacheLocatorService completed successfully: HTTPS PAC File default 2023-09-27 18:40:17.661202 +1000 AssetCacheLocatorService CFNetwork Diagnostics [3:6] 18:40:17.660 { Authentication Challenge: (null) Loader: request POST https://lcdn-locator.apple.com/<redacted> Challenge: challenge space https://lcdn-locator.apple.com:443/, ServerTrustEvaluationRequested (Hash 91283047ef00ae3c) } [3:6] default 2023-09-27 18:40:17.662336 +1000 AssetCacheLocatorService [0x974b0e130] activating connection: mach=true listener=false peer=false name=com.apple.trustd default 2023-09-27 18:40:17.664988 +1000 AssetCacheLocatorService user sessions enabled, targeting 501 default 2023-09-27 18:40:17.665056 +1000 AssetCacheLocatorService [0x974a255e0] activating connection: mach=true listener=false peer=false name=com.apple.trustd default 2023-09-27 18:40:17.928484 +1000 AssetCacheLocatorService cleaning up unpooled xpc conn to trustd 0x974a255e0 default 2023-09-27 18:40:17.928567 +1000 AssetCacheLocatorService [0x974a255e0] invalidated on xpc_connection_cancel() error 2023-09-27 18:40:17.928972 +1000 AssetCacheLocatorService #11553fbd [NSOperationQueue 0x97490ac50 (QOS: UNSPECIFIED)] LocateURL https://lcdn-locator.apple.com/lcdn/locate untrusted: EV=(null) organization=(null) default 2023-09-27 18:40:17.929114 +1000 AssetCacheLocatorService got event: Connection invalid default 2023-09-27 18:40:17.929167 +1000 AssetCacheLocatorService Task <027E06F3-3994-4BE1-9F3C-EA3C22110ACA>.<1> auth completion disp=2 cred=0x0 default 2023-09-27 18:40:17.957367 +1000 AssetCacheLocatorService Task <027E06F3-3994-4BE1-9F3C-EA3C22110ACA>.<1> summary for task failure {transaction_duration_ms=3211, response_status=-1, connection=1, reused=1, request_start_ms=0, request_duration_ms=0, response_start_ms=0, response_duration_ms=0, request_bytes=0, response_bytes=0, cache_hit=false} HTTP Pac File (no https support) default 2023-09-29 16:30:02.452153 +1000 AssetCacheLocatorService CFNetwork Diagnostics [3:6] 16:30:02.452 { Authentication Challenge: (null) Loader: request POST https://lcdn-locator.apple.com/<redacted> Challenge: challenge space https://lcdn-locator.apple.com:443/, ServerTrustEvaluationRequested (Hash 91283047ef00ae3c) } [3:6] default 2023-09-29 16:30:02.454355 +1000 AssetCacheLocatorService [0x81691bab0] activating connection: mach=true listener=false peer=false name=com.apple.trustd default 2023-09-29 16:30:02.455334 +1000 AssetCacheLocatorService user sessions enabled, targeting 501 default 2023-09-29 16:30:02.455436 +1000 AssetCacheLocatorService [0x816b12dc0] activating connection: mach=true listener=false peer=false name=com.apple.trustd default 2023-09-29 16:30:02.630496 +1000 AssetCacheLocatorService cleaning up unpooled xpc conn to trustd 0x816b12dc0 default 2023-09-29 16:30:02.630672 +1000 AssetCacheLocatorService [0x816b12dc0] invalidated on xpc_connection_cancel() default 2023-09-29 16:30:02.631720 +1000 AssetCacheLocatorService got event: Connection invalid default 2023-09-29 16:30:02.631788 +1000 AssetCacheLocatorService Task <44EC5539-7E06-4BC5-AD2D-F40E43C947B6>.<1> auth completion disp=0 cred=0x816a14490 default 2023-09-29 16:30:02.632041 +1000 AssetCacheLocatorService CFNetwork Diagnostics [3:7] 16:30:02.631 { Use Credential: (null) Loader: request POST https://lcdn-locator.apple.com/<redacted> Credential: Name: iswlocator.apple.com, Persistence: session } [3:7] default 2023-09-29 16:30:02.632267 +1000 AssetCacheLocatorService CFNetwork Diagnostics [3:8] 16:30:02.632 { touchConnection: (null) Loader: request POST https://lcdn-locator.apple.com/<redacted> Timeout Interval: 59.739 seconds } [3:8] default 2023-09-29 16:30:02.636661 +1000 AssetCacheLocatorService Connection 1: TLS Trust result 0 default 2023-09-29 16:30:02.636774 +1000 AssetCacheLocatorService boringssl_context_evaluate_trust_async_external_block_invoke_3(1631) [C1.1.1.1.1:2][0x816918590] Returning from external verify block with result: true default 2023-09-29 16:30:02.636935 +1000 AssetCacheLocatorService boringssl_context_certificate_verify_callback(1852) [C1.1.1.1.1:2][0x816918590] Certificate verification result: OK Can the trust mechanism for this process be adjusted to enforce certificate validation to allow for HTTPS pac file delivery.