Discuss hardware-specific topics related to iPad.

Posts under iPad tag

75 Posts

Post

Replies

Boosts

Views

Activity

Navbar buttons disappear in NavigationSplitView's sidebar when changing apps
We recently migrated our app to use NavigationSplitView on iPad with a sidebar and detail setup, and we got reports that the navigation buttons on the sidebar disappear when returning to our app after using a different app. I reproduced the issue from a new empty project with the following code (issue tested on iOS 17.4 and iOS 18.3, was not able to reproduce on iOS 16.4): import SwiftUI @main struct TestApp: App { var body: some Scene { WindowGroup { NavigationSplitView { Text("sidebar") .toolbar { ToolbarItem(placement: .topBarLeading) { Button(action: {}) { Image(systemName: "square.and.arrow.down") } } ToolbarItem(placement: .topBarTrailing) { Button(action: {}) { Image(systemName: "square.and.arrow.up") } } } } detail: { Text("detail") .toolbar { ToolbarItem(placement: .topBarLeading) { Button(action: {}) { Image(systemName: "eraser") } } ToolbarItem(placement: .topBarTrailing) { Button(action: {}) { Image(systemName: "pencil") } } } } } } } Please check the following GIF for the simple steps, notice how the navbar buttons in the detail view do not disappear: Here's the console output, it shows that the constraints break internally:
0
0
130
Apr ’25
Unable to Install Provisioning profile
Hi, I'm unable to install provisioning profile on my iPad and I know the xcode component iOS/iPadOs version and iPadOS version should be same or below the latest compared to xcode components. Now the issue is xcode component version is iOS 18.4 (22E235) SDK + iOS 18.4 (22E238) Simulator (Installed) and iPadOS version is iOS 18.4.1(22E252) could this be cause of issue ? If yes then when will apple release components for 18.4.1? Because iOS 18.4.1 release at least 3-4 weeks before this post.
0
0
115
May ’25
Question regarding ethernet over USB-C
Hello, I have a question regarding the ethernet-over-USB-C stack within iOS/iPadOS. It seems that when manually assigning an IP on this interface within iOS, the IP is stored. Therefore, when disconnecting (the USB-C cable) and reconnecting to another device for a subsequent ethernet connection, the iOS device will always default to the previously assigned IP address (obviously, this isn't the case if the other end is a DHCP server). So, within the iPhone's Ethernet-over-USB-C driver, I was curious if iOS just keeps the assignment based on the MAC of the local USB-C interface, or is stored information tied to some other identifier? Is there a way to override this behavior? Thank you
0
0
79
Jun ’25
How to hide moreNavigationController in SwiftUI?
I have more than five tabs in a TabView, and on some screens, I'm seeing a navigation bar with the title "More". I understand that this is the default behavior of TabView when there are more than five tabs—iOS automatically creates a "More" screen. I've set navigationBarHidden = true throughout my app, but the navigation bar still appears on some screens within the "More" section. Is there another way to hide the moreNavigationController or completely remove the navigation bar from the "More" screen?
0
0
148
Jul ’25
iPadOS 26 TabBar text color can't be changed
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.inlineLayoutAppearance = inlineAppearance tabAppearance.stackedLayoutAppearance = stackedAppearance UITabBar.appearance().standardAppearance = tabAppearance UITabBar.appearance().scrollEdgeAppearance = tabAppearance
0
5
486
Jul ’25
4 or 5 Finger Gestures on iPadOS 26
I disable 4 or 5 Finger Gestures on Settings.app > Multi-tasking and Gestures. But in the third-party apps, 4-5 finger touches are sometimes immediately cancelled. Especially, 4-5 finger swipe gesture. I filed this issue to FB19226717. I develop Piano instrument app. 4 or 5 finger touches are required for that kind of apps. Please fix this, Apple.
0
0
162
Jul ’25
Corrupt IOS Beta 4 and iPad
Hi, Have done the update for IOS Beta 4 and after it was done the screen just had the background and no icons. Couldn't get to any of the icons. Tried to do a restore on the iPad from my Mac and it started the restore but then got the message that it errored out and gave me this: Need help trying to get this fixed. Also tried a computer that wasn't in the beta and got the same error message. Tried to turn it off and then see if it would go back to the error before and it just stays in recovery mode. Please help. Thank you.
0
0
153
Jul ’25
Extending the display on my iPad 11th gen (2025) on iPadOS 26 beta 3
Hi! I am very new to the apple ecosystem. I saw a lot of comments online about how Stage Manager enabled iPads have access to extending the screen to an external display, and that was what hyped me about this beta. Unfortunately, while i do have Stage Manager now, the display is still unwilling to be extended. Is that a feature that’s planned to be included in the OS? Or am i just out of luck? The ipad is one of the most capable devices i have so i was kind of hoping it would get the feature. It has an A11 chip.
0
0
144
Aug ’25
IOS cursor control
My app controls the cursor movement in a text view on iPhone and iPads. On screen touch, the IOS cursor position is out of sync with the app cursor position. Is there a way to find out, on screen touch, where the ios cursor positition is and update the app cursor to the ios cursor position? When they are out of sync, the user has to move the cursor to the startIndex and navigate from there. Frustating! I have looked at many programming books, forums, and internet search with nothing to no avail. Any help will be greatly appreciated. The app names are SummaGramPhonex and SummaGramIPAD11 and SummaGramIPAD13. Thanks. Charlie 3Sep25
0
0
220
Sep ’25
iPadOS 26 Floating Keyboard jumping up and down
Using the floating keyboard extensively. Often It starts to jump up and down. I have to pinch out to see the large version and pinch in again to restore the floating version. Sometimes just touching a key sets it off. Sometimes returning to a window from which the keyboard is displayed starts the issue. This was never a problem in ipad os 18.
0
0
503
Sep ’25
TestFlight app crashes since iOS 26 released
App builds fine locally on iPad. Once released to TestFlight, the app crashes on startup. Can't even release previous builds to TestFlight that worked fine before iOS 26. Using .net Maui 8.0.413 and Xcode 16.4. IpadOS 18.6 Crash log: Incident Identifier: 2183463F-CAFD-4E0C-95FB-8E56876118E9 Distributor ID: com.apple.TestFlight Hardware Model: iPad15,7 Process: VS_NASCO_Auscultation [3576] Path: /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation Identifier: com.NASCO.Auscultation Version: 2.8.04 (20) AppStoreTools: 17A323 AppVariant: 1:iPad15,7:18 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.NASCO.Auscultation [2590] Date/Time: 2025-09-22 14:31:29.9710 -0500 Launch Time: 2025-09-22 14:31:27.7714 -0500 OS Version: iPhone OS 18.6 (22G86) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: VS_NASCO_Auscultation [3576] Triggered by Thread: 0 Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001df60f1dc __pthread_kill + 8 1 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 3 VS_NASCO_Auscultation 0x0000000105157294 0x102e5c000 + 36680340 4 VS_NASCO_Auscultation 0x00000001050cb930 mono_runtime_setup_stat_profiler + 0 (mini-posix.c:690) 5 libsystem_platform.dylib 0x0000000218b40a68 _sigtramp + 56 (sigtramp.c:116) 6 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 7 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 8 VS_NASCO_Auscultation 0x0000000104f91170 mono_log_write_os_log + 408 (mono-log-darwin.c:0) 9 VS_NASCO_Auscultation 0x0000000104f8644c monoeg_g_logv + 172 (goutput.c:173) 10 VS_NASCO_Auscultation 0x0000000104f86594 monoeg_g_log + 28 (goutput.c:184) 11 VS_NASCO_Auscultation 0x00000001050a5f84 load_aot_module + 3172 (aot-runtime.c:2365) 12 VS_NASCO_Auscultation 0x0000000104fe4f48 mono_assembly_request_load_from + 1104 (assembly.c:2020) 13 VS_NASCO_Auscultation 0x0000000104fe4a68 mono_assembly_request_open + 472 (assembly.c:1625) 14 VS_NASCO_Auscultation 0x0000000104fe5cec mono_assembly_open + 80 (assembly.c:1828) 15 VS_NASCO_Auscultation 0x0000000104e1a0ac xamarin_assembly_preload_hook + 884 (monotouch-main.m:157) 16 VS_NASCO_Auscultation 0x0000000104fe6800 invoke_assembly_preload_hook + 64 (assembly.c:1283) 17 VS_NASCO_Auscultation 0x0000000104fe41e4 mono_assembly_request_byname + 1060 (assembly.c:2786) 18 VS_NASCO_Auscultation 0x00000001050af2e0 load_image + 280 (aot-runtime.c:325) 19 VS_NASCO_Auscultation 0x00000001050a5f1c load_aot_module + 3068 (aot-runtime.c:2358) 20 VS_NASCO_Auscultation 0x00000001050aa71c mono_aot_get_method + 292 (aot-runtime.c:4920) 21 VS_NASCO_Auscultation 0x000000010509e924 mono_jit_compile_method_with_opt + 472 (mini-runtime.c:2759) 22 VS_NASCO_Auscultation 0x000000010509cd10 mono_jit_runtime_invoke + 572 (mini-runtime.c:3525) 23 VS_NASCO_Auscultation 0x0000000105044b74 mono_runtime_invoke_checked + 148 (object.c:2792) 24 VS_NASCO_Auscultation 0x0000000105001720 create_exception_two_strings + 592 (exception.c:177) 25 VS_NASCO_Auscultation 0x00000001050014a4 mono_exception_from_name_two_strings_checked + 148 (exception.c:236) 26 VS_NASCO_Auscultation 0x0000000104fe0ab0 mono_runtime_init_checked + 708 (appdomain.c:288) 27 VS_NASCO_Auscultation 0x000000010509c64c mini_init + 6648 (mini-runtime.c:4889) 28 VS_NASCO_Auscultation 0x00000001050a3ad8 mono_jit_init_version + 20 (driver.c:2823) 29 VS_NASCO_Auscultation 0x0000000104e157ac xamarin_bridge_initialize + 216 (monovm-bridge.m:88) 30 VS_NASCO_Auscultation 0x0000000104e1a968 xamarin_main + 1784 (monotouch-main.m:438) 31 VS_NASCO_Auscultation 0x00000001051033ec main + 72 (main.arm64.mm:236) 32 dyld 0x00000001b58e5f08 start + 6040 (dyldMain.cpp:1450) Thread 1: 0 libsystem_pthread.dylib 0x0000000218be9aa4 start_wqthread + 0 Thread 2: 0 libsystem_kernel.dylib 0x00000001df60a438 __psynch_cvwait + 8 1 libsystem_pthread.dylib 0x0000000218beae50 _pthread_cond_wait + 984 (pthread_cond.c:862) 2 VS_NASCO_Auscultation 0x0000000104fdde4c thread_func + 412 (sgen-thread-pool.c:195) 3 libsystem_pthread.dylib 0x0000000218bec344 _pthread_start + 136 (pthread.c:931) 4 libsystem_pthread.dylib 0x0000000218be9ab8 thread_start + 8 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0xffffffff9838bfdf x5: 0x0000000000000018 x6: 0x000000016cfa0730 x7: 0x000000016cf9fe20 x8: 0x9b8f66cd52cb42ec x9: 0x9b8f66ccab4b5cec x10: 0x00000000000003ff x11: 0x000000016cf9fe98 x12: 0x0000000000000000 x13: 0x00000001031e01a0 x14: 0x00000001a960913c x15: 0x00000001a960be20 x16: 0x0000000000000148 x17: 0x00000001f9801e00 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f9801ee0 x22: 0x0000000000000010 x23: 0x000000000000000b x24: 0x0000000000002788 x25: 0x0000000105687624 x26: 0x000000010553ea10 x27: 0x000000010a6a0880 x28: 0x00000000000003c8 fp: 0x000000016cfa0740 lr: 0x0000000218bf0c60 sp: 0x000000016cfa0720 pc: 0x00000001df60f1dc cpsr: 0x40001000 esr: 0x56000080 Address size fault Binary Images: 0x102e5c000 - 0x10535bfff VS_NASCO_Auscultation arm64 <9b9a7de8b40b303bbc3d1a11686bb1dc> /var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation 0x109498000 - 0x1099fbfff libSkiaSharp arm64 /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/Frameworks/libSkiaSharp.framework/libSkiaSharp 0x196e23000 - 0x196ea26c3 libsystem_c.dylib arm64e <335cd87d234b3fc182db943350d31a88> /usr/lib/system/libsystem_c.dylib 0x1b58a7000 - 0x1b594187b dyld arm64e /usr/lib/dyld 0x1df604000 - 0x1df63debf libsystem_kernel.dylib arm64e /usr/lib/system/libsystem_kernel.dylib 0x218b3e000 - 0x218b458cf libsystem_platform.dylib arm64e /usr/lib/system/libsystem_platform.dylib 0x218be9000 - 0x218bf53f3 libsystem_pthread.dylib arm64e <1ee1922008593cbcbdebdf37ca2e8e4f> /usr/lib/system/libsystem_pthread.dylib EOF
0
0
293
Sep ’25
PaperKit: Correct approach for multi-page or infinite-canvas documents?
I’m trying to figure out how to extend PaperKit beyond a single fixed-size canvas. From what I understand, calling PaperMarkup(bounds:) creates one finite drawing region, and so far I have not figured out a reliable way to create multi-page or infinite canvases. Are any of these correct? Creating multiple PaperMarkup instances, each managed by its own PaperMarkupViewController, and arranging them in a ScrollView or similar paged container to represent multiple pages? Overlaying multiple PaperMarkup instances on top of PDFKit pages for paged annotation workflows? Or possibly another approach that works better with PaperKit’s design? I mean it has to be possible, right? Apple's native Preview app almost certainly uses it, and there are so many other notes apps that get this behavior working correctly, even if it requires using a legacy thing other than PaperKit. Curious if others have been able to find the right pattern for going beyond a single canvas.
0
0
144
Nov ’25
Should TabView with .page style support keyboard left/right navigation automatically?
I’m trying to understand the expected behavior of TabView when using .tabViewStyle(.page) on iPadOS with a hardware keyboard. When I place a TabView in page mode, swipe gestures correctly move between pages. However, left and right arrow keys do nothing by default, even when the view is made focusable. This feels a bit surprising, since paging with arrow keys seems like a natural keyboard interaction when a keyboard is attached. Right now, to get arrow-key navigation working, I have to manually: Make the view focusable Listen for arrow key presses Update the selection state manually This works, but it feels a little tedious for something that seems like it could be built-in. import SwiftUI struct PageTabsExample: View { @State private var selection = 0 private let pageCount = 3 var body: some View { TabView(selection: $selection) { Color.red.tag(0) Color.blue.tag(1) Color.green.tag(2) } .tabViewStyle(.page) .indexViewStyle(.page) .focusable(true) .onKeyPress(.leftArrow) { guard selection > 0 else { return .ignored } selection -= 1 return .handled } .onKeyPress(.rightArrow) { guard selection < pageCount - 1 else { return .ignored } selection += 1 return .handled } } } My questions: Is this lack of default keyboard paging for page-style TabView intentional on iPadOS with a hardware keyboard? Is there a built-in way to enable arrow-key navigation for page-style TabView, or is manual handling the expected approach? Does my approach above look like the “SwiftUI-correct” way to do this, or is there a better pattern for integrating keyboard navigation with paging? For this kind of behavior, is it generally recommended to use .onKeyPress like I’m doing here, or would .keyboardShortcut be more appropriate (for example, wiring arrow keys to actions instead)? Any guidance or clarification would be greatly appreciated. I just want to make sure I’m not missing a simpler or more idiomatic solution. Thanks!
0
0
196
Dec ’25
App Launchscreen Size NOT Correct on iPadOS 26
Hello, We’re seeing an iPad-specific Launch Screen issue related to multitasking window sizes. Environment Device: iPad (iPadOS 26) Device orientation: Landscape App is launched in a small window where the app window is portrait-shaped (width < height) Issue When the iPad is in landscape but the app is launched as a portrait-shaped small window, the LaunchScreen.storyboard appears to be rendered/layouted as landscape, not matching the actual window geometry. As a result, the Launch Screen content is clipped / partially missing (we see blank/empty area at the bottom during launch). After the app finishes launching, our first view controller uses the correct window size and the UI looks fine — the problem is mainly during the Launch Screen phase. What we checked LaunchScreen.storyboard uses Auto Layout and is expected to adapt to screen/window size. This only reproduces when the device orientation and the app window aspect ratio don’t match (landscape device + portrait-shaped app window, or vice versa). When device orientation and window shape are aligned, the Launch Screen displays correctly. Question Is it expected that iPadOS renders LaunchScreen.storyboard based on the interface orientation / size class rather than the actual window bounds in multitasking scenarios? If not expected, what is the recommended way to ensure the Launch Screen matches the app’s actual window size/aspect ratio at launch (without using code, since Launch Screen is static)? Are there any additional diagnostics or recommended steps to help us investigate and confirm the root cause (e.g., specific logs, APIs/values to capture at launch such as UIWindowScene bounds, interfaceOrientation, size classes, or any guidance on how Launch Screen snapshots are chosen/cached in multitasking)? Thank you.
0
0
228
Feb ’26
How to get full raw data of barcode using AVFoundation framework
I am creating a barcode reader using the AVfoundation framework for iOS and IPadOS. The read result goes into payloadstringvalue, but I want to check the control characters contained in the symbol, so I am using the raw data of the description, which is a property of NSObjectProtocol inherited by VNBarcodeObservation. However, I noticed that if the length set in the raw data exceeds 26, some of the raw data in the description is omitted. So my question is, is it possible to set it so that all the raw data in the description is written out without omitting any raw data? If so, could you please tell me how to set this up? Also, if you know of any other way to extract the raw barcode data, I would appreciate it if you could let me know. Thank you.
1
0
670
Jul ’25
Apple iPad Air device failing to enroll through ABM with "failed to retrieve configuration" error
Apple iPad Air device failing to enroll through ABM with "failed to retrieve configuration" error. This error occurs while reaching Apple ABM for fetching MDM server enrollment details. When we checked console logs when enrolling the device we found following error: ​default 13:54:07.229022+1000 teslad Error: Error Domain=MCCloudConfigurationErrorDomain Code=34004 "The cloud configuration server is unavailable or busy." UserInfo={NSLocalizedDescription=The cloud configuration server is unavailable or busy., CloudConfigurationErrorType=CloudConfigurationFatalError} default 13:54:07.229120+1000 Setup Service completed default 13:54:07.230096+1000 Setup Could not retrieve cloud configuration. Error: <Error domain: MCCloudConfigErrorDomain, code 33001>\ Feedback raised along with screenshot and console logs as well : FB17785513. Please analyse this issue and reply back to us.
1
0
583
Jun ’25
Feature Request: Dual Apple Pencil Pro Use or Charging Dock Support
Hi everyone 👋 I’ve been using the Apple Pencil Pro with my iPad Pro M4 and absolutely love it — the squeeze gesture, rotation, and haptics are amazing for creative work. But I’ve run into a little roadblock… Right now, only one Pencil Pro can be paired at a time. So while one is charging, you can’t use another as a backup without unpairing and re-pairing, which interrupts the workflow. I’d really love to see one of two things: The ability to use one Pencil while another charges or An official external charger (or support for third-party ones) Personally, I’d happily buy both a second Pencil and a charger if this became possible. I’ve even chatted with other creatives who feel the same — it would make a huge difference for long projects or working on the go. Just wanted to share this idea and see if anyone else here would like this too. Thanks for reading!
1
0
456
Jul ’25
Navbar buttons disappear in NavigationSplitView's sidebar when changing apps
We recently migrated our app to use NavigationSplitView on iPad with a sidebar and detail setup, and we got reports that the navigation buttons on the sidebar disappear when returning to our app after using a different app. I reproduced the issue from a new empty project with the following code (issue tested on iOS 17.4 and iOS 18.3, was not able to reproduce on iOS 16.4): import SwiftUI @main struct TestApp: App { var body: some Scene { WindowGroup { NavigationSplitView { Text("sidebar") .toolbar { ToolbarItem(placement: .topBarLeading) { Button(action: {}) { Image(systemName: "square.and.arrow.down") } } ToolbarItem(placement: .topBarTrailing) { Button(action: {}) { Image(systemName: "square.and.arrow.up") } } } } detail: { Text("detail") .toolbar { ToolbarItem(placement: .topBarLeading) { Button(action: {}) { Image(systemName: "eraser") } } ToolbarItem(placement: .topBarTrailing) { Button(action: {}) { Image(systemName: "pencil") } } } } } } } Please check the following GIF for the simple steps, notice how the navbar buttons in the detail view do not disappear: Here's the console output, it shows that the constraints break internally:
Replies
0
Boosts
0
Views
130
Activity
Apr ’25
Unable to Install Provisioning profile
Hi, I'm unable to install provisioning profile on my iPad and I know the xcode component iOS/iPadOs version and iPadOS version should be same or below the latest compared to xcode components. Now the issue is xcode component version is iOS 18.4 (22E235) SDK + iOS 18.4 (22E238) Simulator (Installed) and iPadOS version is iOS 18.4.1(22E252) could this be cause of issue ? If yes then when will apple release components for 18.4.1? Because iOS 18.4.1 release at least 3-4 weeks before this post.
Replies
0
Boosts
0
Views
115
Activity
May ’25
Question regarding ethernet over USB-C
Hello, I have a question regarding the ethernet-over-USB-C stack within iOS/iPadOS. It seems that when manually assigning an IP on this interface within iOS, the IP is stored. Therefore, when disconnecting (the USB-C cable) and reconnecting to another device for a subsequent ethernet connection, the iOS device will always default to the previously assigned IP address (obviously, this isn't the case if the other end is a DHCP server). So, within the iPhone's Ethernet-over-USB-C driver, I was curious if iOS just keeps the assignment based on the MAC of the local USB-C interface, or is stored information tied to some other identifier? Is there a way to override this behavior? Thank you
Replies
0
Boosts
0
Views
79
Activity
Jun ’25
How to hide moreNavigationController in SwiftUI?
I have more than five tabs in a TabView, and on some screens, I'm seeing a navigation bar with the title "More". I understand that this is the default behavior of TabView when there are more than five tabs—iOS automatically creates a "More" screen. I've set navigationBarHidden = true throughout my app, but the navigation bar still appears on some screens within the "More" section. Is there another way to hide the moreNavigationController or completely remove the navigation bar from the "More" screen?
Replies
0
Boosts
0
Views
148
Activity
Jul ’25
iPadOS 26 TabBar text color can't be changed
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.inlineLayoutAppearance = inlineAppearance tabAppearance.stackedLayoutAppearance = stackedAppearance UITabBar.appearance().standardAppearance = tabAppearance UITabBar.appearance().scrollEdgeAppearance = tabAppearance
Replies
0
Boosts
5
Views
486
Activity
Jul ’25
4 or 5 Finger Gestures on iPadOS 26
I disable 4 or 5 Finger Gestures on Settings.app > Multi-tasking and Gestures. But in the third-party apps, 4-5 finger touches are sometimes immediately cancelled. Especially, 4-5 finger swipe gesture. I filed this issue to FB19226717. I develop Piano instrument app. 4 or 5 finger touches are required for that kind of apps. Please fix this, Apple.
Replies
0
Boosts
0
Views
162
Activity
Jul ’25
Corrupt IOS Beta 4 and iPad
Hi, Have done the update for IOS Beta 4 and after it was done the screen just had the background and no icons. Couldn't get to any of the icons. Tried to do a restore on the iPad from my Mac and it started the restore but then got the message that it errored out and gave me this: Need help trying to get this fixed. Also tried a computer that wasn't in the beta and got the same error message. Tried to turn it off and then see if it would go back to the error before and it just stays in recovery mode. Please help. Thank you.
Replies
0
Boosts
0
Views
153
Activity
Jul ’25
Problem with testing on iPad
Hello. I was working on a Unity game for iPhone, but Apple said that it is impossible to prohibit downloading to iPad. They tested it on iPad Air 5, and for some reason the game did not work correctly - nothing happened when launched, although everything was fine in the simulator and in the real iPhone. Please tell me what to do?
Replies
0
Boosts
1
Views
97
Activity
Aug ’25
Extending the display on my iPad 11th gen (2025) on iPadOS 26 beta 3
Hi! I am very new to the apple ecosystem. I saw a lot of comments online about how Stage Manager enabled iPads have access to extending the screen to an external display, and that was what hyped me about this beta. Unfortunately, while i do have Stage Manager now, the display is still unwilling to be extended. Is that a feature that’s planned to be included in the OS? Or am i just out of luck? The ipad is one of the most capable devices i have so i was kind of hoping it would get the feature. It has an A11 chip.
Replies
0
Boosts
0
Views
144
Activity
Aug ’25
IOS cursor control
My app controls the cursor movement in a text view on iPhone and iPads. On screen touch, the IOS cursor position is out of sync with the app cursor position. Is there a way to find out, on screen touch, where the ios cursor positition is and update the app cursor to the ios cursor position? When they are out of sync, the user has to move the cursor to the startIndex and navigate from there. Frustating! I have looked at many programming books, forums, and internet search with nothing to no avail. Any help will be greatly appreciated. The app names are SummaGramPhonex and SummaGramIPAD11 and SummaGramIPAD13. Thanks. Charlie 3Sep25
Replies
0
Boosts
0
Views
220
Activity
Sep ’25
iPadOS 26 Floating Keyboard jumping up and down
Using the floating keyboard extensively. Often It starts to jump up and down. I have to pinch out to see the large version and pinch in again to restore the floating version. Sometimes just touching a key sets it off. Sometimes returning to a window from which the keyboard is displayed starts the issue. This was never a problem in ipad os 18.
Replies
0
Boosts
0
Views
503
Activity
Sep ’25
TestFlight app crashes since iOS 26 released
App builds fine locally on iPad. Once released to TestFlight, the app crashes on startup. Can't even release previous builds to TestFlight that worked fine before iOS 26. Using .net Maui 8.0.413 and Xcode 16.4. IpadOS 18.6 Crash log: Incident Identifier: 2183463F-CAFD-4E0C-95FB-8E56876118E9 Distributor ID: com.apple.TestFlight Hardware Model: iPad15,7 Process: VS_NASCO_Auscultation [3576] Path: /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation Identifier: com.NASCO.Auscultation Version: 2.8.04 (20) AppStoreTools: 17A323 AppVariant: 1:iPad15,7:18 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.NASCO.Auscultation [2590] Date/Time: 2025-09-22 14:31:29.9710 -0500 Launch Time: 2025-09-22 14:31:27.7714 -0500 OS Version: iPhone OS 18.6 (22G86) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: VS_NASCO_Auscultation [3576] Triggered by Thread: 0 Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001df60f1dc __pthread_kill + 8 1 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 3 VS_NASCO_Auscultation 0x0000000105157294 0x102e5c000 + 36680340 4 VS_NASCO_Auscultation 0x00000001050cb930 mono_runtime_setup_stat_profiler + 0 (mini-posix.c:690) 5 libsystem_platform.dylib 0x0000000218b40a68 _sigtramp + 56 (sigtramp.c:116) 6 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 7 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 8 VS_NASCO_Auscultation 0x0000000104f91170 mono_log_write_os_log + 408 (mono-log-darwin.c:0) 9 VS_NASCO_Auscultation 0x0000000104f8644c monoeg_g_logv + 172 (goutput.c:173) 10 VS_NASCO_Auscultation 0x0000000104f86594 monoeg_g_log + 28 (goutput.c:184) 11 VS_NASCO_Auscultation 0x00000001050a5f84 load_aot_module + 3172 (aot-runtime.c:2365) 12 VS_NASCO_Auscultation 0x0000000104fe4f48 mono_assembly_request_load_from + 1104 (assembly.c:2020) 13 VS_NASCO_Auscultation 0x0000000104fe4a68 mono_assembly_request_open + 472 (assembly.c:1625) 14 VS_NASCO_Auscultation 0x0000000104fe5cec mono_assembly_open + 80 (assembly.c:1828) 15 VS_NASCO_Auscultation 0x0000000104e1a0ac xamarin_assembly_preload_hook + 884 (monotouch-main.m:157) 16 VS_NASCO_Auscultation 0x0000000104fe6800 invoke_assembly_preload_hook + 64 (assembly.c:1283) 17 VS_NASCO_Auscultation 0x0000000104fe41e4 mono_assembly_request_byname + 1060 (assembly.c:2786) 18 VS_NASCO_Auscultation 0x00000001050af2e0 load_image + 280 (aot-runtime.c:325) 19 VS_NASCO_Auscultation 0x00000001050a5f1c load_aot_module + 3068 (aot-runtime.c:2358) 20 VS_NASCO_Auscultation 0x00000001050aa71c mono_aot_get_method + 292 (aot-runtime.c:4920) 21 VS_NASCO_Auscultation 0x000000010509e924 mono_jit_compile_method_with_opt + 472 (mini-runtime.c:2759) 22 VS_NASCO_Auscultation 0x000000010509cd10 mono_jit_runtime_invoke + 572 (mini-runtime.c:3525) 23 VS_NASCO_Auscultation 0x0000000105044b74 mono_runtime_invoke_checked + 148 (object.c:2792) 24 VS_NASCO_Auscultation 0x0000000105001720 create_exception_two_strings + 592 (exception.c:177) 25 VS_NASCO_Auscultation 0x00000001050014a4 mono_exception_from_name_two_strings_checked + 148 (exception.c:236) 26 VS_NASCO_Auscultation 0x0000000104fe0ab0 mono_runtime_init_checked + 708 (appdomain.c:288) 27 VS_NASCO_Auscultation 0x000000010509c64c mini_init + 6648 (mini-runtime.c:4889) 28 VS_NASCO_Auscultation 0x00000001050a3ad8 mono_jit_init_version + 20 (driver.c:2823) 29 VS_NASCO_Auscultation 0x0000000104e157ac xamarin_bridge_initialize + 216 (monovm-bridge.m:88) 30 VS_NASCO_Auscultation 0x0000000104e1a968 xamarin_main + 1784 (monotouch-main.m:438) 31 VS_NASCO_Auscultation 0x00000001051033ec main + 72 (main.arm64.mm:236) 32 dyld 0x00000001b58e5f08 start + 6040 (dyldMain.cpp:1450) Thread 1: 0 libsystem_pthread.dylib 0x0000000218be9aa4 start_wqthread + 0 Thread 2: 0 libsystem_kernel.dylib 0x00000001df60a438 __psynch_cvwait + 8 1 libsystem_pthread.dylib 0x0000000218beae50 _pthread_cond_wait + 984 (pthread_cond.c:862) 2 VS_NASCO_Auscultation 0x0000000104fdde4c thread_func + 412 (sgen-thread-pool.c:195) 3 libsystem_pthread.dylib 0x0000000218bec344 _pthread_start + 136 (pthread.c:931) 4 libsystem_pthread.dylib 0x0000000218be9ab8 thread_start + 8 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0xffffffff9838bfdf x5: 0x0000000000000018 x6: 0x000000016cfa0730 x7: 0x000000016cf9fe20 x8: 0x9b8f66cd52cb42ec x9: 0x9b8f66ccab4b5cec x10: 0x00000000000003ff x11: 0x000000016cf9fe98 x12: 0x0000000000000000 x13: 0x00000001031e01a0 x14: 0x00000001a960913c x15: 0x00000001a960be20 x16: 0x0000000000000148 x17: 0x00000001f9801e00 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f9801ee0 x22: 0x0000000000000010 x23: 0x000000000000000b x24: 0x0000000000002788 x25: 0x0000000105687624 x26: 0x000000010553ea10 x27: 0x000000010a6a0880 x28: 0x00000000000003c8 fp: 0x000000016cfa0740 lr: 0x0000000218bf0c60 sp: 0x000000016cfa0720 pc: 0x00000001df60f1dc cpsr: 0x40001000 esr: 0x56000080 Address size fault Binary Images: 0x102e5c000 - 0x10535bfff VS_NASCO_Auscultation arm64 <9b9a7de8b40b303bbc3d1a11686bb1dc> /var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation 0x109498000 - 0x1099fbfff libSkiaSharp arm64 /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/Frameworks/libSkiaSharp.framework/libSkiaSharp 0x196e23000 - 0x196ea26c3 libsystem_c.dylib arm64e <335cd87d234b3fc182db943350d31a88> /usr/lib/system/libsystem_c.dylib 0x1b58a7000 - 0x1b594187b dyld arm64e /usr/lib/dyld 0x1df604000 - 0x1df63debf libsystem_kernel.dylib arm64e /usr/lib/system/libsystem_kernel.dylib 0x218b3e000 - 0x218b458cf libsystem_platform.dylib arm64e /usr/lib/system/libsystem_platform.dylib 0x218be9000 - 0x218bf53f3 libsystem_pthread.dylib arm64e <1ee1922008593cbcbdebdf37ca2e8e4f> /usr/lib/system/libsystem_pthread.dylib EOF
Replies
0
Boosts
0
Views
293
Activity
Sep ’25
PaperKit: Correct approach for multi-page or infinite-canvas documents?
I’m trying to figure out how to extend PaperKit beyond a single fixed-size canvas. From what I understand, calling PaperMarkup(bounds:) creates one finite drawing region, and so far I have not figured out a reliable way to create multi-page or infinite canvases. Are any of these correct? Creating multiple PaperMarkup instances, each managed by its own PaperMarkupViewController, and arranging them in a ScrollView or similar paged container to represent multiple pages? Overlaying multiple PaperMarkup instances on top of PDFKit pages for paged annotation workflows? Or possibly another approach that works better with PaperKit’s design? I mean it has to be possible, right? Apple's native Preview app almost certainly uses it, and there are so many other notes apps that get this behavior working correctly, even if it requires using a legacy thing other than PaperKit. Curious if others have been able to find the right pattern for going beyond a single canvas.
Replies
0
Boosts
0
Views
144
Activity
Nov ’25
Should TabView with .page style support keyboard left/right navigation automatically?
I’m trying to understand the expected behavior of TabView when using .tabViewStyle(.page) on iPadOS with a hardware keyboard. When I place a TabView in page mode, swipe gestures correctly move between pages. However, left and right arrow keys do nothing by default, even when the view is made focusable. This feels a bit surprising, since paging with arrow keys seems like a natural keyboard interaction when a keyboard is attached. Right now, to get arrow-key navigation working, I have to manually: Make the view focusable Listen for arrow key presses Update the selection state manually This works, but it feels a little tedious for something that seems like it could be built-in. import SwiftUI struct PageTabsExample: View { @State private var selection = 0 private let pageCount = 3 var body: some View { TabView(selection: $selection) { Color.red.tag(0) Color.blue.tag(1) Color.green.tag(2) } .tabViewStyle(.page) .indexViewStyle(.page) .focusable(true) .onKeyPress(.leftArrow) { guard selection > 0 else { return .ignored } selection -= 1 return .handled } .onKeyPress(.rightArrow) { guard selection < pageCount - 1 else { return .ignored } selection += 1 return .handled } } } My questions: Is this lack of default keyboard paging for page-style TabView intentional on iPadOS with a hardware keyboard? Is there a built-in way to enable arrow-key navigation for page-style TabView, or is manual handling the expected approach? Does my approach above look like the “SwiftUI-correct” way to do this, or is there a better pattern for integrating keyboard navigation with paging? For this kind of behavior, is it generally recommended to use .onKeyPress like I’m doing here, or would .keyboardShortcut be more appropriate (for example, wiring arrow keys to actions instead)? Any guidance or clarification would be greatly appreciated. I just want to make sure I’m not missing a simpler or more idiomatic solution. Thanks!
Replies
0
Boosts
0
Views
196
Activity
Dec ’25
App Launchscreen Size NOT Correct on iPadOS 26
Hello, We’re seeing an iPad-specific Launch Screen issue related to multitasking window sizes. Environment Device: iPad (iPadOS 26) Device orientation: Landscape App is launched in a small window where the app window is portrait-shaped (width < height) Issue When the iPad is in landscape but the app is launched as a portrait-shaped small window, the LaunchScreen.storyboard appears to be rendered/layouted as landscape, not matching the actual window geometry. As a result, the Launch Screen content is clipped / partially missing (we see blank/empty area at the bottom during launch). After the app finishes launching, our first view controller uses the correct window size and the UI looks fine — the problem is mainly during the Launch Screen phase. What we checked LaunchScreen.storyboard uses Auto Layout and is expected to adapt to screen/window size. This only reproduces when the device orientation and the app window aspect ratio don’t match (landscape device + portrait-shaped app window, or vice versa). When device orientation and window shape are aligned, the Launch Screen displays correctly. Question Is it expected that iPadOS renders LaunchScreen.storyboard based on the interface orientation / size class rather than the actual window bounds in multitasking scenarios? If not expected, what is the recommended way to ensure the Launch Screen matches the app’s actual window size/aspect ratio at launch (without using code, since Launch Screen is static)? Are there any additional diagnostics or recommended steps to help us investigate and confirm the root cause (e.g., specific logs, APIs/values to capture at launch such as UIWindowScene bounds, interfaceOrientation, size classes, or any guidance on how Launch Screen snapshots are chosen/cached in multitasking)? Thank you.
Replies
0
Boosts
0
Views
228
Activity
Feb ’26
How to get full raw data of barcode using AVFoundation framework
I am creating a barcode reader using the AVfoundation framework for iOS and IPadOS. The read result goes into payloadstringvalue, but I want to check the control characters contained in the symbol, so I am using the raw data of the description, which is a property of NSObjectProtocol inherited by VNBarcodeObservation. However, I noticed that if the length set in the raw data exceeds 26, some of the raw data in the description is omitted. So my question is, is it possible to set it so that all the raw data in the description is written out without omitting any raw data? If so, could you please tell me how to set this up? Also, if you know of any other way to extract the raw barcode data, I would appreciate it if you could let me know. Thank you.
Replies
1
Boosts
0
Views
670
Activity
Jul ’25
Epub issues on Books app with new iPadOS17
Anyone else having issues with books since the update - where all epubs have been wiped or it is disclosed that it not a format applicable to Apple Books?
Replies
1
Boosts
0
Views
79
Activity
May ’25
How can i create a WIFI Hotspot in iphone
I am creating an application that needs to connect to an Iot device, so i want to make a wifi hotspot with a custom SSID and password and WPA3. Could you please provide an example code in Objective-C to get started?
Replies
1
Boosts
0
Views
182
Activity
May ’25
Apple iPad Air device failing to enroll through ABM with "failed to retrieve configuration" error
Apple iPad Air device failing to enroll through ABM with "failed to retrieve configuration" error. This error occurs while reaching Apple ABM for fetching MDM server enrollment details. When we checked console logs when enrolling the device we found following error: ​default 13:54:07.229022+1000 teslad Error: Error Domain=MCCloudConfigurationErrorDomain Code=34004 "The cloud configuration server is unavailable or busy." UserInfo={NSLocalizedDescription=The cloud configuration server is unavailable or busy., CloudConfigurationErrorType=CloudConfigurationFatalError} default 13:54:07.229120+1000 Setup Service completed default 13:54:07.230096+1000 Setup Could not retrieve cloud configuration. Error: <Error domain: MCCloudConfigErrorDomain, code 33001>\ Feedback raised along with screenshot and console logs as well : FB17785513. Please analyse this issue and reply back to us.
Replies
1
Boosts
0
Views
583
Activity
Jun ’25
Feature Request: Dual Apple Pencil Pro Use or Charging Dock Support
Hi everyone 👋 I’ve been using the Apple Pencil Pro with my iPad Pro M4 and absolutely love it — the squeeze gesture, rotation, and haptics are amazing for creative work. But I’ve run into a little roadblock… Right now, only one Pencil Pro can be paired at a time. So while one is charging, you can’t use another as a backup without unpairing and re-pairing, which interrupts the workflow. I’d really love to see one of two things: The ability to use one Pencil while another charges or An official external charger (or support for third-party ones) Personally, I’d happily buy both a second Pencil and a charger if this became possible. I’ve even chatted with other creatives who feel the same — it would make a huge difference for long projects or working on the go. Just wanted to share this idea and see if anyone else here would like this too. Thanks for reading!
Replies
1
Boosts
0
Views
456
Activity
Jul ’25