As of iOS 17 SFSpeechRecognizer.isAvailable returns true, even when recognition tasks cannot be fulfilled and immediately fail with error “Siri and Dictation are disabled”. The same speech recognition code works as expected in iOS 16. In iOS 16, neither Siri or Dictation needed to be enabled to have SpeechRecognition to be available and it works as expected. In the past, once permissions given, only an active network connection is required to have functional SpeechRecognition. There seems to be 2 issues in play: In iOS 17, SFSpeechRecognizer.isAvailable incorrectly returns true, when it can’t fulfil requests. In iOS 17 dictation or Siri being enabled is required to handle SpeechRecognition tasks, while in iOS 17 this isn’t the case. If issue 2. Is expected behaviour (I surely hope not), there is no way to actually query if Siri or dictation is enabled to properly handle those cases in code and inform the user why speech recognition doesn’t work. Expected behaviour: Speech recognition is available when Siri and dictation is disabled SFSpeechRecognizer.isAvailable returns correctly false when no SpeechRecognition requests can be handled. iOS Version 17.0 (21A329) Xcode Version 15.0 (15A240d) Anyone else experiencing the same issues or have a solution? Reported this to Apple as well -> FB13235751

Following the recent 17.4.1 update, while QR code scanning has been resolved, we're still experiencing problems with barcode scanning on iPad devices. Specifically, the AVCaptureMetadataOutput delegate is not functioning as expected. This issue is significantly impacting our application's functionality. We kindly request immediate attention to this matter to ensure seamless operation.

We have encountered a long-standing bug on the iPad (this issue does not exist on the iPhone) that has not been fixed with iPadOS 17.4. **iPad occasionally 't receive the 'applicationDidBecomeActive' system message in AppDelegate, which leads to a series of bugs. ** The most troubling issue for us is that the Flutter engine relies on the 'applicationDidBecomeActive' message for rendering operations, resulting in a white screen in Flutter. Furthermore, through our efforts, we have found a device that can reproduce this issue. We discovered that neither the 'applicationDidBecomeActive' nor the 'applicationWillResignActive' messages are received on the iPad. We hope that Apple can expedite a fix for this issue.

From Xcode15, when Download Container in Window > Devices and Simulators for iPadOS17, an error occurs. The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = "2023-11-21 05:52:37 +0000"; NSURL = "file:///Users/administrator/Desktop/<bundle identifer>%202023-11-21%2014:52.14.006.xcappdata/AppData/Library/WebKit/WebsiteData/IndexedDB/v0"; } -- Performing a file system operation failed: Failed to open Library/WebKit/WebsiteData/IndexedDB/v0 for reading, openat(2) returned POSIX error code 62 (parentParam = 51) Domain: com.apple.dt.remoteservices.error Code: 11001 -- Failed to open Library/WebKit/WebsiteData/IndexedDB/v0 for reading, openat(2) returned POSIX error code 62 (parentParam = 51) Domain: NSPOSIXErrorDomain Code: 62 Failure Reason: Too many levels of symbolic links -- System Information macOS Version 14.0 (Build 23A344) Xcode 15.0.1 (22266) (Build 15A507) indexedDB is not used in the app. I was able to download successfully with Xcode15 and iPadOS16. I was able to download successfully with Xcode14 and iPadOS17. Why do I get an error with Xcode15 and iPadOS17?How should I fix it? That you.

0 I want to get notification like UIApplication.didBecomeActiveNotification and UIApplication.willResignActiveNotification when app switches in iPad Stage Controller Mode, but UIApplication.didBecomeActiveNotification, UIApplication.willResignActiveNotification just dont work, is there any method to get this notification

Our iPad app supports multiple windows. Currently, we use openWindow in SwiftUI to open an 'Add New Item' window so users can fill in the information of the new item by drag and drop from other apps. However, we believe it would be more intuitive and convenient for users if we could open the window in Slide Over mode, instead of having users do it themselves. Currently, a newly opened window in iPad is by default set to split view. Is there a way to achieve this? Many thanks!

It appears that when a class like the following: " class RoomCaptureViewController: UIViewController, RoomCaptureViewDelegate,ARSCNViewDelegate, MTKViewDelegate, ARSessionDelegate, RoomCaptureSessionDelegate. " has multiple delegates, the ordering of the priority of each message is delivered to a delegate by a priority sensitive order based algorithm and that one message can be processed by only one delegate and not passed off to other delegates if they don't have the proper entry points. Specifically I noted that changing the order seems to result in a delegate not getting a message that it should be seeing. Is there a "handoff" call that can be made after a delegate has seen a message but needs to pass it off to another delegate for processing? This is a protocol typically utilized in Interrupt handlers for PCIe and other messaging protocols and I have not been able to find a similar capability In the voluminous documentation available for IOS and Mac systems. I would also like to know how a message is dispatched by a class to the particular delegate for which the message was intended. Is there a detailed document that explains how the messaging protocol works that is not so fragmented as to require having multiple monitors open in order to form a coherent picture of the messaging interface for Delegates belonging to a class?

