Will you be able to run the full version of Xcode on the new iPad Pro M4 on IPadOS?

I see that there's an updated requirement for iPad screenshots (iPad 13"), but there's no info on the screenshot specs page and the device bezels are outdated

Hello, I have an iOS app that is recording audio that is working fine on iPads/iPhones. It asks for microphone permission and after that recording works. I installed the same app on my M3 MacBook via TestFlight since iPad apps are supposed to work without a change that way. The app starts fine and everything, but it never asks for Microphone permission, so I can't record. Do I need to do something to make this happen (this is not macCatalyst, its running the arm64 iPhone binary on macOS) thanks

I wonder if an Apple engineer could confirm: will the Apple Pencil Pro squeeze functionality be detectable in the current API, or will this be a future iPadOS extension to gesture recognizers / UIKit? I’d like to start playing with the functionality if it’s detected behind an existing event though. (Long press?)

I have a iPad mini4 with iPadOS 15.8.2. I try to Install iPadOS 17.5 beta 4. But I can't succeed in installing the program. I read the documents related to iPadOS 17.5 beta 4 in Apple Developer Program. According to the instructions, I repeated to install the profile to my mini4 by various ways, but in vain. I made inquiries to Apple Care and Apple Developer Support, but they said they gave me some advices that they could have in their resources. They told me my operations seemed to be correct in order to install the profile related to iPadOS 17.5 beta 4 for the machines with iPadOS 16.3 and earlier. They also basically told me they didn't know why and how on a beta program and to go to Developer Forums and post my problem in Developer Forum. I have also have M2Macbook Pro, iPad9, SE3. "Beta Updates"s appear in Three System Settings but only "Automatic Updates" appears in mini4. It is sure to enter a Developer Mode on my Apple ID. How should I do in order to install the profile for iPadOS 17.5 beta 4 ? Please tell me how.

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