I just filed a bug report for the Notes app as follows:Area: Notes Summary: When opening Notes with content that is larger than the open Notes App window, and attempting to edit the note, the entire note content scrolls automatically to the top although the cursor remains where text editing was inserted. Typing on the Smart Keyboard will allow text entry however the note insistently keeps scrolling to the top regardless of how often or how much text is entered into the note. Scrolling the note manually with your touch will stop the action from occurring, however that is intermittent and sometimes will scroll automatically as well. This issue will occur on both iPad and iPhone and regardless of the app is used full screen on the iPad or in Split Screen. When the Notes window is not focused and the user is engaging an app in the other split screen window, the Note window does not scroll, only when it is the focused App. Steps to Reproduce: 1. Open Notes2. Begin to edit the note by scrolling down and selecting text or placing your cursor to enter text.3. More likely to happen with a note which has enough text to enable scrolling of the note.Expected Results: The note body of text should not scroll while editing or entering text and should remain where placed either by scrolling to the place of entry with using touch or with moving the cursor with the direction keys of the Smart Keyboard. Actual Results: The note scrolls on its own without intervention. Version: IOS Beta 10.0(14A5261v) Configuration: iPad Pro 12.9" and iPhone 6S both with iOS beta 10.0

I installed and test the simulator in Xcode beta 2. Stage Manager was missing from the settings in the iPad simulators (iOS 16). This was tested on both Intel mac and M1 mac. Xcode release notes states that it should be possible, but the setting seems missing. https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes

Hi there, I would like to remove the iOS 16 beta but the beta profile is no longer displayed to me

I currently have my setup like this: Apple TV 4K -> HDMI -> Denon X2400H -> HDMI -> X930ESo far this behavior only happens with the ATV, but randomly it seems that the TV gets in a funk where the screen for the Apple TV flashes on and off. Almost like a classic HDMI handshake problem. So far the ONLY thing that will fix this is to pull the power on the TV (not even turning off/on will fix it). Once I pull the power on the TV and it reboots, everything is fine again. It may return a day later....2 days later....it's random. It never happens while watching the ATV. It's always either turning the entire chain on or swtiching over from another source (Roku or PS4 for example).I have tried multiple certified cables, none seem to make a difference. I've tried powering off the other devices, that doesn't fix it. I'm thinking this is an Apple TV problem, but the X930E is what is being affected. So far the ATV is the only device that causes this and I haven't found a way to re-produce on my own. But I thinking it's something between the ATV and the Sony that's causing the issue.

Ibooks won't open at all.Says:Ibooks can't access libary Make sure the disk containing your library is connected, then click Try Again.Library Location: (null)You can also reset your library, then sign in to view and re-download your purchased books.

I have just installed Xcode 14 Beta but there is no option to make an AppleScript project. Is this no longer available ?

I joined the Developer program to install the iOS 16 Beta. Apple says you have to enable the Developer Tab under Privacy and Security in the Setting before downloading the software. currently I am using iOS 15.5 for which there is only Privacy instead of Privacy and Security in the Setting and no Developer option under same!! appreciate any help

After I had updated to iOS 16 beta to test it out, I had noticed that my esim had completely stopped working. I have now downgraded down to 15.5 to see if that fixes the issue. But I still have no esim and no way to connect to my carrier. I had tried to request a new esim off of my carrier’s website, but I didn’t work. I was wondering what to do to fix this issue.

Since the last update (21A5534d), my MacBook doesn't detect my 2nd display. I've tried swapping the display with a new one and trying different connection methods. My MacBook's built-in display goes black for a moment when I attach the cable, but nothing else happens. I seem to remember that the System Preferences > Displays used to have an option for manually detecting a display, but it doesn't appear to be there any more. I hope I'm not the only person experiencing this.

When using an Intents configuration with Widget Extension, the compiler will generate code for your configuration. But in Xcode 14, this generated code now contains warnings: Method 'confirm(intent:)' with Objective-C selector 'confirmConfiguration:completion:' conflicts with method 'confirm(intent:completion:)' with the same Objective-C selector; this is an error in Swift 6 It seems that in Xcode 14 this generated code now contains async versions of its methods, but that these methods have the same objc selectors as the non async versions: public protocol ConfigurationIntentHandling: NSObjectProtocol {     @objc(confirmConfiguration:completion:)     optional func confirm(intent: ConfigurationIntent, completion: @escaping (ConfigurationIntentResponse) -> Swift.Void)     @objc(confirmConfiguration:completion:)     optional func confirm(intent: ConfigurationIntent) async -> ConfigurationIntentResponse     @objc(handleConfiguration:completion:)     optional func handle(intent: ConfigurationIntent, completion: @escaping (ConfigurationIntentResponse) -> Swift.Void)     @objc(handleConfiguration:completion:)     optional func handle(intent: ConfigurationIntent) async -> ConfigurationIntentResponse } Is there a new way to handle widget configuration in Xcode 14? Or is this just a massive oversight? I have treat warnings as errors enabled (as everyone should) so this prevents my app from building. Filed as FB10338460

