iPadOS 17.7.7

Has super/subscripting in NSAttributedStrings been deprecated in iPadOS 13? The Objective-C code line:[attString addAttribute:(NSString*)kCTSuperscriptAttributeName value:@1 range:NSMakeRange(k, range)];works fine on my old iPad and simulators running iOS 12 and earlier, but is ignored on my iPad Pro and on simulators running any version of iPadOS 13. It isn't an Xcode 11 problem, since the same thing happens with my apps downloaded from the App Store several years ago.

I am using the following code to set the light colour for StatusBarStyle: But this code has suddenly stopped working in iOS 13 and iPadOS 13extension UINavigationController { override open var preferredStatusBarStyle: UIStatusBarStyle { get { return .lightContent } } }I have implemented UINavigationBarController with Large Titles for iOS 13 and iPadOS 13. I am using Xcode 11.4.1

I've been developing my playground within the Swift Playgrounds app on my iPad Pro for a week, but in my code RealityKit didn't work correctly. I believed my code was wrong and have been struggling to debug it for some days.Today, however, I finally found the Swift Playgrounds app crashes every time as soon as it shows the iPad's camera view, with even a simplest code including ARView. When building an app from the same code with Xcode, the app works well on my iPad.I uploaded the video to show the way it crashes: https://youtu.be/W6l83h29mJcI wanted to submit an AR app to this Swift Student Challenge, but I'm totally exhausted and have given up my submission, since we are supposed to develop a playground within the Playgrounds app in the Challenge.The simple code which doesn't work correctly is like this:import SwiftUI import UIKit import RealityKit import PlaygroundSupport let arView = ARView( frame: .zero, cameraMode: .ar, automaticallyConfigureSession: true ) let sphereMesh = MeshResource.generateSphere(r

(I know this isn't a MusicKit problem but there is no place for the iTunesLibrary SDK when saving the post.)In apps that use the iTunesLibrary SDK, I see playlists that I've deleted a long time ago. However, I don't see them in the Music app, or any of my other connected devices... (iOS, iPadOS, tvOS, watchOS.)I made a quick swift playground and confirmed that the SDK is showing them as part of the ITLibrary. I don't know where these are coming from. I've even created a brand new Library through the music app, and they are still showing up.Where is the iTunesLibrary SDK pulling these from? (Bonus points, Is that even a valid application version?)

I've created a Catalyst app that runs on WatchOS, iOS, iPadOS and MacOS. It stores some basic data in UserDefaults using Combine. The latest builds are starting to get the following error.2020-05-25 12:10:30.535305-0400 Wasted Time[82077:918516] [User Defaults] Couldn't write values for keys ( ApplicationAccessibilityEnabled ) in CFPrefsPlistSource<0x600002c15f00> (Domain: com.apple.Accessibility, User: kCFPreferencesCurrentUser, ByHost: No, 2020-05-25 12:10:30.538688-0400 Wasted Time[82077:918516] [User Defaults] Couldn't write values for keys ( AccessibilityEnabled ) in CFPrefsPlistSource<0x600002c15f00> (Domain: com.apple.Accessibility, User: kCFPreferencesCurrentUser, ByHost: No, Container: (null), Contents Need Refresh: No): setting preferences outside an application's container requires user-preference-write or file-write-data sandbox access 2020-05-25 12:10:30.539074-0400 Wasted Time[82077:918516] [User Defaults] Couldn't write values for keys ( FullKeyboardAccessFocusRingEnabled )

The iPad Pro 2020 includes a LiDAR sensor that promises precise distance measurements in the form of depth points [Apple - Newsroom - Press Release - 2020-03-18 - Apple unveils new iPad Pro with breakthrough LiDAR Scanner and brings trackpad support to iPadOS].I am looking for direct real time access to the depth data, depth points, from the LiDAR sensor at full frame rate in the same way the depth data is provided from the TrueDepthCamera on the front of the iPad Pro and other iOS and iPadOS devices.However, I have not been able to determine a method for retrieving the LiDAR depth data in an efficient way. As a result I am reaching out for clarification: is the LiDAR depth data directly available and if so how can it be accessed?Apple Developer Resources for LiDARThe following Sample Code: Visualizing and Interacting with a Reconstructed Scene, appears to be the only developer resource currently provided for utilizing the LiDAR depth data.In the VisualizingSceneSemantics example, in the Vie

I used to be able to very quickly transfer a large number (50 plus) of RAW photos (24mb each) using the Apple SD card reader to USB-C transfer to my 12.9 iPad 2018 (3rd gen.) when it ran the ORIGINAL iPadOS but with the subsequent beta updates all the way through to today's 13.5 that process now takes so long I don't even bother doing it anymore. What has changed in iPadOS that made what used to be a very fast transfer process into a too slow useless process? I used to review photos before leaving a location to make sure I got what I wanted but now I don't even bother taking my iPad with me anymore.

HelloI'm working to enable proper trackpad support for iOS 13.4+, with the new iPad Magic Keyboard. This has been a relatively straightfoward process, but I've run into an issue around Right-Click support.TLDR: I'd like to be able to tell if a UIContextMenuInteraction was triggered via a right-click from a trackpad (indirect pointer), or from a long-press from a single-tap figure gesture (direct) but that seems impossible given that you cannot navigate from the Interaction to the TouchType that invoked it.---AFAIK, right-click support in iPadOS is enabled via a UIContextMenuInteraction. The one required delegate method returns a nullable UIContextMenuConfiguration. Our app does not support UIContextMenus at this time, but we'd like to use right-clicking, so we run custom code in the delegate method prior to returning nil for the confiiguration. This all works as expected.The problem comes from the fact that now we support UIContextMenus. The interaction is added to our view, which also has a custom l