User Profile

Posts

Posts

Post not yet marked as solved
1 Replies
480 Views

Xcode auto completion incorrectly showing instance methods when initializing

Unlike before, now the auto-completion drop down menu displays instance methods that don't apply when you're only trying to instantiate a class. It's confusing because you now have to scroll up and down to find the correct initializer. I hope this isn't the intended behavior?
Posted
by Smithers.
Last updated
.
Post not yet marked as solved
2 Replies
1.5k Views

Will new API in iOS 14 for SwiftUI work on iOS 13?

I'd like to know if adopting future SwiftUI APIs would not require that I keep supporting only the latest and greatest versions of each OS (iOS / macOS / watchOS). In theory, would I still be able to at least support iOS 13 going forward, even if I were to use new API introduced in iOS 14 for SwiftUI? In theory the runtime bundled with our apps should be backward compatible with iOS 13?
Posted
by Smithers.
Last updated
.
Post not yet marked as solved
2 Replies
804 Views

DockTile plugin not working in Catalina

Our DockTilePlugin is no longer working on Catalina and I'm not sure what else I need to do to ensure it's codesigned properly. It's never given us any issues on earlier macOS versions. The error I see in Console is this:Error loading /path/to/MyApp.app/Contents/PlugIns/MyAppDockTile.docktileplugin/Contents/MacOS/MyAppDockTile: dlopen(/path/to/MyApp.app/Contents/PlugIns/MyAppDockTile.docktileplugin/Contents/MacOS/MyAppDockTile, 0x0109): code signature in (/path/to/MyApp.app/Contents/PlugIns/MyAppDockTile.docktileplugin/Contents/MacOS/MyAppDockTile) not valid for use in process: mapping process is a platform binary, but mapped file is notAny ideas?
Posted
by Smithers.
Last updated
.