I have an app that I would like to test on Mac Sequoia. But when I build in Xcode Cloud, it seems to fail with a This bundle is invalid. Apple is not currently accepting applications built with this version of the OS. It also complains about the release train being closed, but I created a new release (set to manually be released). And it is pulling an old CFBundleShortVersionString somehow, but the other app versions (iOS and VisIonOS) in the same Xcode Cloud build work fine.
Michaelrowe01
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
NC, USA
Post
Replies
Boosts
Views
Activity
I am working thru the issues of turning on Strict Concurrency Checking. I have a SwiftData application, and I am compressing images before saving them as data. My save function is pretty simple
private func save() {
ImageCompressor.compress(image: (frontImageSelected?.asUIImage())!, maxByte: 1_048_576) { image in
guard image != nil else {
print("Error compressing image")
return
}
if let greetingCard {
greetingCard.cardName = cardName
greetingCard.cardFront = image?.pngData()
greetingCard.cardManufacturer = cardManufacturer
greetingCard.cardURL = cardURL
greetingCard.eventType = eventType
} else {
let newGreetingCard = GreetingCard(cardName: cardName, cardFront: image?.pngData(), eventType: eventType, cardManufacturer: cardManufacturer, cardURL: cardURL)
modelContext.insert(newGreetingCard)
}
}
}
I compress the selected image, I had to change my ImageCompressor.compress closure to Sendable, but now every assignment above is flagging with the above warning. I define the greetingCard as var greetingCard: GreetingCard? in my view, since I can have it passed in for edit, or generated if new.
I also get the same warning on modelContext, which is defined as @Environment(\.modelContext) private var modelContext.
It's not clear to me how to address this warning. Any pointers would be helpful.
I've been really happy with Xcode Cloud, but as a single developer with a very simple app, I cannot justify the upcoming paid service. I have two apps with minimal amount of work going on for the one that I used to test Xcode Cloud.
Two questions:
What do I need to do with my Xcode project to successfully disable Xcode cloud?
What is the correct approach to disable the upcoming billing for Xcode cloud?
Thanks for any pointers.
I've been trying to use the example from this session to tweak the default SwiftData template, allowing for syncing of the data across devices. When I added the following code, I get the above error:
@main
struct ItemApp: App {
let items = ModelConfiguration(schema: Schema([Item.self]), url: URL(filePath: "/path/to/item.store"), cloudKitContainerIdentifier: "iCloud.com.app.Item")
let container = try ModelContainer(for: items). // ERROR HERE
var body: some Scene {
WindowGroup {
ContentView()
}
.modelContainer(container)
}
}
Cannot use instance member 'items' within property initializer; property initializers run before 'self' is available
Any pointers would be helpful.
I noticed that this year the Developer App is not allowing me to run the videos in full screen mode. I have confirmed this on a 2019 16inch MBP and 2021 11 Inch iPad Pro. Is anyone else seeing this issue?
In the last few days my Xcode cloud builds are failing with error 65. After downloading the logs and digging thru them, I am seeing the following error -
line 6: $(CURRENT_PROJECT_VERSION) + 1: syntax error: operand expected (error token is "$(CURRENT_PROJECT_VERSION) + 1")
This started after I did a check in of my code via the GIT Desktop app instead of Xcode. Since then I have deleted my workflow, recreated it, and reset my release # to try and clear this message, but every build fails with the exact same error.
I have raised a feedback, but I am currently stuck to building and distributing my app to my TestFlight users. (I don't want to go back to the manual method, I am really enjoying Xcode cloud).
Any suggestions on how to resolve this?
I just updated my project for localization, when I enabled this for SiriIntents, my signings & capabilities settings for the SiriExtension stopped seeing the info.plist. -
..."/SiriExtension/SiriExtension.entitlements" could not be opened.
Verify the value of the CODE_SIGN_ENTITLEMENTS build setting for target "SiriExtension" is correct and that the file exists on disk.
I am running Xcode Version 13.1 (13A1030d), which has created a Info.plist which lists all the localizations I have done, and in each directory below it contains a SiriExtension.engitlemetns file.
How should I setup the SiriExtension.entitlements correctly?
So I am banging my head, I realized my stand along Watch App had a STUPID long name of "App Name - WatchKit App" so I went into my Target and changed the Display Name to "App Name" removing WatchKit App. Well now my app won't validate when uploading to the Appstore. I get the message - Invalid Info.plist key. The key
WKExtensionDelegateClassName in bundle App Name.app/Watch/App Name WatchKit App.app is invalid.
My Info.plist has the value of
<key>WKExtensionDelegateClassName</key>
<string>$(PRODUCT_MODULE_NAME).ExtensionDelegate</string>
I have confirmed that I have @WKExtensionDelegateAdaptor(ExtensionDelegate.self) var delegate in my @main for the SwiftUI App. And when I print a few values in my app launch I get the following confirmations:
Super Init - ExtensionDelegate
Contentview
applicationDidFinishLaunching for watchOS
Super Init - ExtensionDelegate
Optional(My_App_Extension.Setup)
Optional(My_App_Extension.Statistics)
Optional(My_App_Extension.Other)
applicationDidBecomeActive for watchOS
update complication
I create three classes at launch and print this in the log with print(ExtensionDelegate.shared.Setup as Any) , etc. The other lines are just confirming where I am at app startup.
This is a WatchOS8 application and I am running Xcode version Version 13.1 (13A1030d).
I made a minor change the UI of my tvOS App, and am now getting errors related to the App Icon. I have confirmed that all the background images DO match the requirements but App Store Connect won't let me upload:
App Store Connect Operation Error
Invalid Image Asset. The image stack 'App Icon' in 'Payload/My TV.app/Assets.car' has a background layer image that does not match the canvas dimensions '400x240'.
App Store Connect Operation Error
Invalid Image Asset. The image stack 'App Icon' in 'Payload/My TV.app/Assets.car' has a background layer image that does not match the canvas dimensions '800x480'.
App Store Connect Operation Error
Invalid Image Asset. The image stack 'App Icon' in 'Payload/My TV.app/Assets.car' has a background layer image that does not match the canvas dimensions '1280x768'.
App Store Connect Operation Error
Invalid Image Asset. The image stack 'App Icon' in 'Payload/My TV.app/Assets.car' has a background layer image that does not match the canvas dimensions '2560x1536'.
App Store Connect Operation Error
Invalid Image Asset. The App Store Icon must only contain an image with size (1280pt × 768pt @1x). Refer to https://developer.apple.com/tvos/human-interface-guidelines/icons-and-images/app-icon for more information
Have the standards changed? Or is there another issue I should be looking at? Thanks!
I have an App I've been working on with CloudKit to sync data between App on iOS, iPadOS and macOS. I have updated my iPhone and iPad to latest betas. On the iPad I had to wipe and rebuild from scratch. As of now, the iPhone is working fine and changes are showing up on my Mac, but the iPad is not pulling down the data that is in CloudKit. Is there some security or beta testing change that is causing this? They are all logged into the same iCloud account.
I have recently installed a new UPS which as a service to automatically shut down my Mac when certain events happen. It required that I install java. It required I install a new version of java from the Oracle site - here's my version info
java 15.0.1 2020-10-20
Java(TM) SE Runtime Environment (build 15.0.1+9-18)
Java HotSpot(TM) 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)
now when ever I try to upload via Organizer in Xcode I get the following message:
Could not find or load main class 1.Library.Java.Extensions:.Library.Java.Extensions:.Network.Library.Java.Extensions:.System.Library.Java.Extensions:.usr.lib.java:.
Has anyone else seen this? Other than removing the UPS software any ideas how to fix?
Working working with a SwiftUI Architecture WatchOS app, if you want to use ExtensionDelegate you need to create your own. I have done this, but when I try to actually access the delegate in the code, I am getting the following error message Could not cast value of type SwiftUI.ExtensionDelegate' (0x7fff8441b480) to 'TestMe_WatchKit_Extension.ExtensionDelegate' (0x10c3b36d0).
I have defined the ExtensionDelegate as -
class ExtensionDelegate: NSObject, WKExtensionDelegate {
		var meetingStatistics:	MeetingStatistics = MeetingStatistics()
}
in my @main - I have the following:
@main
struct WatchApp: App {
@WKExtensionDelegateAdaptor(ExtensionDelegate.self) var delegate
// code
}
When I try to access the delegate within another class, not via @EnvironmentObject, but via - let delegate = WKExtension.shared().delegate as! ExtensionDelegate I get the above error.
I know with macOS 11 and iOS 14, iOS apps will run on Apple Silicon. I have a Catalyst version of my app, that I would like to add to the same AppStore Connect entry. I know I have to remove my Mac App Store entry, but I can't figure out how to change the App bundle name in the App Store Connect for the the Catalyst app.
Do I have to build a native Mac Version with the same bundle ID as the iOS version to have it on the same App Connect entry?
My app is free and I want people who have it on iOS to have access on macOS.
I have the following HStack in my appleTV app, but the remote will not go to the Button on the right side of the stack.
HStack{
if( self.meeting.meetingEndedState == false){
		Button(action:{
					 _ = self.meeting.addAttendee()
} ) {
				Image(systemName: "plus.circle.fill")
.font(Font.system(size: 42, design: .rounded))
}
				.mask(Circle())
.padding()
Text("\(self.meeting.numberOfAttendees)")
.padding()
Button(action:{
	_ = self.meeting.removeAttendee() })
				{
	 Image(systemName: "minus.circle.fill")
.font(Font.system(size: 42, design: .rounded))
}
.mask(Circle())
.padding()
} else {
		Button(action: {
	 self.meeting.meetingReset()
self.meeting.numberOfAttendees=1
}, label: {
	 Text("Reset")
	 }).buttonStyle(MyButtonStyle(color: .blue))
}
}
.padding()
What I am doing wrong?
I am seeing this with Xcode 12.0 (all betas)
Process:							 Xcode [1211]
Path:									/Applications/Xcode-beta.app/Contents/MacOS/Xcode
Identifier:						com.apple.dt.Xcode
Version:							 12.0 (17210.1)
Build Info:						IDEFrameworks-17210001000000000~14 (12A8189n)
Code Type:						 X86-64 (Native)
Parent Process:				??? [1]
Responsible:					 Xcode [1211]
User ID:							 501
Date/Time:						 2020-09-08 16:06:15.967 -0400
OS Version:						Mac OS X 10.16 (20A5364e)
Report Version:				12
Bridge OS Version:		 5.0 (18P50370a)
Anonymous UUID:				627D7A1F-DDFC-8DCE-8ACF-0ECBAB9020EA
Time Awake Since Boot: 460 seconds
System Integrity Protection: enabled
Crashed Thread:				0	Dispatch queue: com.apple.main-thread
Exception Type:				EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:			 0x0000000000000001, 0x0000000000000000
Exception Note:				EXC_CORPSE_NOTIFY
Termination Signal:		Illegal instruction: 4
Termination Reason:		Namespace SIGNAL, Code 0x4
Terminating Process:	 exc handler [1211]
Application Specific Information:
ProductBuildVersion: 12A8189n
Crashing on exception: The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window.
<DVTDevicesWindow: 0x7fbaa5739c30> 0x160 (352) {{181, 204}, {1040, 700}} Devices en
Application Specific Backtrace 1:
0	 CoreFoundation											0x00007fff2433b0df __exceptionPreprocess + 242
1	 DVTFoundation											 0x000000010a36eba5 DVTFailureHintExceptionPreprocessor + 424
2	 libobjc.A.dylib										 0x00007fff2419d469 objc_exception_throw + 48
3	 CoreFoundation											0x00007fff2433af43 +[NSException raise:format:] + 189
4	 AppKit															0x00007fff26d11119 -[NSWindow(NSDisplayCycle) _postWindowNeedsUpdateConstraintsUnlessPostingDisabled] + 1721
5	 AppKit															0x00007fff26cf616d -[NSView
......
Any suggestions on how to get beyond this.