Hello, I’m currently working on Tiny ML or ML on Edge using the Google Colab platform. Due to the exhaust of my compute unit’s free usage, I’m being prompted to pay. I’ve been considering leveraging the GPU capabilities of my iPad M1 and Intel-based Mac. Both devices utilize Thunderbolt ports capable of sharing connections up to 30GB/s. Since I’m primarily using a classification model, extensive GPU usage isn’t necessary. I’m looking for assistance or guidance on utilizing the iPad’s processor as an eGPU on my Mac, possibly through an API or Apple technology. Any help would be greatly appreciated!

I have an extremely simple SwiftUI View with two buttons. One displays a sheet, the other one a popover. struct ContentView: View { @State private var showPopover = false @State private var showSheet = false var body: some View { VStack { Button("Popover") { showPopover = true } .popover(isPresented: $showPopover, content: { Text("Popover content") }) Spacer() Button("Sheet") { showSheet = true } } .padding() .sheet(isPresented: $showSheet) { Text("Lorem Ipsum") } } } On iPadOS, when the Popover is visible and the "Sheet" Button (that looks disabled but is not) is pressed, nothing happens and I get the following log: Attempt to present <TtGC7SwiftUI29PresentationHostingControllerVS_7AnyView: 0x14508c600> on <TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_12RootModifier_: 0x14501fe00> (from <TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_12RootModifier_: 0x14501fe00>) which is already presenting <TtGC7SwiftUI29PresentationHostingControllerVS_7AnyView: 0x140023e00>. What's even worse is, the "Sheet" Button is now in a broken state and no longer works at all. Is there a way to fix this or am I right in assuming this is a bug?

Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.) Here is what the detailed error message shows: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.) User Info: { DDIPath = "/Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; DVTErrorCreationDateKey = "2024-07-12 19:06:25 +0000"; DeviceIdentifier = "94430B68-BA12-4F63-9EE5-48EE865738D6"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; NSURL = "file:///Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; Options = { MountedBundlePath = "file:///private/var/tmp/CoreDevice_DDI_Staging_501/94430B68-BA12-4F63-9EE5-48EE865738D6/"; UseCredentials = 0; }; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } Error mounting image: 0xe8000105 (kAMDMobileImageMounterTATSUDeclinedAuthorization: The server declined to authorize this image on this device for this user.) Domain: com.apple.mobiledevice Code: -402652923 User Info: { FunctionName = AMDeviceRemoteMountPersonalizedBundle; LineNumber = 2135; } AMAuthInstallRequestSendSync failed: 3194 (kAMAuthInstallTATSUDeclinedAuthorization) Domain: com.apple.mobiledevice Code: -402652923 User Info: { FunctionName = "-[PersonalizedImage mountImage:]"; LineNumber = 2032; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_identifier" = "00008027-000164500AE2402E"; "device_isCoreDevice" = 1; "device_model" = "iPad8,12"; "device_osBuild" = "18.0 (22A5307f)"; "device_platform" = "com.apple.platform.iphoneos"; "device_thinningType" = "iPad8,12"; "dvt_coredevice_version" = "397.3.5.2"; "dvt_coresimulator_version" = 980; "dvt_mobiledevice_version" = "1757.0.0.101.1"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 1332838; "operation_errorCode" = "-402652923"; "operation_errorDomain" = "com.apple.dt.CoreDeviceError.12040.com.apple.mobiledevice"; "operation_errorWorker" = IDEInstallCoreDeviceWorker; "operation_name" = IDERunOperationWorkerGroup; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_113575882_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos18.0"; "sdk_osVersion" = "18.0"; "sdk_variant" = iphoneos; } System Information macOS Version 14.5 (Build 23F79) Xcode 16.0 (23037.4) (Build 16A5171r) Timestamp: 2024-07-12T12:06:25-07:00

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 the app in the background advertising, the Central device cannot receive the advertisements from the Peripheral device. ( CBCentralManagerDelegate.centralManager(_:didDiscover:advertisementData:rssi:) don't work.) In the reverse scenario (Central on iOS 17.5.1 in the foreground scanning, and Peripheral on iOS 18/iPadOS 18 Beta 3 in the background advertising), the advertisements are received correctly. Additionally, advertisements are received correctly in cases where both devices are not on iOS 18/iPadOS 18. I am wondering if anyone else has encountered this issue or if there is any information available regarding whether this is a bug or an intended behavior change in iOS 18/iPadOS 18. Thank you.

The cursor is moved by the app in a Text area. iPadOS allows touch screen cursor movement to cut, copy, paste and insert text. When text is highlighted via handle controls, and cut requested, the app fails with cursor out of bounds. The app cursor was not moved in sync with IOS. It is obvious IOS does not sync with the app cursor position and the update of the endIndex.

Dear Apple Support Team, I am currently developing a control in my app that uses UIDatePicker for time input. To ensure that the time display format is consistently in 24-hour notation regardless of the region, I have set the locale of UIDatePicker to ‘systemLocale’. However, while this worked as expected up to iPadOS15, displaying the time in 24-hour format, it has switched to a 12-hour format from iPadOS16 onwards. I am wondering if there have been any changes in the behavior of UIDatePicker’s locale between the updates from iPadOS15 to iPadOS16? Additionally, I would like to know if there are any workarounds to this issue that do not involve modifying the program. In other words, is there a way to revert back to the 24-hour format without changing the code? Any information you could provide on this issue would be greatly appreciated. Thank you for your assistance.

Hello Apple, I am concerned about the new iOS Screen Mirroring that is available on iOS. I have an app that is only meant to be viewed on iPhones (not Macs or Computers, due to security reasons. I am assuming that Screen Mirroring is using AirPlay underneath, otherwise is there an API being planned or coming that can disable this functionality or is there a way for my app to opt out out of iOS Screen Mirroring? Thanks.

App is Xcode swiftUI on iPad using textview. The cursor is invisible yet it moves "underneath". How to make it visible. The app textview input is button characters and coexists with a Magic Keyboard where the cursor is visible.

I think iPad models with only WiFi need to have an sos or emergency calling feature Incase of any emergency.

I'd like to use the eye tracking feature in the latest iPadOS 18 update as more than an accessibility feature. i.e. another input modality that can be detected by event + enum checks similar to how we can detect and distinguish between touches and Apple pencil inputs. This might make it a lot easier to control and interact with iPad-based AR experiences that involve walking around, regardless of whether eye-tracking is enabled for accessibility. When walking, it's challenging to hold the device and interact with the screen with touch or pencil at all. Eye tracking + speech as input modalities could assist here. Also, this would help us create non-immersive AR experiences that parallel visionOS experiences that use eye tracking. I propose an API option for enabling eye-tracking (and an optional calibration dialogue within-app), as well as a specific UIControl class that simply detect when the eye looks at the control using the standard (begin/changed/end) events. My specific use case is that I'd like to treat eye-tracking-enabled UI elements or game objects differently depending on whether something is looked at with the eyes. For example, to select game objects while using speech recognition, suppose we have 4 buttons with the same name in 4 corners of the screen. Call them "corner" buttons. If I have my proposed invisible UI element for gaze detection, I can create 4 large rectangular regions on the screen. Then if the user says "select the corner" the system could parse this command and disambiguate between the 4 corners by checking which of the rectangular regions I'm currently looking at. (Note: the idea would be to make the gaze regions rather large to compensate for error.) The above is just a simple example, but the advantage over other methods like dwell is that it could be a lot faster. Another simple example: Using the same rectangular regions, instead of speech input, I could hold a button placed in just one spot on the screen, and look around the screen with my gaze to produce a laser beam for some kind of game, or draw curves (that I might smooth-out to reduce inaccuracy). OR maybe someone who does not have their hands available. This would require us to have the ability to get the coordinates of the eye gaze, but otherwise the other approach of just opting to trigger uicontrol elements might work for coarse selection. Would other developers find this useful as well? I'd like to propose this feature in feedback assistant, but I'm also opening-up a little discussion if by chance someone sees this. In short, I propose: a formal eye-tracking API for iPadOS 18+ that allows for turning on/off the tracking within the app, with the necessary user permissions the API should produce begin/changed/ended events similar to the existing events in UIKit, including screen coordinates. There should be a way to identify that an event came from eye-tracking. alternatively, we should have at minimum an invisible UIControl subclass that can detect when the eyes enter/leave the region.

IpadOS18.0 在主屏幕上有一个错误。请做好准备。只有一种方法可以解决它---重新启动系统。

I'd like to create meshes in RealityKit ( AR mode on iPad ) in screen-space, i.e. for UI. I noticed a lot of useful new functionality in RealityKit for the next OS versions, including the OrthographicCameraComponent here: https://developer.apple.com/documentation/realitykit/orthographiccameracomponent?changes=_3 I think this would help, but I need AR worldtracking as well as a regular perspective camera to work with the 3D elements. Firstly, can I have a camera attached selectively to a few entities, just for those entities? This could be the orthographic camera. Secondly, can I make it so those entities are always rendered in-front, in screenspace? (They'd need to follow the camera.) If I can't have multiple cameras, what can be done in that case? Is it actually better to use a completely different view / API for layering on-top of RealityKit? I would much rather keep everything in RealityKit, however, for simplicity.

See FB13917278 (App Becomes Unresponsive for iOS/iPadOS 18 Regular Size Class Interactions When Selecting One Particular View in Sidebar).

Hello everyone. Is iPadOS18’s Eye-tracking feautre available on iPad Pro 12.9” 2018? If not, where can I find the compatible devices where Eye-tracking available?

Hello im on IPadOS 18 developer beta version 1 and when i connect to my managed wallpaper instead of it changing the wallpaper to the managed one it becomes plain green, how do i fix this

Was it a typo on the Website or why is the 2017 10.5 inch iPad Pro (A10X + 4GB of ram) not supported? Because the 7th generation iPad which has an A10 processor + 3GB of ram is supported! It’s weird because the A10X is a more powerful processor so why does it not make the cut?

Hi all, I am currently working on a user interfacing using SwiftUI where I have created custom button cards which have a mask modifier containing a RoundedRectangle with a corner radius of 15. The cards are displayed properly in the interface but when hovering over card with the iPad cursor using the hoverEffect() modifier or tapping and holding to show a context menu the corners aren't rounded and you can see a space where the rounded corners should be. Thanks! Here is the code for the custom card. var body: some View { Button(action: {}) { ZStack { Color("MainColor") VStack(spacing: 20) { Spacer() Text("Card content here") .font(.largeTitle) .bold() Spacer() } .padding() } } .contentShape(RoundedRectangle(cornerRadius: 15, style: .continuous)) .buttonStyle(.plain) .mask(RoundedRectangle(cornerRadius: 15)) .contextMenu { Button(action: {}) { Label("Edit", systemImage: "pencil") } Button(role: .destructive) { // Edit goes here } label: { Label("Delete", systemImage: "trash") } } .hoverEffect() }

For accessibility dev purposes, I am trying to move the iPadOS (17.4) pointer via virtual mouse and keyboard events generated via pynput. All keyboard keys, mouse click events, and scroll events are registered when relayed to the iPad and works as expected, except for mouse position and move events. Is this something iPadOS blocks specifically or is there a work around? Thanks in advance

can the example from Support external cameras in your iPadOS app work on IOS 17.5 Iphone 15PRO ? https://developer.apple.com/videos/play/wwdc2023/10106/

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!