iPadOS 17.7.7

After doing the latest update of iPadOS 17 (21A5277) my iPad Pro refuse to charge But the type C OTG works well Please, who ever face this issue and how to deal with it ?

Hello, I have been trying for some time to change the color of native UITabBar in UITabBarController through UITabBarAppearance, but nothing works and the text is still black in the Xcode Beta 3 on iPadOS 26 while it works correctly in the previous OS versions. Here is the code: let color = UIColor.white let stackedAppearance = UITabBarItemAppearance() stackedAppearance.normal.iconColor = color stackedAppearance.normal.titleTextAttributes = [ .foregroundColor: color ] stackedAppearance.selected.iconColor = color stackedAppearance.selected.titleTextAttributes = [ .foregroundColor: color ] let inlineAppearance = UITabBarItemAppearance() inlineAppearance.normal.iconColor = color inlineAppearance.normal.titleTextAttributes = [ .foregroundColor: color ] inlineAppearance.selected.iconColor = color inlineAppearance.selected.titleTextAttributes = [ .foregroundColor: color ] let tabAppearance = UITabBarAppearance() tabAppearance.compactInlineLayoutAppearance = inlineAppearance tabAppearance.inlineLayoutAppear

I have an iPad Pro 10.5 inch, and he bootlooped, I tried to update and restore him on itunes, but without results, itunes reported me an error 4013, someone can explain me how can I fix him?

I would really like to see the support of widescreen 16:9 external screens- Thank you very much! Ciao Marco

Hi, When I have a UITextView displayed on screen and in focus, the iPad keyboard shows buttons to Bold, Italics and Underline text (since it supports attributed text), and also a 'formatting' button that allows the user to change the font, color and size of the text, as well as justify text and add numbered lists and bullet points. Is there any way to disable or remove this 'formatting' button? My app doesn't support saving these options (other than bold, italics and underline), so it confuses users to see this option. Thanks.

Hello, Has anyone encountered issues with CoreBluetooth advertising and scanning between iOS 18/iPadOS 18 Beta 3 ? I'm want to know this is a bug or an intended change in behavior. Issue Summary: Central device on iOS 18/iPadOS 18 Beta 3 (foreground) and Peripheral device on iOS 17.5.1 (background) fail to communicate via BLE advertising. The reverse setup or using non-iOS 18 devices works as expected. Detailed Description: I am developing an iOS/iPadOS application using CoreBluetooth for advertising and scanning. Here are the specifics of my setup: The application uses a fixed BLE service UUID, and scanning is performed with the specified service UUID. Background Modes Uses Bluetooth LE accessories and Acts as a Bluetooth LE accessory are enabled to allow advertising and scanning even when the app is in the background. When the Central device is running iOS 18/iPadOS 18 Beta 3 and the app is in the foreground scanning, and the Peripheral device is running iOS 17.5.1 with t

I have just updated to the first beta of iPadOS 13.1 and I have noticed that when I try to share anything pressing the Activity button the sharing suggestion row looks empty but, trying to interact with it, one sees that the options are only greyed out and almost invisibles.Is anyone else experiencing this?If not, is there something I could do or is there something I am forgetting or not thinking about?Thank you very much

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

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.

Crash stack as below, it don't contain the code for our App. Please check the reason, thanks. Crashed: com.apple.network.connections 0 libsystem_kernel.dylib 0x7200 __pthread_kill + 8 1 libsystem_pthread.dylib 0x71ac pthread_kill + 268 2 libsystem_c.dylib 0x20c8c abort + 180 3 libsystem_malloc.dylib 0x1df2c malloc_vreport + 908 4 libsystem_malloc.dylib 0x1e1d0 malloc_zone_error + 100 5 libsystem_malloc.dylib 0x186b0 nanov2_guard_corruption_detected + 44 6 libsystem_malloc.dylib 0x16acc nanov2_free_definite_size + 386 7 libsystem_c.dylib 0x6a08 strdup + 40 8 libxpc.dylib 0x1ee0 xpc_string_create + 20 9 libxpc.dylib 0x16a54 xpc_dictionary_set_string + 36 10 CoreFoundation 0x6fd74 _CFPrefsEncodeValueIntoMessage + 236 11 CoreFoundation 0x56494 -[CFPrefsPlistSource createSynchronizeMessage] + 692 12 CoreFoundation 0x550e4 -[CFPrefsPlistSource sendMessageSettingValues:forKeys:count:] + 136 13 CoreFoundation 0x46b10 -[CFPrefsPlistSource alreadylocked_setPrecopiedValues:forKeys:count:from:] + 1264 14 CoreFoundation 0

I am pretty new to ARKit/RealityKit and am trying to build an app that would, on an iPad or iPhone that has access to a LiDAR sensor, save the mesh data of the field of view of the seen environment and save it to a document 3D document that would later be used to make measurements as a post-processing action. For now I am unsure on how to start on saving the mesh that is visible in debugging. I am thinking about saving the ARMeshAnchors and their corresponding geometries and maybe convert the whole list into a USDZ (or similar file). Would this be the right approach or am I going completely the wrong way? Would appreciate any help! Thanks in advance