Search results for

iPadOS 17.7.7

3,646 results found

Post

Replies

Boosts

Views

Activity

Reply to Enhanced Security Capability < iOS 26
I want to highlight a couple of points in the releases notes for the software that we seeded yesterday: Xcode 26.4 Beta Release Notes documents new entitlements that allow your app to deploy back to pre-xyzOS 26 systems (search for 168185600 to find the info). iOS & iPadOS 26.4 Beta Release Notes document that hard mode is now an option (search for 160719439). I haven’t had a chance to play with this yet, but I encourage you to take it for a spin and lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
4d
Reply to Hardware Memory Tag (MIE) enforcement outside of debugger
I want to highlight a couple of points in the releases notes for stuff that we seeded yesterday: Xcode 26.4 Beta Release Notes documents new entitlements that allow your app to deploy back to pre-xyzOS 26 systems (search for 168185600 to find the info). iOS & iPadOS 26.4 Beta Release Notes document that hard mode is now an option (search for 160719439). I haven’t had a chance to play with this stuff yet, but I encourage you to take it for a spin and lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Privacy & Security SubTopic: General Tags:
4d
Support for trailing accessory views in Tab (sidebarAdaptable TabView)
In iOS 18, TabView with .tabViewStyle(.sidebarAdaptable) introduced a powerful adaptive pattern — tabs in compact, sidebar in regular. However, the current Tab API only supports a title and an image (icon). There is no way to provide a trailing accessory view (e.g., a secondary icon or indicator) for sidebar rows. This is a meaningful gap in the API, because trailing accessories are a well-established pattern throughout UIKit and SwiftUI. Precedent in Apple's own design language Apple already supports trailing accessories in many analogous contexts: UITableViewCell / UICollectionViewListCell — support accessories (disclosure indicators, checkmarks, custom views) via UICellAccessory. UIListContentConfiguration — allows leading and trailing content in list rows. SwiftUI List rows — support Label, HStack with trailing elements, .badge(), and swipeActions. NavigationLink — automatically renders a disclosure chevron as a trailing accessory. UITabSidebarItem (UIKit, iOS 18) — supports configurationUpdateHandler and
2
0
48
4d
What iPadOS version do evaluation devices run when submitted via Swift Playgrounds?
I'm working on my Swift Student Challenge 2026 submission and have a question about the evaluation environment. My app targets iOS 26 (I had to configure this on the Package.swift file directly) and uses the Speech framework for on-device speech recognition. I've selected Swift Playgrounds as my evaluation path (rather than Xcode) with the intention of having it run on a physical iPad rather than Simulator. My question: What version of iPadOS will the evaluation iPads be running? The reason I ask is practical, as my app's minimum deployment target is iOS 26. If the evaluation device is running an earlier version of iPadOS, the app won't launch at all. I've searched the eligibility and terms pages but couldn't find this documented anywhere.
1
0
69
4d
Developer Disk Image could not be mounted on this device
I have been working on a M1 Mac mini, using my iPad Air M2 running 26.3 iPadOS. Switched to a new M4 Mac mini, went to connect my iPad to run from Xcode and was presented this The developer disk image could not be mounted on this device. So how can a get an updated DDI? I appreciate any ideas. /Users/robertlawson/Desktop/Screenshot 2026-02-15 at 8.21.50 PM.png
0
0
26
5d
In-App Purchases not loading in production / TestFlight — Previously missing Paid Apps Agreement — App rejected under Guideline 3.1.2
Hello, My app was rejected on iPad (iPad Air 11-inch M3, iPadOS 26.2.1) with two related issues: Guideline 2.1 – Performance – App Completeness “The app exhibited one or more bugs that would negatively impact users. Bug description: the premium subscription cannot be loaded properly.” Guideline 3.1.2 – Business – Payments – Subscriptions “The submission did not include all the required information for apps offering auto-renewable subscriptions.” I am using StoreKit 2 with SubscriptionStoreView to present the auto-renewable subscription. During development: Subscriptions load correctly in the simulator (sandbox). On real devices, I test without a local StoreKit configuration file to fetch products from App Store Connect. The subscription UI (title, duration, price) displays correctly when products are returned. At the time of review, the Paid Apps Agreement was not active. I suspect this may have caused the subscription products to fail loading on the review device. Since then: Paid Apps Agreement is
0
0
51
1w
Reply to Xcode Simulator error
Thanks for this very interesting. I would check about the multiple returns the error is complaining about: NSMultipleUnderlyingErrorsKey=(n) I have 2 recommendations, first can you read this thread: https://developer.apple.com/forums/thread/815397?page=1#875810022 Second, I would like you to try to run this on the simulator to see if makes any difference. On the terminal: xcrun simctl status_bar clear I am sure you already went through the clearing and build and restarting the simulator. Open the Console app on your Mac and filter logs for your simulator. Look for any additional error messages or warnings that might provide more context about what's going wrong and post it here. Occasionally, beta versions of macOS and iOS/iPadOS simulators may contain bugs that have been fixed in later beta releases. So please provide me all the versions you are using. As a last resort, consider reinstalling Xcode and the simulators to ensure there aren’t any corrupted files causing the issue. Otherwise we can go ah
1w
Xcode Simulator error
Following is an error I encounter when trying to run a foundation model function in simulator. Error Domain=FoundationModels.LanguageModelSession.GenerationError Code=-1 (null) UserInfo={NSMultipleUnderlyingErrorsKey=( Error Domain=ModelManagerServices.ModelManagerError Code=1026 (null) UserInfo={NSMultipleUnderlyingErrorsKey=(n)} )} Its a swift playground I'm building in xcode and works fine in the preview and on a real device too but since it's my submission for the swift student challenge I need it to run on the simulator. I have updated my macOS to latest version of Tahoe(26.3) and Xcode is also on latest version. The simulator I run the playground is also on ios and iPadOS 26. I have set my region to US and have turned on Apple Intelligence on my mac too. Any suggestions on how to fix the issue?👾
1
0
81
1w
iPadOS 26 – SwiftUI Menu in ToolbarItem shifts during pointer hover when view is presented as sheet
I am observing inconsistent pointer hover behavior for a SwiftUI Menu placed inside a ToolbarItem on iPadOS 26.2 (real device). Scenario: • Screen A is pushed inside a NavigationStack. • Screen B is presented as a sheet (with its own NavigationStack). • Both screens contain the same toolbar Menu item using an SF Symbol (arrow.up.arrow.down). Observed behavior: In the pushed view, hover is mostly stable. In the sheet-presented view, the SF Symbol visibly shifts/jumps when pointer hover activates. The hover highlight shape differs from the native navigation back button. Label-level hoverEffect modifiers do not stabilize the behavior. Minimal example: import SwiftUI struct ContentView: View { @State private var showSheet = false var body: some View { NavigationStack { VStack { Button(Open Sheet) { showSheet = true } } .navigationTitle(Home) .toolbar { ToolbarItem(placement: .topBarTrailing) { Menu { Button(Option A) { } Button(Option B) { } } label: { Image(systemName: arrow.up.arrow.down) } } } .sheet(
Topic: UI Frameworks SubTopic: SwiftUI
0
0
30
1w
macOS: Is ARKit-equivalent face tracking possible with an external camera?
Hello, I am an individual developer working on a macOS application using SwiftUI and RealityKit. I would like to understand the feasibility of face-related tracking on macOS when using an external USB camera, compared to iOS/iPadOS. Specifically: • Does macOS provide an ARKit Face Tracking–equivalent API (e.g., real-time facial expressions, gaze direction, depth)? • If not, is it common to rely on Vision / AVFoundation as alternatives for: • Facial expression coefficients • Gaze estimation • Depth approximation • In an environment without dedicated sensors such as TrueDepth, is it correct to assume that accurate depth data and high-fidelity blend shape extraction are realistically difficult? Any clarification on official limitations, recommended alternatives, or relevant documentation would be greatly appreciated. Thank you.
0
0
37
1w
A blank keyboard appear in safari view controller
A blank keyboard appear in safari view controller Description: While clicking a password enter field in a page inside a safari view controller, keyboard will appear. However, the keyboard is blank out. The app is enterprise program app which is iPhone app but allow to install in iPad. The issue will only appear in iPadOS 26+ and it can be temporary fixed by changing the window size. Expected result: A keyboard with characters button should be appeared. Actual: A keyboard which is blank and no characters can be input. P.S. : A feedback ticket also raise : FB21921438
0
0
72
1w
IAP Purchase Fails During App Review – Circular Dependency Between App Approval and IAP Approval
Hello everyone, I’m facing an issue with In-App Purchases during App Review and would appreciate guidance from anyone who has encountered a similar situation. Context: New iOS/iPadOS app, first submission. One Non-Consumable In-App Purchase. IAP was created, fully configured, and submitted together with the app version. IAP status in App Store Connect: In Review. App includes Restore Purchase and uses standard StoreKit purchase flow. Paid Apps Agreement is accepted. Problem: During Apple’s review, when the reviewer taps the purchase button, a generic error appears: “Purchase failed. An error occurred, please try again.” Apple rejected the app under Guideline 2.1 – Performance – App Completeness, stating that the IAP shows a bug. What seems to be happening: The IAP itself is still in review and therefore not fully active, which causes the purchase attempt to fail. However, the app cannot be approved because the purchase fails, creating a circular dependency: App cannot be approved because IAP purchase
2
0
76
1w
Reply to SWİFT STUDENT CHALLANGE iOS vers
[quote='815061021, alyme, /thread/815061, /profile/alyme'] iOS 19/iPadOS 19 [/quote] There is no iOS 19 O-: You can assume that your playground will be run on a released version of iPadOS 26 / macOS 26 [1]. AFAICT the fine print doesn’t specify what type of device will be used for testing, other than to confirm that on-device intelligence will be available [2]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See my response here to the equivalent question from last year. [2] See this thread.
1w