Posts

Post marked as Apple Recommended
0 Views
I am seeing this starting yesterday. I raised a feedback request
Post not yet marked as solved
1 Replies
0 Views
Note, I have confirmed that all of background layers do not have an Alpha Channel, and are of the appropriate sizes.
Post not yet marked as solved
2 Replies
0 Views
Have opened a ticket with Apple and have been working thru suggestions.. still no resolution, but will post answer when it is resolved
Post not yet marked as solved
33 Replies
0 Views
I am still not seeing this work, I am the very latest developer beta, has this been enabled yet?
Post not yet marked as solved
2 Replies
0 Views
I am still seeing this error on my iMac, I can only deploy my code via my MBP at this time. Any suggestions would be appreciated.
Post marked as solved
1 Replies
0 Views
I'm closing this question for now, as deploying the same version of the app via the USB-C cable from the Xcode to the iPad worked. It now pulled the data from CloudKit.
Post not yet marked as solved
1 Replies
0 Views
I am having this same issue, have you figured out how to debug this? I have a project I’ve not worked on for about 5 months, and when I try to open it now.. Xcode hangs.
Post not yet marked as solved
4 Replies
0 Views
What was your ultimate issue here.. I am trying to covert a Core Data UIKit App to SwiftUI Architecture, and I am getting this in previews and when I launch in the Simulator, The app launches and the immediately shuts down (closing the debug window).
Post not yet marked as solved
2 Replies
0 Views
Well, I tired to get some help on StackOverflow and they didn't get the issue... https://stackoverflow.com/questions/64082376/couldnt-cast-swiftui-extensiondelegate-to-extensiondelegate/64085463#64085463 - Just to be clear, it is not a problem with @environmentObjects - that is working well - passing between the various views... the issue is with passing to a class.
Post marked as solved
1 Replies
0 Views
Resolved.. problem was button shapes were causing SwiftUI on tvOS to not process correctly.. went back to "default" buttons.. and works as expected.
Post marked as solved
20 Replies
0 Views
I am also getting this same error message - Invalid Swift 2020-09-25 19:35:46.281502-0400 XXXX WatchKit Extension[1012:18958] [default] lookupMainFuncAddressInMachHeader:71: Invalid Swift entry point data 2020-09-25 19:35:46.282071-0400 XXXX WatchKit Extension[1012:18958] [default] lookupMainFuncAddressInMachHeader:77: Swift entry point addres could not be determined. And when the program then tries to access the WatchKit ExtensionDelegate I get nil
Post not yet marked as solved
5 Replies
0 Views
I read thru the alternative thread... and seems that the problem is different but similar to mine.