Activity image for custom activity is blank ever since iOS 17 release ,compiled in Xcode 15. The image being sent is 180x180 px. Works fine in iOS 16 running earlier Xcodes. Attached a image of the issue showing blank icons (mail and messages are the custom activities) Anyone facing the issue?

We are in the midst of testing camera and photo/video access using iPadPro 17 Beta (21A5326a) from within our application, and we are encountering an error message on only one device (iPad Pro 12.9-inch, A2229). Full access to the camera roll has been explicitly granted to the application when prompted. On only the above device, attempting to select an existing photo results in this error popup: "Photo or Video Unavailable: This app is using the Photos picker in an unsupported configuration." (We are able to take and save new photos from within our application on this device with no issues.) I have a second device on hand (iPadPro 10.5-inch, A1701) that presently also has the same iPadOS version installed and is running the same application, and we are able to select existing photos and take new photos with no errors. I have compared the Photos settings on both devices, and they appear to be identical. On a third iPad device running with the same iPadOS version, application, and Photos settings (that device is not in my possession), it has been reported that no errors are encountered when either taking new photos or selecting existing photos via the Photo Picker from within our app. We are trying to figure out what might be causing this error to appear when selecting existing photos on only the A2229 device, and/or what aspect of the configuration or settings would need to be modified in order to use the photo picker on that one iPad Pro. This issue had not been encountered on the A229 device while running with iPadOS 16. Searching the text of this error message online has not returned anything significantly meaningful thus far.

We were still unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. While we appreciate that your app is intended primarily for use on iPhone, in order to bring your app into compliance with App Store guidelines, all apps designed for use on iPhone must still be formatted correctly and behave properly when run on iPad. Review device details: Device type: iPad OS version: iOS 17.2 crashlog-82A3D8C6-0136-4C68-A006-6A4AE49B1D1C.txt crashlog-DBA3D1B0-5760-4B47-8FE7-DE44C570271A.txt crashlog-C30814D5-13BC-40FE-92EC-89E736FA7F1B.txt my app crashed only on iPad mini 6th generation its run fine on all other iPad's

I'm developing an app that works on iOS and iPadOS in Portrait mode only. I'd like it to be able to run on Apple Silicon Macs as well, but when I try running it on my Mac, the application screen it resizable to any size and any aspect ratio. (Oddly, it works fine in visionOS, where the window can be made bigger or smaller but always maintains a portrait aspect ration.) Is there some way I can have the aspect ration fixed when the app runs on macOS? Thanks!

Hi. We have weird trouble related to the multi-threading. Does anyone have ideas how to resolve or avoid? Sample Code // sample.hpp class Sample { public: Sample(); ~Sample(); void Init(); void Dealloc(); void OnEvent(); private: std::mutex sample_mutex_; int counter = 1; } // sample.cpp #include "sample.hpp" Sample::Sample() {} Sample::~Sample() {} void Sample::Init() { std::async([]() { std::this_thread::sleep_for(std::chrono::seconds(2)); this->OnEvent(); }); } void Sample::Dealloc() { std::lock_guard<std::mutex> lock(sample_mutex_); counter = 0; } void Sample::OnEvent { // called from another thread std::lock_guard<std::mutex> lock(sample_mutex_); counter += 1; } // obj_sample.h @interface ObjSample : NSObject - (id _Nonnull)init; @property(nonatomic, readonly) std::shared_ptr<Sample> sample; @end // obj_sample.mm @implementation ObjSample - (id _Nonnull)init{ if (self = [super init]) { _sample = std::make_shared<Sample>(); _sample->Init(); } return self; } - (void)dealloc { sample->Dealloc(); } @end What happens the deadlock happens. according to the debug navigator with the Xcode, we figured out 2 facts below. OnEvent does not end although it looks completed. void Sample::OnEvent { // called from another thread std::lock_guard<std::mutex> lock(sample_mutex_); counter += 1; } // <= Thread 35: stop here Sample::Dealloc is run on the same thread of OnEvent. // debug navigator Thread 35 2 Sample::Dealloc <- this is weird. 3 Sample::OnEvent We guess they causes the deadlock. probability less than 10% Environment MacOS: 14.3.1(Apple M1) Xcode: 15.3 iOS Simulator: 17.0.1

