iPadOS 17.7.7

Hello, When creating an app with side bar for iPadOS using SwiftUI, when in dark mode the color of the sidebar and the detail view is indistinguishable. When running in light mode the sidebar has a distinct color. Just build and run the Fruta sample app and you can notice the issue. I tried adding something like .background(Color.gray) to the list but it has no effect. I compared with the Files app on iPad, and the side bar in that app is a grey color which clearly separates the side bar from the detail content. Is this a known issue? Are there any customisation modifiers that can set the background color? Thanks! Best Regards, Filip

I have successfully used the primaryPresentedItemURL functionality of NSFilePresenter in macOS apps to, write to file.foo after the user used, for example, NSOpenPanel to open file.bar in a sandboxed application. This makes use of the primaryPresentedItemURL property belonging to NSFilePresenter (as well as NSIsRelatedItemType in Info.plist). I am struggling to do the same on an iOS/iPadOS app and not sure whether that can be done. primaryPresentedItemURL is not available outside of macOS. When I try to use the same approach as macOS (except for primaryPresentedItemURL of course), it works on the Simulator, but not on an actual device. Can this be done in some other way? My internet search has not revealed a solution. Thanks in advance!!

In ARKit+RealityKit I do a raycast from the ARView's center, then create an AnchorEntity at the result and add a target ModelEntity (a flattened cube) to the AnchorEntity. guard let result = session.raycast(query).first else { return } let newAnchor = AnchorEntity(raycastResult: result) newAnchor.addChild(placementTargetEntity) arView.scene.addAnchor(newAnchor) I repeat this for each frame update via the ARSessionDelegate session(_:didUpdate:), removing the previous AnchorEntity first. I use this as a target to let the user know where the full model will be placed when they tap the screen. This works find under iOS 14, but I get strange results with iPadOS 15 - two different placements are created on different screen updates, offset from each other and slightly rotated from each other. Has anyone else had issues with raycast() or creating an AnchorEntity from the result? Is the use of session(_:didUpdate:) via ARSessionDelegate to update virtual content considered bad style now? (I noticed in the WWD

Our app is an enterprise app via MDM. We are experiencing an issue in iPadOS 18.4 when loading an internal HTTPS server via WKWebView in a hybrid iOS app. Our server uses a self-signed certificate but lacks the digitalSignature usage in its Key Usage extension. (Currently we have no chance to change the server's certificate) We override webView:didReceiveAuthenticationChallenge:completionHandler: to trust the certificate: completionHandler(NSURLSessionAuthChallengeUseCredential, credential); This completionHandler works in previous 18.3.2 , but not work in 18.4. May I know is there any changes in 18.4 for the https certification? Why this delegate not work? What we can do to ignore this ssl error and get connection? Thanks in advance, look forward for your reply.

Hello Community,I've been using the public beta 2 version the iPadOS 13 and I have an really bad problem that really makes it hard to use my iPad.The problem is that most applications and the system itself are not responsive and crash the iPad the home screen and safari function well so far and it's really hard to cope with it until its fixed.If anyone knows how to cope with this problem please reply!

NOTE: iOS 15 did not have this issue. If you enabled pointer capture then hit Esc key. It will disable pointer-capture BUT will also resize sub-UIViews used for capture. Then pointer-capture never works again in the app until you RESTART the iPad. (force-quitting app and restarting doesn't work) Tested with iPadOS 16.3 & iPad 10th gen

We are Java application developers and we have a question regarding camera access via WebRTC on iPadOS. Specifically, on iPadOS 17.1, we are encountering an issue when trying to access the camera via the WKWebView API in the Chrome browser, where an error occurs and the camera capture fails. Our investigation suggests that device access through the navigator.mediaDevices property via the WKWebView API may not work in Chrome. However, it works as expected in the Safari browser, leading us to wonder if this is a Chrome-specific limitation, or if it's due to an iPadOS setting or specification. At this point, we are unsure if this issue is related to the WKWebView and WebRTC specifications on iPadOS 17.1, or if there are specific limitations in Chrome. We would appreciate any insights or solutions regarding camera access in iPadOS 17.1 with WKWebView and WebRTC, especially in relation to Chrome.