We don't have a suitable design for our widget for WidgetRenderingMode.vibrant as used on the iPad Lock Screen. Is there a way to opt out of having our widget available there? The iOS 17 photos widget seems to behave like this. It is available for iPhone StandBy, but not for iPad Lock Screen. This is the behaviour we want to have.

Our app uses Cordova with a Cordova Local Webserver plugin. This plugin uses the url http://localhost: with a randomly chosen port. Some of the devices that our app runs on are MDM configured and have Content Filters enabled which only allows a finite list of website URLs to be accessed. This configuration has always worked in the past. Starting with the release of iPadOS 16.5, our app now hangs because the content filters are now preventing access to http://localhost. We've tried adding http://localhost, plus any derivative of that URL (i.e. http://localhost:, http://localhost:*, etc.) to the Allowed Website list, but this does not help. Wondering if anyone else has encountered this issue.

On XCode 14.3.1, downloading support files for iPadOS 17, fails with message: **Could not locate device support files You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com. [missing string: 869a8e318f07f3e2f42e11d435502286094f76de]** on XCode 15.0 beta (15A5160n), iPad does not show up. Have rebooted Mac, iPad, Settings > Clear Trusted Computers => no iPad in XCode 15 => missing support files message on XCode 14.3.1 Am stuck. How to get unstuck quickly?

When I upgraded my 2nd gen iPad Pro to iPadOS 17 beta 1, the entry method changed from the 0 large numbers that normally show for a numerical passcode to a text entry field - but the passcode worked. Now I updated to Beta 2 and it says press home to upgrade, then shows the passcode textfield, but doesn't accept my Passcode anymore. Any hints?

I am running iPadOS 17 beta2 and experiencing an issue with the integration between a third-party app and the Health app. Specifically, I have noticed that the isHealthDataAvailable() method in HealthKit is returning false. Additional Information: ・Device: iPad (6th generation) running iPadOS 17 beta2. ・Xcode: ver14.2.0 Expected Outcome: ・I expect the isHealthDataAvailable() method in HealthKit to return true. This would allow the third-party app to integrate with the Health app. Additional Details: ・The third-party app successfully integrates with the Health app on iOS 17 beta2. ・The issue occurs regardless of whether the Health app is installed or uninstalled. I would greatly appreciate any advice or solutions regarding this issue. Thank you for your assistance.

I have an accessoryCircular Lock Screen widget built for iOS 16: ZStack { AccessoryWidgetBackground() VStack { Text("MON") .font(.caption) Text("6") .font(.title) } } When run on iOS 17 it renders an error “Please adopt containerBackground API”. So I changed it to: VStack { Text("MON") .font(.caption) Text("6") .font(.title) } .containerBackground(for: .widget) { AccessoryWidgetBackground() } This causes the error to go away but the circular background is no longer visible (tested with iPadOS 17b2). What’s the right way to implement this?

After installing the latest iOS 17 v3 update on my iPhone 12 Pro, the setup assistant appeared. I chose my Wi-Fi network and then an error appears that "Verification Failed: There was a problem connecting to the server." It then just stays on that screen. I was about to DFU restore my device - as removing Find my iPhone, trying on Cellular, and restarting didn't work. But luckily, I had Siri enabled! The FIX: Use Siri (holding down the power button for 1 second) from the post-update intro screen and ask it turn on AirPlane Mode. Once Airplane Mode was on, it let me skip the connect to Wifi section and I was in - as cellular was also disabled! No DFU needed!