Dear Developer Community, My app is saving handwritten notes, forms and images as annotations in PDF documents by using PDFKit. Since iPadOS 17.2, the content of the annotations within the annotation boundaries is scaled down when saving the annotated PDF file. I.e. the annotation boundaries remain unchanged, but the displayed annotation content shrinks and no longer fills the boundaries. This gets worse with every save operation and applies both to newly created annotations and to elements that were saved before iPadOS 17.2. This issue only occurred after updating to iPadOS 17.2. The same code on my test device with iPadOS 17.1 works perfectly. Does anybody have a similar issue and/or found a workaround to solve this problem? Thanks for any idea!

This is a major issue. My iPad app is crashing in the App Store. In order to fix it, I found a post that recommended making the framework optional. I did so. Now I can't compile on simulator and besides, it did not fix the iPad App Store crash. ld: framework 'JournalingSuggestions' not found

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 frequently use the Universal Control feature from my Mac, the 27in, to my iPad Pro 5th gen, and recently, when I take a screenshot from my Mac and drag and drop to my tablet, the image won't appear. To be clear, I see the mouse going from the Mac to the iPad, and I see the image floating on the iPad, but when I release the image, it does not appear on the screen. I have the latest update, the Sonoma 14.4. I've searched everywhere and I honestly don't know what to do. I am not good with tech, but I don't know what else to do. In addition, I don't know if this is relevant, but my Mac does not find my iPad on Bluetooth and I have tried everything as well. I restarted it, and everything and nothing.

I'm encountering a crash in my iPad application when using Split View or Slide Over multitasking mode. The crash is occurring with the error message: Crashing on exception: child view controller:<UIPageViewController: 0x155f84200> should have parent view controller:<MyApp.HomeViewController: 0x29e040800> but actual parent is:<MyAoo.HomeViewController: 0x12d2c5e00> The issue seems to be related to incorrect parent view controller assignments when retrieving the top view controller using the window. I've tried to address this by saving the persistent identifier in UserDefaults and comparing it when retrieving the key window, but the problem persists. Here's a snippet of the code I'm using to retrieve the key window: `static func getKeyWindow(for role: UISceneSession.Role = .windowApplication) -> UIWindow? { for scene in shared.connectedScenes { guard scene.session.role == role else { continue } if let savedIdentifier = UserDefaults.standard.string(forKey: "\(scene.session.persistentIdentifier)") { debugPrint("#### saved identifier is \(savedIdentifier)") if scene.session.persistentIdentifier == savedIdentifier { return (scene as? UIWindowScene)?.windows.first { $0.isKeyWindow } } else { debugPrint("#### didn't match identifier") } } else { return (scene as? UIWindowScene)?.windows.first { $0.isKeyWindow } } } return nil }` It seems like the issue arises when the app is opened in a split view, as the persistent identifier changes but the app fails to differentiate between the different instances. Consequently, it takes the wrong Split View window and returns the wrong HomeViewController instance, leading to the crash. How can I properly handle the retrieval of the top view controller to avoid this crash in multitasking mode on iPad? Any insights or suggestions would be greatly appreciated. Thanks in advance!

This is the situation: one of the flows in our app is a navigation stack that consists of several screens. At a certain point in this flow, one of the screens lacks a back button, because we don't want the user to go back to a previous screen in that flow. For sighted users everything works fine. But once a screen reader user activates VoiceOver and uses the perform escape gesture (2 fingers right-left-right) the app does go back to the previous screen! We tried to override accessibilityPerformEscape (both in UIKit and SwiftUI) and do nothing in that method and in case of UIKit return true. That blocks going back when you're focusing on an element on the screen that belongs to the presented screen/viewController (not to the navigationBar). But once the user is focused on the navigationBar and performs the escape gesture, the user can still go back. We tried to override again the accessibilityPerformEscape on the UINavigationController level and the UINavigationBar level but they are not even called.

Hi, I have an app in the AppStore and some users reported problems when pressing a NavigationLink that leads to a new view since updating to iOS 17.4. The view that should open only contains a Text("Hello"). The strange thing is: I have to buttons leading to the same view, one is working and the other is not! Not working: NavigationLink(destination: AddServerView()) { Image(systemName: "plus.circle.fill") } Working: NavigationLink(destination: AddServerView()) { Image(systemName: "plus.circle.fill") } What is even more strange is, that the button reported working from user1 doesn't work for user2. User1 reported the problem also to be present on iPadOS 17.4. The problem never happened before iOS 17.4 and I can't reproduce any of the problems on multiple devices running iOS 17.4 including the simulator with multiple devices. I hope somebody can help in this regard or is experiencing issues like this. Kind regards