I'm currently facing an issue with my RADIUS server's EAP configuration and Apple devices. I'm using a certificate signed by "DigiCert Global Root G2", which is included in Apple's trusted store CA's (https://support.apple.com/en-us/105116). However, DigiCert uses an intermediate authority, "DigiCert Global G2 TLS RSA SHA256 2020 CA1", to sign customer certificates, and this seems to be causing a problem. When an Apple device tries to connect to the WiFi, the RADIUS server presents its certificate, but the device doesn't trust it due to the untrusted intermediate certificate. Here's my current configuration: Root CA in FreeRADIUS: "DigiCert Global Root G2" Server certificate in FreeRADIUS: "Intermediate + Server certificate" I have also tried to extend the CA with the full chain, but since the final certificate is issued by the intermediate authority, my Apple devices continue to report that they don't trust the certificate. Has anyone else experienced this issue and found a solution? It seems unlikely that DigiCert would sign certificates with their (presumably offline) root authority. Any help or suggestions would be greatly appreciated. Thanks!

I am trying to save data files between runs of an iOS App from Xcode on a real iPad (not the simulator). NSHomeDirectory gives me a different directory every time I run the app on the iPad (from XCode). I cannot write a file on one run and then retrieve it on the next run. How do I get around this annoying problem?

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

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

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.

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.

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?

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

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

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

Still no hypervisor support in iPadOS 17 Hypervisor is indeed physically possible on any of the M series chips included in the iPad Airs and iPad Pros, but locked away the iPadOS. Block hypervisor on iOS is reasonable to me, because it consume powers, not frendly for battery and not sutable for a mobile phone. But for iPadOS, the limitation is not reasonable to me. First, the Guideline 2.5.2 of iOS and iPadOS blocks code execution that loads dynamically, it may protect users because apps may load malicious code after it passes the revew from app store. But if we load codes in the hypervisor, any malicious can only run in the VM, and the safety of the VM is not an issue. Escape from a VM is even harder than escape from the sandbox of the safari browser. Even there are still other concerns about load arbitrary codes to hypervisor, we can limit it only load user selected code to the hypervisor, blocks app load code from interent without user intention. Running user selected code in the hypervisor won't threaten the security at all, there is no reason for Guideline 2.5.2 applies to hypervisor. Second, iPad a laptop replacement in the advertisement. As a laptop, it can't execute any user generated code on it, it can only be interpreted. As a software develper, it means iPadOS basically not useable. I can only run code on a remote server, and use iPad as a thin client. It can't be a standalone devices, even it has a powerful M2 chip. For the xcode on iPad, if apple concerns xcode on iPad breaks the security model, we can run the compiled code in the hypervisor, which isolates the reviewed code and user generated code. iPad has a powerful M2 chip, but iPadOS limit the power for it.