Hello there, Since I updated from Monterey (public Beta) to Ventura (public Beta) I am experiencing a native crash that it's like Apple's analytics is crashing when Avalonia tries to load an image (libAvaloniaNative.dylib). If I execute /Library/Frameworks/Mono.framework/Versions/6.12.0/bin/mono64 foo.exe (this is how VS for mac runs my application) my program runs with no issues, but if I execute /Library/Frameworks/Mono.framework/Versions/Current/bin/mono-sgen64 foo.exe (this is how Jetbrains Rider runs my application), then I get a native crash. The funny thing is that mono64 is an alias to mono-sgen64. Same results if I run this from the Terminal. This is happening since I updated my macOS to the new Ventura beta version. It's like executing mono from an alias works, but executing mono from the binary doesn't. Can anyone tell me something I can try to fix or workaround this to be able to debug from Rider? Please find attached the mono crash report. Thanks a lot in advance mono-sgen64-2022-07-15-124127.txt

Hi. I'm trying out some of the new MusicKit functionality using Xcode 14 beta 3 and macOS 13 beta 3 and I'm getting the above error (or similar) whenever I use any of the new classes with a Mac Catalyst destination (an iOS 16 destination works fine). I'm guessing one of my build settings is incorrect on either my project or target, but it's not obvious. So far I've set: Project / IOS Deployment Target = 16.0 Target / Minimum Deployments / iOS = 16.0 Could someone please tell me what I'm missing? Thanks in advance!

I just noticed, that iOS 16 is using the accent color for the navigation bar back button. (SwiftUI) When running my app on iOS 15 devices it's white. Is there a way to change that behavior? I want to have another accent color than white.

(Submitted to Apple's Developer Feedback) Randomly while I type (or don't), it will unfocus the main window and then refocus it. I've tried closing nearly every app but one, and it still seems to happen, so doesn't seem to be an app I'm using that causes this. It’s usually WHILE I’m typing, so it causes issues. Video explains. View video: https://www.loom.com/share/ed5971a47c204c819a2370d7fe0c8411 happens at 40 seconds in Has anyone else experienced this and or have a temp fix? It makes testing on this platform nearly impossible, I can't code on it, or use it for anything productive. Seems to only happen in latest beta 3 for Ventura.