To bring my widgets to iPad lock screen, i need to detect my widget that has a background to display different contents, watch the wwdc 23 video it tells we can use .showsWidgetContainerBackground environment to apply that goal, but the problem is this code wouldn't compile because .showsWidgetContainerBackground only available in iOS 17 @available(iOS 14.0, *) struct MyWidgetView: View { @Environment(\.showsWidgetContainerBackground) var showsBackground var body: some View { ... } } So, my solution is use a environment wrapper, like this: @available(iOS 17.0, *) struct EnvironmentWrapper: View { @Environment(\.showsWidgetContainerBackground) var showsWidgetContainerBackground var body: some View { VStack(alignment: .leading) { Text("Wrapper Has Background: \(showsWidgetContainerBackground ? "YES" : "NO")") } } } extension View { var showsWidgetContainerBackground: Bool { if #available(iOS 17.0, *) { return EnvironmentWrapper().showsWidgetContainerBackground } else { return true } } } But it didn't work, this is the example: @available(iOS 17.0, *) struct EnvironmentWrapper: View { @Environment(\.showsWidgetContainerBackground) var showsWidgetContainerBackground var body: some View { VStack(alignment: .leading) { Text("Wrapper has background: \(showsWidgetContainerBackground ? "YES" : "NO")") } } } @available(iOS 17.0, *) struct ExampleView: View { @Environment(\.showsWidgetContainerBackground) var showsBackground var body: some View { VStack(alignment: .leading) { Text("Read from self: \(showsBackground ? "YES" : "NO")") EnvironmentWrapper() Text("Read from wrapper: \(EnvironmentWrapper().showsWidgetContainerBackground ? "YES" : "NO")") } .font(.system(size: 12, weight: .medium)) } } As you can see, if i read it directly from self, it works, but if i read from outside, it always return true i also try to load a view first in the wrapper, but it didn't work either func getShowsBackground() -> Bool { let _ = body return showsWidgetContainerBackground }

