Post not yet marked as solved
I experience an issue with SceneKit that is driving me crazy ;(
I have severe hangs when I disable Metal API Validation (which is default when you don't run from Xcode). So is there any way to force enable Metal API Validation for AppStore binary? (run MTL_DEBUG_LAYER=1 for Testflight or App Store)
Hangs happen on Catalyst but also on iOS if I use lightingEnvironment...
Post not yet marked as solved
We have an iOS app with a web View.
To develop and debug, we inspect the web view using Safari Dev Tools (Developer menu).
This Works: We are able to inspect the web view when the application is run on physical devices as well as on simulated devices (iPhone and iPad).
This Does NOT Work: We are not able to inspect the web view of the same app running, unmodified, on same Mac. Safari’s Developer menu says “No Inspectable Applications” against the Mac.
Requesting guidance or leads on ways to inspect and debug the app under these conditions. Many thanks!
Post not yet marked as solved
In our mac catalyst app we access AppKit api's by using MacOS bundle(plugin).
when using CGDisplayCreateImage(_: CGDirectDisplayID, rect: CGRect) method the plugin crashes.
Implementation:
@objc
func windowMoved(_ notification: NSNotification) {
guard let win = self.window else {
return
}
let displayId = CGMainDisplayID()
let winRect = win.contentView?.convert(qrRect, from: self)
var rect = win.convertToScreen(winRect ?? self.bounds)
if let screenFrame = NSScreen.main?.visibleFrame {
rect.origin.y = screenFrame.height - rect.maxY
rect.origin.y += screenFrame.minY + win.titlebarHeight
}
guard let image = CGDisplayCreateImage(
displayId,
rect: rect) else {
return
}
guard let qrString = image.detectQRCode().first else { return }
// ...
}
Crash report in printed in console:
-[RPDaemonProxy proxyCoreGraphicsWithMethodType:config:machPort:completionHandler:]: unrecognized selector sent to instance 0x600000500960
(
0 CoreFoundation 0x00000001931deccc __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000192cc6788 objc_exception_throw + 60
2 CoreFoundation 0x000000019329102c -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x0000000193148a80 ___forwarding___ + 976
4 CoreFoundation 0x00000001931485f0 _CF_forwarding_prep_0 + 96
5 ScreenCaptureKit 0x0000000227d9d95c SLSHWCaptureDesktopProxying + 692
6 SkyLight 0x0000000198b370a8 SLSHWCaptureDesktop + 488
7 SkyLight 0x0000000198b3b1ac SLSDisplayCreateImage + 252
8 MacPlugin 0x0000000112e0d374 $s9MacPlugin14MZMacQrScannerC11windowMovedyySo14NSNotificationCF + 1500
9 MacPlugin 0x0000000112e0d714 $s9MacPlugin14MZMacQrScannerC11windowMovedyySo14NSNotificationCFTo + 52
10 CoreFoundation 0x000000019315eb1c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148
11 CoreFoundation 0x00000001931f2db8 ___CFXRegistrationPost_block_invoke + 88
12 CoreFoundation 0x00000001931f2d00 _CFXRegistrationPost + 440
13 CoreFoundation 0x000000019312d648 _CFXNotificationPost + 768
14 Foundation 0x0000000194249434 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
15 AppKit 0x00000001969ffbfc -[NSWindow _setFrameCommon:display:fromServer:] + 2056
16 AppKit 0x0000000197475080 -[NSWindow _windowMovedToRect:dueToMoveEvent:] + 184
17 AppKit 0x0000000196ae8630 -[NSWindow _windowMoved:] + 832
18 AppKit 0x0000000196ae82a4 -[NSWindow _internalHandleAppKitDefinedEvent:] + 152
19 AppKit 0x0000000196ae8074 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 528
20 AppKit 0x0000000196ae7c90 -[NSWindow(NSEventRouting) sendEvent:] + 284
21 AppKit 0x00000001971adda8 -[NSApplication(NSEventRouting) sendEvent:] + 1800
22 UIKitMacHelper 0x00000001acb964f8 -[NSApplication(UINSApplicationSwizzling) _uinsSwizzledSendEvent:] + 252
23 AppKit 0x0000000196dfb954 -[NSApplication _handleEvent:] + 60
24 AppKit 0x00000001969afd24 -[NSApplication run] + 512
25 AppKit 0x0000000196986fa4 NSApplicationMain + 880
26 AppKit 0x0000000196bd9798 +[NSWindow _savedFrameFromString:] + 0
27 UIKitMacHelper 0x00000001acb82198 UINSApplicationMain + 972
28 UIKitCore 0x00000001c2ea2924 UIApplicationMain + 148
29 MyApp-DEBUG 0x00000001049d2d04 main + 64
30 dyld 0x0000000192d020e0 start + 2360
This is working fine in all previous version but crashing in macOS beta 14.4 and 14.4.1.
I wanted to post this here in the hope that this will draw attention to what I think is a serious change in behavior that could negatively affect Catalyst apps in macOS 14.4.
Prior to macOS 14.4, when the completion handler was invoked from calling dismiss() to dismiss a presented view controller in a Catalyst app, the dismissed controller no longer appeared in the chain. That is to say that if the root view controller presents View Controller A, when View Controller A is dismissed, the root view controller's presentedViewController property is nil when the completion handler for dismiss() is called.
With macOS 14.4, this is no longer the case. If the root view controller presents View Controller A and then View Controller A is dismissed, the presentedViewController property of the root view controller still refers to Controller A when dismiss()'s completion handler is called.
The side effect of this change in behavior means that if you try to present another view controller from the completion handler of the one being dismissed, it will fail to show because the top most view controller in the chain is the controller being dismissed and presenting from it will result in nothing showing up because it is removed from the chain immediately after the completion handler is invoked. Before macOS 14.4, it the top of the chain would have been the controller that presented the controller that was dismissed, which is what you actually want.
This problem does not exist in the betas for iOS 17.4 or iPadOS 17.4. It appears to affect only Catalyst apps running under macOS 1.4.4.
I think this change in behavior has the potential to affect a number existing Catalyst apps and it may not be obvious to the user something is going wrong. It really should be fixed before macOS 14.4 is released to the public.
I've created a feedback with a sample Xcode project that demonstrates the problem (feedback number FB13622757).
Post not yet marked as solved
Running in a Mac (Catalyst) target or Apple Silicon (designed for iPad).
Just accessing the playbackStoreID from the MPMediaItem shows this error in the console:
-[ITMediaItem valueForMPMediaEntityProperty:]: Unhandled MPMediaEntityProperty subscriptionStoreItemAdamID.
The value returned is always “”.
This works as expected on iOS and iPadOS, returning a valid playbackStoreID.
import SwiftUI
import MediaPlayer
@main
struct PSIDDemoApp: App {
var body: some Scene {
WindowGroup {
Text("playbackStoreID demo")
.task {
let authResult = await MPMediaLibrary.requestAuthorization()
if authResult == .authorized {
if let item = MPMediaQuery.songs().items?.first {
let persistentID = item.persistentID
let playbackStoreID = item.playbackStoreID // <--- Here
print("Item \(persistentID), \(playbackStoreID)")
}
}
}
}
}
}
Xcode 15.1, also tested with Xcode 15.3 beta 2.
MacOS Sonoma 14.3.1
FB13607631
Post not yet marked as solved
It appears the app is sandboxed. I need to be able to access the broader file-system and pick a folder/file. Is this possible?
Is it possible to invoke the app with a command-line argument? If so, how is it accessed (in code)?
Post not yet marked as solved
While I'm keen on being on the latest version of macOS, I'm having trouble meeting the requirement that my app can run on a version of macOS that doesn't exist :)
I'm using Xcode 15.2 (15C500b), targeting iOS 17.2.
I've elected to have the App Store choose the minimum version for Catalyst. I've also tried selecting a version.
ITMS-90899: Apple silicon Mac support issue - The app is not compatible with the provided minimum macOS version of 14.2. It can run on macOS 14.4 or later. Please specify an LSMinimumSystemVersion value of 14.4 or later in a new build, or select a compatible version in App Store Connect. For details, visit: ...
Is there something I could be doing wrong to prompt this behaviour?
Post not yet marked as solved
Running a Process executableURL path for a Catalyst target using a macOS type bundle returns the following error as output:
(/Applications/Xcode-15.1.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Debugger/libViewDebuggerSupport_macCatalyst.dylib), but incompatible platform (have \'MacCatalyst\', need \'macOS\'))
Is it possible to set which dylib platform is used by the macOS bundle executable file instead of using the MacCatalyst one?
Post not yet marked as solved
Hello,
I am working on an AUv3 extension project using SwiftUI in Xcode and have encountered a peculiar issue when implementing a simple alert on Mac Catalyst. The code is straightforward; it's merely an alert triggered by a button within a SwiftUI view. Here's the relevant portion of the code:
import SwiftUI
struct SwiftAUv3ExtensionMainView: View {
var parameterTree: ObservableAUParameterGroup
@State var showingAlert = false
var body: some View {
VStack {
ParameterSlider(param: parameterTree.global.gain)
Button(action: {showingAlert = true}, label: {
Text("Button")
})
}
.alert("Alert", isPresented: $showingAlert, actions: {}, message: { Text("Message") })
}
}
The problem arises when this alert is displayed and subsequently closed. Upon closing the alert, the cursor turns into a spinning rainbow and the app freezes for several seconds. Additionally, Xcode's console displays the warning: -[NSWindow makeKeyWindow] called on _NSAlertPanel which returned NO from -[NSWindow canBecomeKeyWindow].
I am looking for insights or solutions to address this issue. Has anyone else experienced similar problems with SwiftUI alerts in AUv3 extension projects, especially when using Mac Catalyst? Any advice or suggestions would be greatly appreciated.
Thank you.
Post not yet marked as solved
I am trying to add a keyboard shortcut to an existing standard Menu Bar Button such as "Tile Window to Left of Screen".
I've tried the different .command modifiers but could not find a way to get access to the existing ones in order to add a keyboard shortcut.
Thanks for your help in advance
Anyone knows about any workarounds for this crash "Spatial presentations are not permitted from popovers."
Post not yet marked as solved
Crash seems to be in a private Apple framework. There's some other reports of this floating around but no solutions so far. Any ideas?
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[WebAVPlayerLayer startRedirectingVideoToLayer:forMode:]: unrecognized selector sent to instance 0x6000037033c0'
*** First throw call stack:
(
0 CoreFoundation 0x0000000187d56800 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x000000018784deb4 objc_exception_throw + 60
2 CoreFoundation 0x0000000187e083bc -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x0000000187cc0a84 forwarding + 1572
4 CoreFoundation 0x0000000187cc03a0 _CF_forwarding_prep_0 + 96
5 AVKit 0x00000001bdc81f30 -[__AVPlayerLayerView startRoutingVideoToPictureInPicturePlayerLayerView] + 156
6 AVKit 0x00000001bdcf1d48 -[AVPictureInPicturePlatformAdapter(Common) _setRoutingVideoToHostedWindow:pictureInPictureViewController:source:] + 84
7 AVKit 0x00000001bdcd952c -[AVPictureInPicturePlatformAdapter startPictureInPicture] + 380
8 AVKit 0x000000022883000c -[AVPictureInPicturePlatformAdapterAccessibility startPictureInPicture] + 44
9 AVKit 0x00000001bdcddea0 -[AVPictureInPictureController startPictureInPicture] + 216
10 WebCore 0x00000001c75277c8 -[WebAVPlayerViewController startPictureInPicture] + 128
11 libdispatch.dylib 0x0000000102c64f14 _dispatch_call_block_and_release + 32
Post not yet marked as solved
Hello all, I'm porting my existing app to catalyst with optimized for mac option. However, I noticed the app will sometimes restore previous open windows if I previously kill it in Xcode. However, these restored windows are also just showing the app entry content instead of restoring the previous scene content. Question, is there anyway to disable this restore scene behavior? Thanks!
Post not yet marked as solved
I have a button in my iOS app that opens the Settings app to my app's Notification permissions section. I use UIApplicationOpenSettingsURLString for this (or UIApplicationOpenNotificationSettingsURLString on iOS 15.4 and later). On Catalyst, both of these simply open the settings screen that is auto-generated from the Settings bundle.
How do I get it to open to the appropriate place in System Settings?
Post not yet marked as solved
With Mac Catalyst, in Big Sur and Monterey, you could use UICommandTagShare as the property list for a UICommand in combination with activityItemsConfiguration and itemProvidersForActivityItemsConfiguration to allow a "Share" submenu to appear in a menu in your app (for instance, under the File menu like many other apps).
Starting in Ventura, this submenu no longer appears with that same code, and instead the UICommandTagShare command in the menu now just displays "Share" with no submenu, which triggers a UIActivityViewController to appear in the main window.
Is there any way to still allow a Share submenu to work in Ventura and beyond with Mac Catalyst? Thanks so much for any help!
Post not yet marked as solved
I was loading a URL using SFSafariViewController in my app and also implemented the SFSafariViewControllerDelegate. I noticed that when I am running my app on iOS, I am not getting the callBack in safariViewControllerDidFinish(_:) until or unless "Done" button is pressed. But when I am running it on MacCatalyst following behaviour is noticed:
default browser is launched.
I get a callback in safariViewControllerDidFinish(_:) without any of my action(like pressing "Done" button).
Is this the expected behaviour? I am curious to know why I am getting callback in safariViewControllerDidFinish(_:).
Post not yet marked as solved
List items do not appear to be moveable when they are contained within a popover on Mac Catalyst running on macOS Sonoma. Dragging and dropping a list item simply returns it to its original location, and onMove(preform:) is not called. The same happens using the drag handles with an EditButton() or .environment(\.editMode, .constant(.active)).
Below is a reproducible sample which, to my knowledge, worked as expected on Ventura. It also currently works as expected on iPad. Changing the popover to a sheet makes it work on Mac Catalyst, but then, the view takes up a lot of unnecessary space.
Does anyone have any good workarounds for this issue?
struct ContentView: View {
@State private var isShowingPopover = false
@State private var items = ["one", "two", "three"]
var body: some View {
Button("Show Popover") {
isShowingPopover = true
}
.popover(isPresented: $isShowingPopover) {
List {
ForEach(items, id: \.self) { item in
Text(item)
}
.onMove { fromOffsets, toOffset in
items.move(fromOffsets: fromOffsets, toOffset: toOffset)
}
}
.frame(minWidth: 300, minHeight: 270)
}
}
}
Is there a way to link a prebuilt dylib that was built for the 'macOS' platform on Mac Catalyst without being warned by Xcode?
Generally it would be better to just recompile for Mac Catalyst but this is a third party library and they have a complicated build system with dozens of dependencies that doesn't support Mac Catalyst as of now (although they have iOS and Mac 'regular'). So I would have to spend quite a bit of time trying to sort through their build system to make a Catalyst version myself.
The library uses no platform specific UI code and I'm fairly certain that macOS build would work just fine on Mac Catalyst without any changes since it isn't UI related at all.
It seems to work fine (apart from Xcode warning me about linking a .dylib built for macOS on Mac Catalyst).
I could shim all this away in a NSBundle that is aware of the AppKit world but then I have to make all method calls to the third party framework on Mac Catalyst through the bundle and it would separate my iOS and Catalyst code relying on the same implementation which isn't great.
Is there a way I could just replace the 'macOS' platform in the .dylib with macCatalyst to get rid of the warning?
Post not yet marked as solved
Hello,
is there a recommended way to render Menu items, e.g in a SwiftUI ContextMenu with icon (SFSymbols)?
Let's say I have the following setup:
Both buttons render fine on native macOS (e.g Sonoma) but Catalyst refuses to render the symbol at all. I tried every possible combination I could think off. The only way I found was to directly copy and paste a symbol from the SF symbols app and inline it with the label string as unicode. Unfortunately I have a couple custom SF symbols so this isn't really an option for me.
I feel like this is a perfectly valid usecase, as it makes the menu visually a lot easier scannable.
With UIKit and Ventura this at least worked for Menubar items but now also seems broken on Sonoma.
I would greatly appreciate any hints. Thanks!
Post not yet marked as solved
Can not select anything within WkWebView editor view of my MacCatalyst app when running on macOS 14 Sonoma.
Any selection gesture or command key fails to select anything in content editable WKWebView, so none of the Editor tools can be activated.
My application uses the nnhubbard / ZSSRichTextEditor WKWebView-based Rich Text Editor: https://github.com/nnhubbard/ZSSRichTextEditor. The app is built with Xcode 15.0 or 15.0.1.
The app is a Catalyst app that implements an editor view with a ZSSRichTextEditor WKWebView.
The problem does not occur if the the app is run in iOS or macOS 11, 12, or 13 (Catalina, Monterey, or Ventura.) The issue only occurs in macOS 14 Sonoma.
