Explore the various UI frameworks available for building app interfaces. Discuss the use cases for different frameworks, share best practices, and get help with specific framework-related questions.

Posts under General subtopic

Post

Replies

Boosts

Views

Activity

Can a CGVirtualDisplay-based display receive direct touch in macOS 27 (Touch on Mac)?
We ship a macOS app that creates a virtual display with CGVirtualDisplay and streams it to a tablet, which acts as a second screen. Today we deliver the tablet's touches as mouse events (CGEvent), so the system sees a pointer, not touch. With Touch on Mac in macOS 27, we would like the system to treat that display as touch-capable, the way it does for an iPad connected with Sidecar: Can a display created with CGVirtualDisplay report touch capability (NSScreen.touchCapabilities including .multiTouch) and receive direct touches? If not directly, is a virtual HID digitizer (DriverKit or CoreHID) associated with the display's UUID the supported path? Is the com.apple.developer.hid.virtual.device entitlement available for this use? If neither is supported today, what is the recommended way to deliver touch input to a virtual display without mouse emulation? We asked this in the Touch on Mac Group Lab on 20 November and were directed here. Thank you.
0
0
149
14h
UIDesignRequiresCompatibility = YES causes a crash on iOS 26 when built with Xcode 27. The key seems to follow the runtime OS, not the build SDK
Hi, I ran into a behavior of UIDesignRequiresCompatibility that doesn't match how I (and probably others) read the documentation. Environment Xcode: 27.2 Base SDK: iOS 27.2 Deployment target: iOS 18 Run destination: iOS 26.6 (physical device) Documentation The documentation states: "The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later." I read "build for iOS 27" as a build-time condition: once the app is built with the iOS 27 SDK, the key no longer has any effect, whatever OS the app runs on. What I observed With UIDesignRequiresCompatibility = YES in Info.plist, I built the app against the iOS 27 SDK and ran it on iOS 26.6. The app crashes at launch. I removed only that key, did a clean build with the same configuration, and ran on the same iOS 26.6 device. The app runs normally. So in practice the key is not ignored for an app built for iOS 27. It looks like the decision is made by the OS the app runs on: iOS 27+ ignores the key, but iOS 26 still reads and applies it to a binary linked against the iOS 27 SDK, and that combination crashes. Questions What does "build for iOS 27 or later" refer to: the SDK the app is built with, the deployment target, or the OS the app runs on? My deployment target is iOS 18, so the app still runs on iOS 26. If the key is still honored there even when the app is built with the iOS 27 SDK, could the documentation say so explicitly? Is compatibility mode on iOS 26 for an app linked against the iOS 27 SDK an unsupported combination, and is the crash expected? Should developers simply remove the key when they adopt the iOS 27 SDK and still support iOS 26? Thanks!
Topic: UI Frameworks SubTopic: General Tags:
0
0
98
2d
Keeping the display awake during hands-free auto-scroll in a watchOS reading app
I develop Folito, a free watchOS app for reading EPUB books on Apple Watch. We added an auto-scroll mode: the text scrolls continuously at a speed the user sets with the Digital Crown, so they can read hands-free with their wrist raised. The display dims after the wake timeout because auto-scroll isn't user interaction, so the text becomes hard to read after 15–70 seconds while the user is still reading. What we've considered Pausing on isLuminanceReduced and resuming on tap. This works, but it needs a touch every minute. Continuing in Always On (luminance reduced) with ~1 Hz line-by-line updates. This is our current plan, but the text is dimmed and SE models have no Always On. WKExtendedRuntimeSession. None of the session types (self care, mindfulness, physical therapy, smart alarm, workout) describes reading, and we don't want to misuse one. HKWorkoutSession. Not appropriate, because it would record fake workouts. Questions Is there a supported way for a frontmost app to keep the display at normal brightness while showing continuously changing content the user is reading, without touch input? Would a WKExtendedRuntimeSession started only while auto-scroll runs (and ended as soon as it pauses or stops) be acceptable for this, and if so, which type? In Always On, what's the recommended way to keep text content advancing (for example, updating a ScrollView position via ScrollViewReader about once per second)? I found thread 720495 (iOS, isIdleTimerDisabled) and thread 122753 (Always On, 2019), but neither covers a watchOS app that needs the display awake while content advances on its own. Deployment target: watchOS 10, SwiftUI. Thanks!
1
0
263
3d
macOS 27 has a bit laggier menus than recent macOS versions. Can that be improved?
While not always too obvious there is sometimes delay or ”hiccup” when moving the arrow pointer horizontally among the menus for an app in top left of the menu bar. This feels like a regression from previous macOS versions. I hope this will improve in fuiture macOS 27 updates as it adds a bit of friction in the user interface experience. Wanted to add a video, but since only images seem supported to upload I might link to it later.
Topic: UI Frameworks SubTopic: General
1
0
101
6d
macOS 27.2: external monitor on a USB-C to HDMI adapter flickers, shows as "12 inch Display" at 1280x720, all resolutions refused (empty EDID)
Since I updated from macOS 27.0.1 to 27.2 (26B123), my second monitor stopped working on a Mac mini M4 Pro. It is a Dell SE2726HG on a USB-C to HDMI adapter. My LG on the built-in HDMI port still works. Symptoms: The Dell flickers. It disconnects and reconnects about once per second. System Settings shows it as "Display", 12 inch, 1280x720 at 50 Hz. Every resolution change is refused, also for the other monitor. A restart, a replug, or a lower refresh rate on the other monitor does not help. What the logs show: macOS cannot read the monitor's EDID through the adapter. IOAVServiceCopyEDID returns 0xe00002c9 (internal error), and the framebuffer has an all-zero EDID. Without an EDID, the kernel gives the display no display pipe: "AED: validate_or_set_ex: fb 2 rejecting request, exceeds full dual-pipe allocation (w 1280 vs 0 ...)" and "skipping display with null info". In 47 minutes, the log had 379 hotplug "out" events. Workaround (no extra hardware, no paid app): I injected a normal 1920x1080 EDID at runtime with the private IOKit call IOAVServiceSetVirtualEDIDMode(service, 1, edid), then IODPDeviceSetUpdated(device, 1). The monitor then comes up with its correct name at 1920x1080, with zero disconnects. The override is lost on reboot, sleep, or replug, so a LaunchAgent re-applies it every 5 seconds when the EDID read fails. This is the same approach as these projects: https://gist.github.com/danii1/99fa5f849a4d42807418259abfbf03d5 https://github.com/owomocha/macos-360hz-unlock BetterDisplay Pro can also apply a custom EDID.
Topic: UI Frameworks SubTopic: General
3
2
438
1w
Age Range Functionality in MacOS 27.2 no handle?
I have a running implementation for an iOS Application which is using AgeRange. It was running very well on Mac OS below 27 and was getting the results. It is still working on iOS 27.2 but now in MacOS 27.2 with the same code base I'm getting an } catch AgeRangeService.Error.notAvailable { NSLog("[AgeRangeDeclaration] Handle not available error")Is there a change for MacOS 27 which has to be implemented or do I have to configure something else?
Topic: UI Frameworks SubTopic: General
1
0
125
1w
On iPhone Duo in landscape, the tab bar isn't visible.
Hi, I have an app with a specific view hierarchy, and when I tested it on an iPhone Duo in landscape, I noticed an issue with how the tab bar is displayed or, rather, how it isn’t displayed. On iPhone Duo in landscape and on the main screen, the tab bar for a `UITabBarController` pushed onto a `UINavigationController` (itself inside another `UITabBarController`) isn’t visible. I've tested it in both UIKit and SwiftUI, and the issue is present in both. I could only get the tab bar to appear by presenting the view modally instead of pushing it, but that isn’t a viable solution for my app. For example: ``` UIWindow └─ RootTabBarController (UITabBarController) └─ UINavigationController (tab 2) ├─ FirstTabViewController (root) └─ push └─ NestedTabBarController (UITabBarController) ├─ ItemListViewController (UITableView) ├─ ItemListViewController (UITableView) └─ ItemListViewController (UITableView) ``` I've put together a simplified [demo repo](https://github.com/janossuta/iphone-duo-issue-demo/tree/main) that shows the problem. I've attached two images showing that the tabs disappear in landscape mode and are visible in portrait mode. Can we preserve the original functionality?
Topic: UI Frameworks SubTopic: General
0
0
45
1w
Cannot move window by its background (macOS 27)
Hi, My app (SmashTunes) can display a floating window with artwork of a music track that is displaying. It does for over a decade in multiple versions of macOS. I do this by calling window?.isMovableByWindowBackground = true. This stopped working under macOS 27. I've read some reports of others not being able to move windows. It should supposedly have been fixed in macOS 27.2, but it is not. Has anyone on this forum run into the same problem, or know of a different way to move windows around on the screen? When I add add a titlebar, I can drag it by the titlebar, but that is not really an option for my use case.
Topic: UI Frameworks SubTopic: General
1
0
177
1w
PDFView context menu: "Actual Size"
In a PDFView, the OS provides a context menu which contains (among other things) "Actual Size" zoom. This command wrongly displays the page at 1 point = 1 pixel. Traditionally on MacOS, "Actual Size" displays the page at 1 inch on page = 1 inch on screen, e.g. for a Letter page, 8.5 x 11 inches on the screen. (So the API needs to determine the display's pixel density to calculate the zoom size.) In Preview 11.0 on Os 27.2, "Actual Size" in the PDFView context menu and in the View menu both zoom to 1 point = 1 pixel. In Preview on Sequoia, Actual Size in the View menu displays at 1 inch = 1 inch, but the context menu gives 1 pt = 1px. (The latter presumably relying on the built-in context menu from PDFView.) Note that in Pages.app, Actual View gives the expected 1 inch = 1 inch on screen.
1
0
110
2w
iPadOS 26.0 RC–27.2: Four/Five-finger swipe still triggers system gesture and swallows touches even with all Multitasking Gestures disabled (FB24795986)
Summary: With all Multitasking Gestures disabled and Full Screen Apps enabled, four/five-finger pinch or swipe gestures are still intercepted by the system and swallow all touch points, so the foreground app stops receiving touch input. This is most noticeable in games that rely on multi-finger controls. The issue has persisted from iPadOS 26.0 RC through 27.2 — over a year — and remains unfixed(open). Multiple Feedback reports have been marked Open without a fix. one related report was marked “Potential Fix Identified – For a Future OS Update” and later reverted. Environment: iPad running any iPadOS version from 26.0 RC through 27.2 Settings > Multitasking & Gestures > all gestures disabled Full Screen Apps enabled (not Stage Manager or windowed apps) Steps to Reproduce: On the above configuration, open any app (most noticeable in games). Perform a four-finger pinch, or a four/five-finger left/right swipe. Observe that all touch points are immediately swallowed by the system, and the foreground app stops receiving touch input. Expected Result: Since all multitasking gestures are disabled in Settings, four/five-finger gestures should not respond at all, and the app should continue receiving touch input normally. Actual Result: The system still intercepts touches in the gesture area, causing the app to lose touch input temporarily or persistently. In games that rely on multi-finger input, this effectively breaks controls. FB Number: FB24795986
0
0
162
3w
macOS widget stays on the grey placeholder after a Developer ID app is replaced by a Mac App Store build of the same app
I have a macOS app with a WidgetKit widget extension, distributed two ways: a notarised Developer ID download, and a Mac App Store build (same bundle identifiers, same team, different signature). When a user replaces the Developer ID copy in /Applications with the store-signed copy, the desktop widget draws only the grey placeholder and never recovers. The app itself runs normally. What I saw (8 October 2026, macOS 27): An iMac had the Developer ID build 47 (version 1.6.3) in /Applications with the widget on the desktop. I installed build 48 (version 1.6.4), signed for the store, from TestFlight. It replaced the Developer ID copy in /Applications. The app worked. The large widget showed grey placeholder bars and no data, for at least five minutes. killall chronod in Terminal brought the widget back straight away. On a MacBook, updating from one TestFlight build to the next (builds 46, 47, 48) redrew the widget each time. So it is the change from a Developer ID signature to a store signature, not an ordinary update. What I think is happening, and would like confirmed or corrected: the widget process that was started from the Developer ID copy keeps running after the app is replaced, and the system refuses what it draws (or never asks it for a new timeline), while the widget gallery and desktop keep showing that process's placeholder. What I already do: The Developer ID build ships a small helper outside the sandbox that ends the old widget process after an update. The Mac App Store build cannot carry that helper. The widget extension compares the build number in its bundle's Info.plist on disk with the one it started with, and exits if they differ. This ran in the case above (the build numbers were 47 and 48) and did not clear the placeholder. I suspect the check only runs when the system asks the widget for a snapshot or timeline, and the system had stopped asking. I call WidgetCenter.shared.reloadAllTimelines() after the app writes new data. Questions: Is there a supported way for a sandboxed app (or its widget extension) to make the system replace or restart a widget process that belongs to an earlier, differently signed copy of the same app? Without a Terminal command, and without a helper outside the sandbox. Is it expected that chronod keeps the old extension process after the containing app is replaced by a copy with a different signing identity, and that the widget then stays on the placeholder? Is there a log subsystem or predicate that shows why the old extension process was kept, or what the system refused? Thank you.
0
1
326
3w
UIDesignRequiresCompatibility for Xcode27
Hallo everyone, We are building our app with Xcode 27 and noticed that UIDesignRequiresCompatibility still appears to be honored on iOS 26 devices. Questions: Could you confirm whether this key is still supported on iOS 26 when built with Xcode 27? If our deployment target includes iOS 26, should we keep the key for backward compatibility, or is Apple's recommendation to remove it entirely? Additionally, are there any risks associated with removing it for iOS 26 users?
1
0
594
Oct ’26
Mission Control Window Management update
Dear Apple, I am sending feedback regarding the desktop management of macOS to improve the user experience. Mission Control currently only has a “+” button to the right, meaning that all new desktops are forced to the right side of the line. Adding an identical “+” button to the left will increase ease of using the OS, as I don’t necessarily need every new desktop to be on the right side. This will increase usability and make using desktops significantly easier than manually dragging them into the needed positions every time I add a desktop. Another thing is that when I maximize apps, all desktops go to the left by one spot. There should be a setting where you can control where desktops go when maximizing screens, either you want every desktop to go to the right or the left. This makes things easier as sometimes I have my main app on the right, with all the multi-tasking on the left. If desktops move to the right instead of the left, no open apps will be interfered with. (Please put this setting in the “Desktop and Dock” section). I have been using macOS for a year now, and those details were quite clear. Please consider this as a software update for over 100 million Macbook users, increasing usability without changing the OS so much people barely know how to use it. I have been concentrating significantly on macOS lately, noticing an upgrade followed by another, and is how I noticed this. Please consider this a fresh start for my feedback. I apologize for my previous un-trained replies. I am not a trained professional, but I genuinely care about improving the user experience and wanted to share these layout ideas. I promise to keep my interactions respectful of the forum guidelines from now on. May these desktop management ideas be considered? Thanks, Alyaman
Topic: UI Frameworks SubTopic: General
2
0
453
Oct ’26
Tapping the top area of iPhone Duo does not respond in Device Hub
I’m simulating an iPhone Duo using Xcode 27.1 beta, and I’m having trouble tapping buttons placed near the top of the screen. It seems that the top ~20 pixels of the screen are not responding to taps. In my ViewController, preferredScreenEdgesDeferringSystemGestures returns .all, so system gestures should require two swipes to be triggered. However, a simple tap in this area does not seem to be recognized. This appears to happen only on iPhone Duo; taps work normally on other iPhone models. Does anyone know whether this behavior is expected to occur on the actual iPhone Duo hardware as well, or is it specific to the simulator? For reference, the buttons are positioned according to LayoutMarginsGuide with Safe Area. FB24914903 I wonder if anyone knows how to get the top margin size programmatically.
1
1
935
Oct ’26
EyeFlow: Which Apple APIs support camera-based gaze scrolling and dwell selection?
Hello Apple Developer Community, I’m Yashwanth Pentakota, the independent developer behind EyeFlow, a prototype exploring hands-free screen navigation using a standard device camera. EyeFlow focuses on gaze-based scrolling and dwell-based selection. The goal is to support people who have difficulty using a mouse or touchscreen. My current work includes improving calibration, reducing gaze jitter, and preventing unintended actions. I’m exploring bringing this interaction model to Apple platforms and would appreciate guidance on one architectural question: For gaze-controlled scrolling and selection within my own app, which supported Apple frameworks or APIs should I evaluate first, and what platform limitations should I account for? My current pipeline is: Camera capture → face/eye detection → gaze estimation → calibration and smoothing → scrolling or selection. This is an experimental prototype; I’m still evaluating its accuracy and usability. Prototype/source: https://github.com/Yashwanth6121/Eye-Flow-v3. Suggestions on relevant documentation or sample projects would be helpful. Thank you, Yashwanth Pentakota
0
0
254
Oct ’26
CODM stutters whenever iOS system UI appears (Notification Center, Volume HUD, etc.) on iPhone 13 - iOS 27 Public Beta
Hi everyone, I'm using an iPhone 13 running the iOS 27 Public Beta, and overall the experience has been excellent. Battery life is better than I expected, and the system feels very smooth during everyday use. However, I'm experiencing one persistent issue while playing Call of Duty: Mobile (CODM). Whenever an iOS system UI appears, the game briefly stutters or drops frames. This happens with: Pulling down the Notification Center The volume indicator (Volume HUD) Other iOS overlays or system UI animations The stutter only lasts for a moment while the UI is displayed, and gameplay immediately returns to normal if I open the full control center (swiping down). The frame drops will be also gone when I change the frame rate from MAX to Low then Low to MAX frame rate. Things I've already tried: Restarting the device -Enabling Shader Preload in CODM -Closing background apps -Testing different graphics and frame rate settings (which is a temporary solution) -Updating to the latest iOS 27 Public Beta The issue was also present on my previous iOS version, so it doesn't appear to be new to this beta. During normal gameplay, the game runs smoothly. The frame drops only occur when iOS overlays are rendered. Has anyone else experienced this on iPhone, particularly on iPhone 13 or other models? I'm also curious whether this is an iOS compositor issue, a CODM optimization issue, or simply expected behavior when system UI interrupts a game. Any feedback or suggestions would be greatly appreciated. Thank you!
Topic: UI Frameworks SubTopic: General
2
1
753
Oct ’26
Can a CGVirtualDisplay-based display receive direct touch in macOS 27 (Touch on Mac)?
We ship a macOS app that creates a virtual display with CGVirtualDisplay and streams it to a tablet, which acts as a second screen. Today we deliver the tablet's touches as mouse events (CGEvent), so the system sees a pointer, not touch. With Touch on Mac in macOS 27, we would like the system to treat that display as touch-capable, the way it does for an iPad connected with Sidecar: Can a display created with CGVirtualDisplay report touch capability (NSScreen.touchCapabilities including .multiTouch) and receive direct touches? If not directly, is a virtual HID digitizer (DriverKit or CoreHID) associated with the display's UUID the supported path? Is the com.apple.developer.hid.virtual.device entitlement available for this use? If neither is supported today, what is the recommended way to deliver touch input to a virtual display without mouse emulation? We asked this in the Touch on Mac Group Lab on 20 November and were directed here. Thank you.
Replies
0
Boosts
0
Views
149
Activity
14h
UIDesignRequiresCompatibility = YES causes a crash on iOS 26 when built with Xcode 27. The key seems to follow the runtime OS, not the build SDK
Hi, I ran into a behavior of UIDesignRequiresCompatibility that doesn't match how I (and probably others) read the documentation. Environment Xcode: 27.2 Base SDK: iOS 27.2 Deployment target: iOS 18 Run destination: iOS 26.6 (physical device) Documentation The documentation states: "The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later." I read "build for iOS 27" as a build-time condition: once the app is built with the iOS 27 SDK, the key no longer has any effect, whatever OS the app runs on. What I observed With UIDesignRequiresCompatibility = YES in Info.plist, I built the app against the iOS 27 SDK and ran it on iOS 26.6. The app crashes at launch. I removed only that key, did a clean build with the same configuration, and ran on the same iOS 26.6 device. The app runs normally. So in practice the key is not ignored for an app built for iOS 27. It looks like the decision is made by the OS the app runs on: iOS 27+ ignores the key, but iOS 26 still reads and applies it to a binary linked against the iOS 27 SDK, and that combination crashes. Questions What does "build for iOS 27 or later" refer to: the SDK the app is built with, the deployment target, or the OS the app runs on? My deployment target is iOS 18, so the app still runs on iOS 26. If the key is still honored there even when the app is built with the iOS 27 SDK, could the documentation say so explicitly? Is compatibility mode on iOS 26 for an app linked against the iOS 27 SDK an unsupported combination, and is the crash expected? Should developers simply remove the key when they adopt the iOS 27 SDK and still support iOS 26? Thanks!
Topic: UI Frameworks SubTopic: General Tags:
Replies
0
Boosts
0
Views
98
Activity
2d
Keeping the display awake during hands-free auto-scroll in a watchOS reading app
I develop Folito, a free watchOS app for reading EPUB books on Apple Watch. We added an auto-scroll mode: the text scrolls continuously at a speed the user sets with the Digital Crown, so they can read hands-free with their wrist raised. The display dims after the wake timeout because auto-scroll isn't user interaction, so the text becomes hard to read after 15–70 seconds while the user is still reading. What we've considered Pausing on isLuminanceReduced and resuming on tap. This works, but it needs a touch every minute. Continuing in Always On (luminance reduced) with ~1 Hz line-by-line updates. This is our current plan, but the text is dimmed and SE models have no Always On. WKExtendedRuntimeSession. None of the session types (self care, mindfulness, physical therapy, smart alarm, workout) describes reading, and we don't want to misuse one. HKWorkoutSession. Not appropriate, because it would record fake workouts. Questions Is there a supported way for a frontmost app to keep the display at normal brightness while showing continuously changing content the user is reading, without touch input? Would a WKExtendedRuntimeSession started only while auto-scroll runs (and ended as soon as it pauses or stops) be acceptable for this, and if so, which type? In Always On, what's the recommended way to keep text content advancing (for example, updating a ScrollView position via ScrollViewReader about once per second)? I found thread 720495 (iOS, isIdleTimerDisabled) and thread 122753 (Always On, 2019), but neither covers a watchOS app that needs the display awake while content advances on its own. Deployment target: watchOS 10, SwiftUI. Thanks!
Replies
1
Boosts
0
Views
263
Activity
3d
macOS 27 has a bit laggier menus than recent macOS versions. Can that be improved?
While not always too obvious there is sometimes delay or ”hiccup” when moving the arrow pointer horizontally among the menus for an app in top left of the menu bar. This feels like a regression from previous macOS versions. I hope this will improve in fuiture macOS 27 updates as it adds a bit of friction in the user interface experience. Wanted to add a video, but since only images seem supported to upload I might link to it later.
Topic: UI Frameworks SubTopic: General
Replies
1
Boosts
0
Views
101
Activity
6d
macOS 27.2: external monitor on a USB-C to HDMI adapter flickers, shows as "12 inch Display" at 1280x720, all resolutions refused (empty EDID)
Since I updated from macOS 27.0.1 to 27.2 (26B123), my second monitor stopped working on a Mac mini M4 Pro. It is a Dell SE2726HG on a USB-C to HDMI adapter. My LG on the built-in HDMI port still works. Symptoms: The Dell flickers. It disconnects and reconnects about once per second. System Settings shows it as "Display", 12 inch, 1280x720 at 50 Hz. Every resolution change is refused, also for the other monitor. A restart, a replug, or a lower refresh rate on the other monitor does not help. What the logs show: macOS cannot read the monitor's EDID through the adapter. IOAVServiceCopyEDID returns 0xe00002c9 (internal error), and the framebuffer has an all-zero EDID. Without an EDID, the kernel gives the display no display pipe: "AED: validate_or_set_ex: fb 2 rejecting request, exceeds full dual-pipe allocation (w 1280 vs 0 ...)" and "skipping display with null info". In 47 minutes, the log had 379 hotplug "out" events. Workaround (no extra hardware, no paid app): I injected a normal 1920x1080 EDID at runtime with the private IOKit call IOAVServiceSetVirtualEDIDMode(service, 1, edid), then IODPDeviceSetUpdated(device, 1). The monitor then comes up with its correct name at 1920x1080, with zero disconnects. The override is lost on reboot, sleep, or replug, so a LaunchAgent re-applies it every 5 seconds when the EDID read fails. This is the same approach as these projects: https://gist.github.com/danii1/99fa5f849a4d42807418259abfbf03d5 https://github.com/owomocha/macos-360hz-unlock BetterDisplay Pro can also apply a custom EDID.
Topic: UI Frameworks SubTopic: General
Replies
3
Boosts
2
Views
438
Activity
1w
Age Range Functionality in MacOS 27.2 no handle?
I have a running implementation for an iOS Application which is using AgeRange. It was running very well on Mac OS below 27 and was getting the results. It is still working on iOS 27.2 but now in MacOS 27.2 with the same code base I'm getting an } catch AgeRangeService.Error.notAvailable { NSLog("[AgeRangeDeclaration] Handle not available error")Is there a change for MacOS 27 which has to be implemented or do I have to configure something else?
Topic: UI Frameworks SubTopic: General
Replies
1
Boosts
0
Views
125
Activity
1w
On iPhone Duo in landscape, the tab bar isn't visible.
Hi, I have an app with a specific view hierarchy, and when I tested it on an iPhone Duo in landscape, I noticed an issue with how the tab bar is displayed or, rather, how it isn’t displayed. On iPhone Duo in landscape and on the main screen, the tab bar for a `UITabBarController` pushed onto a `UINavigationController` (itself inside another `UITabBarController`) isn’t visible. I've tested it in both UIKit and SwiftUI, and the issue is present in both. I could only get the tab bar to appear by presenting the view modally instead of pushing it, but that isn’t a viable solution for my app. For example: ``` UIWindow └─ RootTabBarController (UITabBarController) └─ UINavigationController (tab 2) ├─ FirstTabViewController (root) └─ push └─ NestedTabBarController (UITabBarController) ├─ ItemListViewController (UITableView) ├─ ItemListViewController (UITableView) └─ ItemListViewController (UITableView) ``` I've put together a simplified [demo repo](https://github.com/janossuta/iphone-duo-issue-demo/tree/main) that shows the problem. I've attached two images showing that the tabs disappear in landscape mode and are visible in portrait mode. Can we preserve the original functionality?
Topic: UI Frameworks SubTopic: General
Replies
0
Boosts
0
Views
45
Activity
1w
Cannot move window by its background (macOS 27)
Hi, My app (SmashTunes) can display a floating window with artwork of a music track that is displaying. It does for over a decade in multiple versions of macOS. I do this by calling window?.isMovableByWindowBackground = true. This stopped working under macOS 27. I've read some reports of others not being able to move windows. It should supposedly have been fixed in macOS 27.2, but it is not. Has anyone on this forum run into the same problem, or know of a different way to move windows around on the screen? When I add add a titlebar, I can drag it by the titlebar, but that is not really an option for my use case.
Topic: UI Frameworks SubTopic: General
Replies
1
Boosts
0
Views
177
Activity
1w
PDFView context menu: "Actual Size"
In a PDFView, the OS provides a context menu which contains (among other things) "Actual Size" zoom. This command wrongly displays the page at 1 point = 1 pixel. Traditionally on MacOS, "Actual Size" displays the page at 1 inch on page = 1 inch on screen, e.g. for a Letter page, 8.5 x 11 inches on the screen. (So the API needs to determine the display's pixel density to calculate the zoom size.) In Preview 11.0 on Os 27.2, "Actual Size" in the PDFView context menu and in the View menu both zoom to 1 point = 1 pixel. In Preview on Sequoia, Actual Size in the View menu displays at 1 inch = 1 inch, but the context menu gives 1 pt = 1px. (The latter presumably relying on the built-in context menu from PDFView.) Note that in Pages.app, Actual View gives the expected 1 inch = 1 inch on screen.
Replies
1
Boosts
0
Views
110
Activity
2w
iPadOS 26.0 RC–27.2: Four/Five-finger swipe still triggers system gesture and swallows touches even with all Multitasking Gestures disabled (FB24795986)
Summary: With all Multitasking Gestures disabled and Full Screen Apps enabled, four/five-finger pinch or swipe gestures are still intercepted by the system and swallow all touch points, so the foreground app stops receiving touch input. This is most noticeable in games that rely on multi-finger controls. The issue has persisted from iPadOS 26.0 RC through 27.2 — over a year — and remains unfixed(open). Multiple Feedback reports have been marked Open without a fix. one related report was marked “Potential Fix Identified – For a Future OS Update” and later reverted. Environment: iPad running any iPadOS version from 26.0 RC through 27.2 Settings > Multitasking & Gestures > all gestures disabled Full Screen Apps enabled (not Stage Manager or windowed apps) Steps to Reproduce: On the above configuration, open any app (most noticeable in games). Perform a four-finger pinch, or a four/five-finger left/right swipe. Observe that all touch points are immediately swallowed by the system, and the foreground app stops receiving touch input. Expected Result: Since all multitasking gestures are disabled in Settings, four/five-finger gestures should not respond at all, and the app should continue receiving touch input normally. Actual Result: The system still intercepts touches in the gesture area, causing the app to lose touch input temporarily or persistently. In games that rely on multi-finger input, this effectively breaks controls. FB Number: FB24795986
Replies
0
Boosts
0
Views
162
Activity
3w
macOS widget stays on the grey placeholder after a Developer ID app is replaced by a Mac App Store build of the same app
I have a macOS app with a WidgetKit widget extension, distributed two ways: a notarised Developer ID download, and a Mac App Store build (same bundle identifiers, same team, different signature). When a user replaces the Developer ID copy in /Applications with the store-signed copy, the desktop widget draws only the grey placeholder and never recovers. The app itself runs normally. What I saw (8 October 2026, macOS 27): An iMac had the Developer ID build 47 (version 1.6.3) in /Applications with the widget on the desktop. I installed build 48 (version 1.6.4), signed for the store, from TestFlight. It replaced the Developer ID copy in /Applications. The app worked. The large widget showed grey placeholder bars and no data, for at least five minutes. killall chronod in Terminal brought the widget back straight away. On a MacBook, updating from one TestFlight build to the next (builds 46, 47, 48) redrew the widget each time. So it is the change from a Developer ID signature to a store signature, not an ordinary update. What I think is happening, and would like confirmed or corrected: the widget process that was started from the Developer ID copy keeps running after the app is replaced, and the system refuses what it draws (or never asks it for a new timeline), while the widget gallery and desktop keep showing that process's placeholder. What I already do: The Developer ID build ships a small helper outside the sandbox that ends the old widget process after an update. The Mac App Store build cannot carry that helper. The widget extension compares the build number in its bundle's Info.plist on disk with the one it started with, and exits if they differ. This ran in the case above (the build numbers were 47 and 48) and did not clear the placeholder. I suspect the check only runs when the system asks the widget for a snapshot or timeline, and the system had stopped asking. I call WidgetCenter.shared.reloadAllTimelines() after the app writes new data. Questions: Is there a supported way for a sandboxed app (or its widget extension) to make the system replace or restart a widget process that belongs to an earlier, differently signed copy of the same app? Without a Terminal command, and without a helper outside the sandbox. Is it expected that chronod keeps the old extension process after the containing app is replaced by a copy with a different signing identity, and that the widget then stays on the placeholder? Is there a log subsystem or predicate that shows why the old extension process was kept, or what the system refused? Thank you.
Replies
0
Boosts
1
Views
326
Activity
3w
UIDesignRequiresCompatibility for Xcode27
Hallo everyone, We are building our app with Xcode 27 and noticed that UIDesignRequiresCompatibility still appears to be honored on iOS 26 devices. Questions: Could you confirm whether this key is still supported on iOS 26 when built with Xcode 27? If our deployment target includes iOS 26, should we keep the key for backward compatibility, or is Apple's recommendation to remove it entirely? Additionally, are there any risks associated with removing it for iOS 26 users?
Replies
1
Boosts
0
Views
594
Activity
Oct ’26
Mission Control Window Management update
Dear Apple, I am sending feedback regarding the desktop management of macOS to improve the user experience. Mission Control currently only has a “+” button to the right, meaning that all new desktops are forced to the right side of the line. Adding an identical “+” button to the left will increase ease of using the OS, as I don’t necessarily need every new desktop to be on the right side. This will increase usability and make using desktops significantly easier than manually dragging them into the needed positions every time I add a desktop. Another thing is that when I maximize apps, all desktops go to the left by one spot. There should be a setting where you can control where desktops go when maximizing screens, either you want every desktop to go to the right or the left. This makes things easier as sometimes I have my main app on the right, with all the multi-tasking on the left. If desktops move to the right instead of the left, no open apps will be interfered with. (Please put this setting in the “Desktop and Dock” section). I have been using macOS for a year now, and those details were quite clear. Please consider this as a software update for over 100 million Macbook users, increasing usability without changing the OS so much people barely know how to use it. I have been concentrating significantly on macOS lately, noticing an upgrade followed by another, and is how I noticed this. Please consider this a fresh start for my feedback. I apologize for my previous un-trained replies. I am not a trained professional, but I genuinely care about improving the user experience and wanted to share these layout ideas. I promise to keep my interactions respectful of the forum guidelines from now on. May these desktop management ideas be considered? Thanks, Alyaman
Topic: UI Frameworks SubTopic: General
Replies
2
Boosts
0
Views
453
Activity
Oct ’26
Tapping the top area of iPhone Duo does not respond in Device Hub
I’m simulating an iPhone Duo using Xcode 27.1 beta, and I’m having trouble tapping buttons placed near the top of the screen. It seems that the top ~20 pixels of the screen are not responding to taps. In my ViewController, preferredScreenEdgesDeferringSystemGestures returns .all, so system gestures should require two swipes to be triggered. However, a simple tap in this area does not seem to be recognized. This appears to happen only on iPhone Duo; taps work normally on other iPhone models. Does anyone know whether this behavior is expected to occur on the actual iPhone Duo hardware as well, or is it specific to the simulator? For reference, the buttons are positioned according to LayoutMarginsGuide with Safe Area. FB24914903 I wonder if anyone knows how to get the top margin size programmatically.
Replies
1
Boosts
1
Views
935
Activity
Oct ’26
EyeFlow: Which Apple APIs support camera-based gaze scrolling and dwell selection?
Hello Apple Developer Community, I’m Yashwanth Pentakota, the independent developer behind EyeFlow, a prototype exploring hands-free screen navigation using a standard device camera. EyeFlow focuses on gaze-based scrolling and dwell-based selection. The goal is to support people who have difficulty using a mouse or touchscreen. My current work includes improving calibration, reducing gaze jitter, and preventing unintended actions. I’m exploring bringing this interaction model to Apple platforms and would appreciate guidance on one architectural question: For gaze-controlled scrolling and selection within my own app, which supported Apple frameworks or APIs should I evaluate first, and what platform limitations should I account for? My current pipeline is: Camera capture → face/eye detection → gaze estimation → calibration and smoothing → scrolling or selection. This is an experimental prototype; I’m still evaluating its accuracy and usability. Prototype/source: https://github.com/Yashwanth6121/Eye-Flow-v3. Suggestions on relevant documentation or sample projects would be helpful. Thank you, Yashwanth Pentakota
Replies
0
Boosts
0
Views
254
Activity
Oct ’26
CODM stutters whenever iOS system UI appears (Notification Center, Volume HUD, etc.) on iPhone 13 - iOS 27 Public Beta
Hi everyone, I'm using an iPhone 13 running the iOS 27 Public Beta, and overall the experience has been excellent. Battery life is better than I expected, and the system feels very smooth during everyday use. However, I'm experiencing one persistent issue while playing Call of Duty: Mobile (CODM). Whenever an iOS system UI appears, the game briefly stutters or drops frames. This happens with: Pulling down the Notification Center The volume indicator (Volume HUD) Other iOS overlays or system UI animations The stutter only lasts for a moment while the UI is displayed, and gameplay immediately returns to normal if I open the full control center (swiping down). The frame drops will be also gone when I change the frame rate from MAX to Low then Low to MAX frame rate. Things I've already tried: Restarting the device -Enabling Shader Preload in CODM -Closing background apps -Testing different graphics and frame rate settings (which is a temporary solution) -Updating to the latest iOS 27 Public Beta The issue was also present on my previous iOS version, so it doesn't appear to be new to this beta. During normal gameplay, the game runs smoothly. The frame drops only occur when iOS overlays are rendered. Has anyone else experienced this on iPhone, particularly on iPhone 13 or other models? I'm also curious whether this is an iOS compositor issue, a CODM optimization issue, or simply expected behavior when system UI interrupts a game. Any feedback or suggestions would be greatly appreciated. Thank you!
Topic: UI Frameworks SubTopic: General
Replies
2
Boosts
1
Views
753
Activity
Oct ’26