Post not yet marked as solved
Anybody found a solution to this? Navigation UX is degraded in SwiftUI, without a proper highlight on touch down in the button.
Has this been solved? I encounter that very same issue with Xcode 15 (final version)
Post not yet marked as solved
Any news on this? This can mess up soooo much with the UX
Post not yet marked as solved
My lightning cable was going through my LG 5k. Plugged it in directly into the mac, seems to work for now. I lost so many days fighting this.
Post not yet marked as solved
This makes watch development a real pain.
Post not yet marked as solved
See: https://github.com/steipete/SwiftUITouchHandling
Post not yet marked as solved
Same experience here, when modifications are in the scope of a "lightweight migration"
Post not yet marked as solved
Did you find a solution to this?
Post not yet marked as solved
I have a similar error (Xcode 14). My watchOS dev has been a nightmare so far, just because of the impossibility of testing.
The app cannot be installed:
This app contains a WatchKit app with an invalid bundle identifier. The bundle identifier of a WatchKit app must have a prefix consisting of the companion app's bundle identifier, followed by a '.'.
iOS app id : com.me.appname
Watch app id : come.me.appname.watchkitapp
Note: Xcode 14 does not create a target watch extension anymore.
WARNING: Bug present on iOS 16 RC (possibly on earlier versions of iOS 16 beta): if interaction.preferredInteractionTypes = [.automatic], attempting to translate the text using the ad-hoc button will fail. Nothing happens.
As a workaround, I used interaction.preferredInteractionTypes = [.textSelection, .dataDetectors] which makes the translation work.
Post not yet marked as solved
Thank you! It indeed makes sense. And you save me a headache :-).
My shortcut works, but only when selecting a PDF from the finder.
If the shortcut is configured as a quick action, I can't manage to get the file. The INFile is nil.
Any idea why? Thanks!
Post not yet marked as solved
Same issue here, with the exact situation (pdf), except that I'm only using the main app for now.
Btw, did you manage to receive the file from the quick action input?
Post not yet marked as solved
override init()call super.init()Replace the ManagedObjectContext created by your own:self.managedObjectContext = yourMocAccess the document's context as usual, and you will get your notifications
