Post

Replies

Boosts

Views

Activity

Comment on Apple doc still refers to nonexistent info.plist. Should we use the entitlements file instead?
Thanks. That screen shot is odd, because it shows "Build Settings" selected, not Info. I don't have anything like those entries in my build settings. On the Info page... that is some absymal UI. I mean... not only are the + controls invisible unless you happen to roll over them, but they are depicted as only applying to one setting... not as if they add entirely new entries to the overall list. Unbelievable. Thanks! I did add the options I'll need. But the simulator doesn't prompt for them...
Topic: Code Signing SubTopic: Entitlements Tags:
Jan ’24
Comment on Conforming @MainActor class to Codable
That doesn't work for me. Adding async to those does make the errors on those functions go away, but the compiler still complains Type 'User' does not conform to protocol 'Decodable' Type 'User' does not conform to protocol 'Encodable' with no further information.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jan ’24
Comment on Apple doc still refers to nonexistent info.plist. Should we use the entitlements file instead?
Thanks. That screen shot is odd, because it shows "Build Settings" selected, not Info. I don't have anything like those entries in my build settings. On the Info page... that is some absymal UI. I mean... not only are the + controls invisible unless you happen to roll over them, but they are depicted as only applying to one setting... not as if they add entirely new entries to the overall list. Unbelievable. Thanks! I did add the options I'll need. But the simulator doesn't prompt for them...
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Jan ’24