When I generate an xctestrun file using Xcode 14 with: xcodebuild build-for-testing -project UITestTesting.xcodeproj -scheme UITestTesting -destination 'id=00008020-000545362EE1002E' -derivedDataPath ./build I'm able to see the xctestrun file at "/Users/noahmartin/Desktop/UITestTesting/Build/Build/Products/UITestTesting_iphoneos16.0-arm64.xctestrun" However, I can't use it to run tests on my iOS 16 iPad. I'm trying to invoke the test like this: xcodebuild test-without-building -xctestrun "/Users/noahmartin/Desktop/UITestTesting/Build/Build/Products/UITestTesting_iphoneos16.0-arm64.xctestrun " -destination 'id=00008020-000545362EE1002E' -derivedDataPath ./build And getting this error: xcodebuild: error: Unable to find a destination matching the provided destination specifier: { id:00008020-000545362EE1002E } Available destinations for the "Transient Testing" scheme: { platform:macOS, arch:arm64e, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64, id:00006001-0012198A0102801E } { platform:macOS, arch:x86_64, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64e, variant:Mac Catalyst, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64, variant:Mac Catalyst, id:00006001-0012198A0102801E } { platform:macOS, arch:x86_64, variant:Mac Catalyst, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64e, variant:DriverKit, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64, variant:DriverKit, id:00006001-0012198A0102801E } { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00006001-0012198A0102801E } { platform:iOS Simulator, id:3113F5B7-7358-4ADE-9660-667872D113A7, OS:16.0, name:iPad (9th generation) } { platform:iOS Simulator, id:D7232872-AC19-4DF1-BF18-D23C2C2A5BFE, OS:16.0, name:iPad Air (5th generation) } { platform:iOS Simulator, id:EE6444F9-2664-4907-9481-08CE44D028E9, OS:16.0, name:iPad Pro (9.7-inch) } { platform:iOS Simulator, id:10063708-10B3-4510-A41F-E948B2D09DB3, OS:16.0, name:iPad Pro (11-inch) (3rd generation) } { platform:iOS Simulator, id:794714E1-25E0-474A-BA79-F5E0EFA3E646, OS:16.0, name:iPad Pro (12.9-inch) (5th generation) } { platform:iOS Simulator, id:809FAD25-CFE5-44CA-B642-0FF2A0E638E5, OS:16.0, name:iPad mini (6th generation) } { platform:iOS Simulator, id:055D580A-859B-42F8-B306-BD8CB68BF1CC, OS:16.0, name:iPhone 8 } { platform:iOS Simulator, id:228440FE-9536-401D-9221-E909761468FE, OS:16.0, name:iPhone 8 Plus } { platform:iOS Simulator, id:D2F30B3E-32F9-44B2-9B02-20A1B6FEDFC3, OS:16.0, name:iPhone 11 } { platform:iOS Simulator, id:1677A963-4BBC-4DE3-896B-2D93FBF10A1B, OS:16.0, name:iPhone 11 Pro } { platform:iOS Simulator, id:67F569A4-B422-406F-961A-C9093F4EA861, OS:16.0, name:iPhone 11 Pro Max } { platform:iOS Simulator, id:927F62C4-CB4E-487A-B021-0A986B9B700A, OS:16.0, name:iPhone 12 } { platform:iOS Simulator, id:AAAE026B-A40E-4D84-9447-91B2034B6FDA, OS:16.0, name:iPhone 12 Pro } { platform:iOS Simulator, id:96E6D2AB-140B-496F-8C31-71A12412AB0C, OS:16.0, name:iPhone 12 Pro Max } { platform:iOS Simulator, id:B68ACAB0-A87A-4384-B9F8-63ECF09D9564, OS:16.0, name:iPhone 12 mini } { platform:iOS Simulator, id:E6FFBA89-6B9E-4A76-A99E-0510E1EFE97B, OS:16.0, name:iPhone 13 } { platform:iOS Simulator, id:0ECA5023-8C7B-4CFA-B264-E0539509E61A, OS:16.0, name:iPhone 13 Pro } { platform:iOS Simulator, id:203AC07C-503F-476E-9F14-DA7FA4D63131, OS:16.0, name:iPhone 13 Pro Max } { platform:iOS Simulator, id:16AA1AE3-1D75-4358-A4FB-8A73141A0551, OS:16.0, name:iPhone 13 mini } { platform:iOS Simulator, id:FAC28F61-2CF8-40C1-AB2D-64CE6F11B96B, OS:16.0, name:iPhone SE (3rd generation) } Ineligible destinations for the "Transient Testing" scheme: { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } { platform:macOS, name:Any Mac } { platform:macOS, variant:Mac Catalyst, name:Any Mac } { platform:tvOS, id:dvtdevice-DVTiOSDevicePlaceholder-appletvos:placeholder, name:Any tvOS Device } { platform:tvOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-appletvsimulator:placeholder, name:Any tvOS Simulator Device } { platform:watchOS, id:dvtdevice-DVTiOSDevicePlaceholder-watchos:placeholder, name:Any watchOS Device } { platform:watchOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-watchsimulator:placeholder, name:Any watchOS Simulator Device } I am able to launch the test directly from xcode, or with the "project" and "scheme" flags and xcodebuild test but I can't get the xctestrun file to work with iOS 16. This method works fine for iOS 15/Xcode 13. Is there anything I'm missing to make this work with the new betas? Also filed as FB10129497

Following the sample notes at https://developer.apple.com/documentation/widgetkit/creating-lock-screen-widgets-and-watch-complications, when I try to preview the Watch widget, I get an error saying: Cannot preview in this file WidgetEntryPointFactory' does not conform to NonUIEntryPoint RemoteHumanReadableError: Type 'WidgetEntryPointFactory' does not conform to NonUIEntryPoint (in framework at path /System/Library/PrivateFrameworks/ChronoCore.framework/Support/WidgetPreviewsExtensionAgent.bundle) ================================== |  MessageSendFailure: Message send failure for <ServiceMessage 187: update> App widgets preview fine though. Am I doing something obviously wrong?

I want to enroll my iphone 12 for the ios 16 public beta release but the program do not see my iphone. How can i correct that?