Hi, I am trying to use the AVCam sample app code (latest as of 19 Jul 2023 from here - https://developer.apple.com/documentation/avfoundation/capture_setup/avcam_building_a_camera_app) Test setup: iPad Pro 11" 4 Gen running iPadOS 17 (public beta). Xcode 15 beta 4 to use the iPad as the run destination (wireless mode). An external USB webcam is connected to the iPad during the test. This camera is working when I test using the FaceTime app. I am able to build and run the app on the iPad, however I get the following error when the external camera is selected for video capture. Capture session runtime error: related decl 'e' for AVError(_nsError: Error Domain=AVFoundationErrorDomain Code=-11819 "Cannot Complete Action" UserInfo={NSLocalizedDescription=Cannot Complete Action, NSLocalizedRecoverySuggestion=Try again later.}) Error Code = AVError(rawValue: -11819) From the code the error points to "mediaServicesWereReset" error. I am unable to figure out what is the cause of this error. Can someone help regarding this? Thanks!

This is a very annoying error which is causing a crash in my app. The error description is very vague and I'm guessing mostly related to oddities of Xcode 15 Beta. Here is the full error stack: *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _UIRecessedMaterialView because no class named _UIRecessedMaterialView was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' *** First throw call stack: ( 0 CoreFoundation 0x00007ff80048c88a __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007ff800057894 objc_exception_throw + 48 2 CoreFoundation 0x00007ff80048c768 -[NSException initWithCoder:] + 0 3 UIFoundation 0x00007ff804a1eb4d UINibDecoderDecodeObjectForValue + 352 4 UIFoundation 0x00007ff804a1eebe UINibDecoderDecodeObjectForValue + 1233 5 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 6 UIKitCore 0x000000010e566a9f -[UIView initWithCoder:] + 1327 7 UIKitCore 0x000000010e4ed417 -[UIScrollView initWithCoder:] + 65 8 UIKitCore 0x000000010e34cbd5 -[UITextView initWithCoder:] + 65 9 UIFoundation 0x00007ff804a1ecb4 UINibDecoderDecodeObjectForValue + 711 10 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 11 UIKitCore 0x000000010d97e7f0 -[UIRuntimeConnection initWithCoder:] + 160 12 UIFoundation 0x00007ff804a1ecb4 UINibDecoderDecodeObjectForValue + 711 13 UIFoundation 0x00007ff804a1eebe UINibDecoderDecodeObjectForValue + 1233 14 UIFoundation 0x00007ff804a1e9e2 -[UINibDecoder decodeObjectForKey:] + 257 15 UIKitCore 0x000000010d977a79 -[NSCoder(UIIBDependencyInjectionInternal) _decodeObjectsWithSourceSegueTemplate:creator:sender:forKey:] + 447 16 UIKitCore 0x000000010d97a77e -[UINib instantiateWithOwner:options:] + 1118 17 UIKitCore 0x000000010d532dab -[UIViewController loadView] + 643 18 UIKitCore 0x000000010d533128 -[UIViewController loadViewIfRequired] + 129 19 UIKitCore 0x000000010d533960 -[UIViewController view] + 27 .... Has anyone found the solution to this issue? This is preventing us from fully validating our iPadOS 17 upgrade builds. Thanks in advance.

I was hopeful that I would be able to record video from an external action camera such as the DJI Action Cam 3. The DJI action cam has a webcam mode that can be enabled as soon as one plugs it to a device, such as a macbook or an iPad. On the Macbook, the DJI shows up as an external camera for use in facetime or quicktime. But when I plug it into the iPad and use the AVCam sample from here, I notice that the camera preview comes up when the AVCam app is in photo mode but as soon as I switch the video mode, the preview layer hangs. No error message or AVCaptureSession errors that I could see. The same code works when using the Apple studio as an external camera. Curious if anyone has had any luck figuring this out? So near yet so far.

Download this Apple Speech Project https://developer.apple.com/documentation/accessibility/wwdc21_challenge_speech_synthesizer_simulator The project uses IOS15 deployment, when building and running I receive below errors. Setting deployment to IOS17 results in same errors. Appreciate if anyone else has determined how to re-engage this basic functionality. TTS appears to no longer to work. __ Folder ), NSFilePath=/Library/Developer/CoreSimulator/Volumes/iOS_21A5277g/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/TTSPlugins, NSUnderlyingError=0x600000c75d40 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} Failed to get sandbox extensions Query for com.apple.MobileAsset.VoiceServicesVocalizerVoice failed: 2 #FactoryInstall Unable to query results, error: 5 Unable to list voice folder Query for com.apple.MobileAsset.VoiceServices.GryphonVoice failed: 2 Unable to list voice folder Query for com.apple.MobileAsset.VoiceServices.CustomVoice failed: 2 Unable to list voice folder Query for com.apple.MobileAsset.VoiceServices.GryphonVoice failed: 2 Unable to list voice folder

Hello, When I try to install the iPadOS 17 public beta, my 32GB iPad says that it needs 13GB free to install the update! Is there a way to update to the beta without freeing up so much space? This is my main iPad so I don't want to reset it, but can I do it using Finder etc? Bye!

Hello, I am turning to this forum because I suspect I am "doing it wrong" when it comes to implementing VoiceOver accessibility in my collection view. I suspect this because the system has resisted everything I have tried to do, fought it tooth and nail, and I can't see any way to get this to work. The Collection View I have a collection view that displays a large dataset. It uses a custom collection view layout to create a spreadsheet-like view. It has hundreds of rows, and each row can have hundreds of items. The items in each row do not conform to specific column widths. Their width is defined by the data they display, and for the purposes of this discussion, can be considered to be arbitrary. To the left of the "table" is a column of sticky headers whose position remains fixed in relation to the content. On top of the "table" is a row of headers, whose position also remains fixed. The Problem The default accessibility behavior that Apple has baked into UICollectionView is completely impractical for this application. Each row can contain hundreds of items, so a user who is attempting to navigate by swiping right would have to swipe through hundreds of items just to reach the second row (of hundreds). The Desired Behavior I want the user to be able to swipe through just the cells that are onscreen. To scroll, they can use the standard three-finger gesture. When scrolling occurs, VoiceOver should announce the range of data that is being displayed. Attempted Solution 1: Setting the accessibilityElements array I can set the accessibilityElements array of the UICollectionView to only contain the elements that are onscreen. I also can override the accessibilityScroll method to perform the paging upon a three-finger scroll. This works okay, but has some pretty fatal flaws: As the user swipes through elements, the collection view insists upon scrolling horizontally to try and fit the element into view. It also insists upon scrolling vertically to keep the focused element in the middle of the view. This not only causes the content offset to jump around wildly in a disorienting way, but it also brings content into view that VoiceOver does not know about because I have not added it to the accessibilityElements array. A low-vision user, or a user who pans their finger across the screen, would not be able to access those visible elements. VoiceOver refuses to read my paging announcement. No matter when I post a pageScrolled notification, the system will not read it. Setting accessibilityFrame In an attempt to fix the scroll jumping described above, I tried setting the accessibilityFrame of my collection view cells. This did nothing to alter the scroll jumping behavior, and had the added downside that, as the view jumped around, the accessibility frames did not follow it. A bridge too far? Overriding contentOffset I was about to override contentOffset on the collection view so that only I could set it. That would probably work. But it would do nothing to fix the paging announcement. Attempted Solution 2: Ignore the Cells! Use proxy UIAccessibilityElements I tried setting the accessibilityElements array of my collection view to a collection of UIAccessibilityElement instances whose accessibilityFrame matched the frame of the cells they represent. This worked pretty well! No more scrolling nonsense when swiping through cells, and my paging announcements were being read. This approach has a different, equally fatal flaw: If the user attempts to three finger-scroll too quickly, the VoiceOver process will become confused. It acts as though the last selected element is the only element that exists; swiping right or left does nothing. Three finger-scrolling also does nothing. As best as I can tell, it gets stuck with the last selected element as the only one it knows about. I have since replaced all of the elements in the collection view's accessibilityElements array and posted a layoutDidChange notification, which VoiceOver ignores completely. The only way out of this state is to tap on a cell, causing VoiceOver to refresh its collection of views that it knows about. I guess? No idea what's happening there. Now what? I'm at a complete and total loss. I'm at my wit's end. It feels like this seemingly simple customization is entirely impossible. Does anyone know what I'm doing wrong? Thanks!

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

Unable to find where this is happening... *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSCountableTextLocation compare:] receiving unmatching type (null)' *** First throw call stack: ( 0 CoreFoundation 0x000000012083f88a __exceptionPreprocess + 242 1 libobjc.A.dylib 0x0000000117674894 objc_exception_throw + 48 2 CoreFoundation 0x000000012083f768 -[NSException initWithCoder:] + 0 3 UIFoundation 0x000000014ee60aa5 -[NSCountableTextLocation compare:] + 200 4 UIFoundation 0x000000014ee25919 -[NSTextLayoutManager _invalidateLayoutForTextRange:hard:] + 1573 5 UIFoundation 0x000000014ee26102 -[NSTextLayoutManager processLayoutInvalidationForTextRange:synchronizing:] + 32 6 CoreFoundation 0x00000001207a01bd __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7 7 CoreFoundation 0x0000000120721d57 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 285 8 UIFoundation 0x000000014ee83e49 __54-[NSTextContentManager synchronizeTextLayoutManagers:]_block_invoke + 78 9 CoreFoundation 0x00000001207a01bd __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7 10 CoreFoundation 0x0000000120721d57 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 285 11 UIFoundation 0x000000014ee83dc6 -[NSTextContentManager synchronizeTextLayoutManagers:] + 85 12 UIFoundation 0x000000014ee85f51 -[NSTextContentStorage synchronizeTextLayoutManagers:] + 61 13 UIFoundation 0x000000014ee84780 -[NSTextContentStorage setAttributedString:] + 162 14 UIFoundation 0x000000014ee84488 -[NSTextContentStorage dealloc] + 29 15 libobjc.A.dylib 0x0000000117672228 _ZN11objc_object17sidetable_releaseEbb + 204 16 UIKitCore 0x000000013f3d5297 -[_UITextKit2LayoutController .cxx_destruct] + 94 17 libobjc.A.dylib 0x0000000117652766 _ZL27object_cxxDestructFromClassP11objc_objectP10objc_class + 83 18 libobjc.A.dylib 0x000000011766adfc objc_destructInstance + 61 19 libobjc.A.dylib 0x000000011767176c -[NSObject dealloc] + 19 20 UIKitCore 0x000000013f3ceb68 -[_UITextKit2LayoutController dealloc] + 119 21 libobjc.A.dylib 0x0000000117672228 _ZN11objc_object17sidetable_releaseEbb + 204 22 UIKitCore 0x000000013fee4aea -[UITextField .cxx_destruct] + 343 23 libobjc.A.dylib 0x0000000117652766 _ZL27object_cxxDestructFromClassP11objc_objectP10objc_class + 83 24 libobjc.A.dylib 0x000000011766adfc objc_destructInstance + 61 25 libobjc.A.dylib 0x000000011767176c -[NSObject dealloc] + 19 26 UIKitCore 0x000000013fade794 -[UIResponder dealloc] + 145 27 UIKit 0x0000000171b2e9ef -[UIResponderAccessibility dealloc] + 55 28 UIKitCore 0x00000001401311e4 -[UIView dealloc] + 1330 29 UIKitCore 0x000000013fec9441 -[UITextField dealloc] + 272 30 libobjc.A.dylib 0x0000000117672228 _ZN11objc_object17sidetable_releaseEbb + 204 31 CoreFoundation 0x000000012085cf54 __RELEASE_OBJECTS_IN_THE_SET__ + 144 32 CoreFoundation 0x000000012085ce7d -[__NSSetM dealloc] + 130 33 libobjc.A.dylib 0x0000000117672228 _ZN11objc_object17sidetable_releaseEbb + 204 34 UIKitCore 0x0000000140026766 -[_UILayoutArrangement .cxx_destruct] + 128 35 libobjc.A.dylib 0x0000000117652766 _ZL27object_cxxDestructFromClassP11objc_objectP10objc_class + 83 36 libobjc.A.dylib 0x000000011766adfc objc_destructInstance + 61 37 libobjc.A.dylib 0x000000011767176c -[NSObject dealloc] + 19 38 UIKitCore 0x000000014001d85e -[_UIAlignedLayoutArrangement dealloc] + 325 39 libobjc.A.dylib 0x0000000117672228 _ZN11objc_object17sidetable_releaseEbb + 204 40 CoreFoundation 0x0000000120725152 __RELEASE_OBJECTS_IN_THE_ARRAY__ + 124 41 CoreFoundation 0x000000012072508f -[__NSArrayM dealloc] + 130 ... ...

We are using a ListView which contains Section views and some of those sections contains footer text. We are seeing an issue where the footer doesn't layout correctly when switching from 1/2 to 1/3 Split View sizes. This results in the footer truncating or in some cases removing the last few lines with no ellipsis indicating that the view is correctly laid out but the list footer view is not respecting the intrinsic size of the Text view. I wondered if we are doing something wrong but I was able to reproduce in a clean project with the following code struct ListView: View { let string = "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." @ScaledMetric var spacing: CGFloat = 18 var body: some View { NavigationView { List { Section { Text("Some content cell") } footer: { Text(string) } } } .navigationViewStyle(.stack) } } Before screen size change After screen size change Interestingly changing dynamic font size after this lets the view layout correctly. Does anyone know why this could be happening or if there's some way we can resolve this issue? Thanks

Configuration: iPad Pro (10.5-inch) iPadOS 17 beta 4 USB USV Camera Nexigo N940P 2K Apple Lightning to USB 3 Camera Adapter Attaching the adapter to the iPad caused it to update driver software - so far ok Next attached USB Camera to adapter and iPad complained "Not Enough Power ...". Attached power to lighting port of adapter. Above warning cleared. FaceTime didn't recognize the External Camera. I went through the usual unplug routine with no luck. Xcode sees the iPad so I executed the Objective-C version of AVCam from the presentation and added breakpoints at "AVCaptureDeviceDiscoverySession *externalVideoDeviceDiscoverySession = [AVCaptureDeviceDiscoverySession discoverySessionWithDeviceTypes:@[AVCaptureDeviceTypeExternal] mediaType:AVMediaTypeVideo position:AVCaptureDevicePositionUnspecified];" The externalVideoDeviceDiscoverySession shows no attached camera. Does anyone have a suggestion for debugging this? Or share your working setup? Thanks!

I'm working on an .html file. On Safari iOS/iPad, when testing on my local web server I get correct values for window.innerHeight. However when uploading to a dev/prod environment innerHeight is incorrect (so the elements in the page do not fit the screen). Testing on ipad air 3rd gen, IpadOS 16.5.1 I get these values for window.innerHeight : local server, navigation bar only (landscape): 764 => correct local server, navigation bar and tab bar (landscape): 731=> correct dev/prod environment, navigation bar only (landscape): 795 => incorrect dev/prod environment, navigation bar and tab bar (landscape): 795 => incorrect I have a similar issue when testing on portrait. InnerHeight is bigger than it should be and doesn't change when the tab bar is open. QA team also tested on Iphones and gets the same issue. Tried alternatives (visualViewport.height, 100vh, documentElement.clientHeight...they all are incorrect on a real environment)

The Problem In the Preview app in macOS (or the Files app in iOS and iPadOS), when a user selects a radio button to "On", the radio button appears to behave as expected (with related radio buttons, sharing the same parent form field, appearing to turn "Off"). Also, as expected, the app indicates that the user has edited the PDF and, as such, is able to save and close the file as normal. On re-opening the file, the radio buttons seem to have been reset and user input lost. What is Happening Related radio button annotation widgets share the same parent form field. In the PDF 1.7 specification (ISO PDF32000-2008, s. 12.7.4.2.4), the parent form field object holds the field name property (T), the name object of the appearance state of the kid object currently selected (V), as well as an array of the references to the related radio button kid objects (Kids). Each kid object holds a reference to the parent object (Parent). When the user selects a radio button to be on, the V property is updated in the parent object accordingly. On saving the PDF, an incremental update to the file is made with an updated copy of the kid object, corresponding to the selected radio box, created. The kid object created for the updated radio box, however, is updated incorrectly with the Parent object reference removed and the properties that ought to reside with the parent object (for V, T, and FT), instead, incorrectly written/merged into the kid object itself. The original parent object (belonging to the shared field form) is not updated with the incremental update in any way. Impact on User Experience Radio buttons are not functional, with user-input not properly saved. As such, using Preview to complete a PDF form with radio buttons is not possible. On re-opening the PDF, user input to the state of radio buttons appear not to have been saved. Affected Apps/OSs: Preview (macOS 12 and above) and Files (iOS 16 and iPadOS 16) Related Sample of Code Radio button annotation widget object (11 0 obj) and form field parent object (16 0 obj) in original PDF file: 11 0 obj << /Border [ 0 0 0 ] /Rect [ 433 405 453 425 ] /F 4 /BS 13 0 R /Subtype /Widget /DA (/Helvetica 13 Tf 0 g) /MK 14 0 R /C [ 0 ] /AP 15 0 R /M (D:20230803164805Z00'00') /AS /Off /Parent 16 0 R /Type /Annot /Ff 32768 >> endobj 16 0 obj << /V / /Kids [ 10 0 R 11 0 R ] /T (button2) /FT /Btn >> endobj 15 0 obj << /N 17 0 R >> endobj 17 0 obj << /Ted 18 0 R /Off 20 0 R >> endobj Copy of object (11 0 obj) created with incremental update of PDF, included in saved file following user selection: 11 0 obj << /C [ 0 ] /FT /Btn /F 4 /BS << /W 0 >> /Subtype /Widget /DA (//Helvetica 13 Tf 0 g) /Type /Annot /Border [ 0 0 0 ] /M (D:20230803164805Z00'00') /Rect [ 433 405 453 425 ] /MK << /BG [ 0.75 ] >> /AP << /N << /Off 53 0 R /Ted 57 0 R >> >> /T (button2) /AS /Ted /Ff 32768 /V /Ted >> endobj A bug report, describing as much, was submitted to Apple (FB9978281).