I had the same issue in Xcode 14. I'm on the 14.1 beta at the moment and it doesn't seem to happen, but 14.0.1 has been released. See if it's fixed in that? If not, please raise a bug.

Does this help? https://stackoverflow.com/questions/26900302/swift-storing-states-in-coredata-with-enums

These are the Developer Forums. Your question is best asked at the Support Forums.

These are the Developer Forums. Your question is best asked at the Support Forums. You'll get more people responding.

So you already have a paid-for app available that comes with a Watch app? Well, then your question is moot, isn't it? Your combination of iOS app and watchOS app seems fine as it is. From what I can see you use the Watch app to track your runs, and the iOS app merely holds them there for you? So yes, the iOS app compliments the Watch app. Nothing says the iOS app has to be the main player in an iOS/watchOS app combination.

Are you using Flutter? Someone else had this problem here.

This is my code, and it works fine: @main struct WidgetEntry: Widget { public var body: some WidgetConfiguration { IntentConfiguration(kind: kWidgetKind, intent: DynamicEventSelectionIntent.self, provider: Provider() ) { entry in WidgetEntryView(entry: entry) } .configurationDisplayName(NSLocalizedString("AddingWidget_Title", comment: "Adding the Widget")) .description(NSLocalizedString("AddingWidget_Description", comment: "Adding the Widget")) .supportedFamilies([.accessoryCircular, .accessoryInline, .accessoryRectangular, .systemSmall, .systemMedium]) } } struct WidgetEntryView: View { var entry: Provider.Entry @Environment(\.widgetFamily) var family @ViewBuilder var body: some View { switch family { case .accessoryCircular, .accessoryInline, .accessoryRectangular: LockScreenWidgetView(event: entry.event) case .systemSmall: SmallWidgetView(event: entry.event) case .systemMedium, .systemLarge, .systemExtraLarge: MediumWidgetView(event: entry.event) @unknown default: MediumWidgetView(event: entry.event) } } } }

Get in touch with the App Store people directly through your account. You'll likely not get any direct help on the forums.

Is there any indication of where in your code the compile failed? We're going to need a lot more info that one sentence if you want help.

This is a problem better suited to the Support Forums.

Personally Identifiable information (PII) really shouldn't be shared with a third party unless you explicitly ask the user's permission, which is different from App Tracking Transparency. ATT stops your app from accessing the phone's unique identifier so advertisers can't track you as a specific individual user. If the user says no to sharing their PII, will you respect that? Will your app continue to function correctly if you don't share their PII with your partner company? Your app details that show in the App Store definitely have to tell users you're going to share their details. I have to say, unless it's something that specifically needs my PII like an app that books a hire car, I wouldn't go anywhere near such an app.

That's a bit extreme. Get in touch with the store where you bought the computer and see if they can do anything. If it was from an Apple Store they'll probably be very helpful in trying to fix your problem despite it being a week out of warranty. These things happen. Don't burn your house down just because there's a leak in the pipework.

That looks like a bug in the beta. I'm not getting it at all. Raise a bug.

Doesn't your struct Dummy have to define what it is? For example: @main struct Dummy : App { I have no idea, just a guess from looking at my own code.

I don't think this is possible for non-Apple complications. It's not in the public APIs. I thought about rotating the text a number of degrees, but you can't tell which corner of the Watch face your complication is on, so it would only ever be correct in one of four places ¯\ _ (ツ) _ /¯