I've been trying to send an archive with Organizer to iTunes Connect. It's not my first time. I've been doing it for more than a decade. Anyway, when I try to send a package for my new macOS application, Organizer gives me two error messages that I have never seen before.
App Record Creation Error
App Record Creation failed due to an invalid attribute. The SKU you entered has already been used.
App Record Creation Error
App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect.
An odd thing is that, as shown in the screenshot below, Organizer demands that I enter an application name and SKU manually. I've entered the exactly same ones from the App Store Connect page. I didn't see this step on Organizer last month.
I'm using a new SKU for this submission. And I don't have an existing application at iTunes Connect with the same application name.
I guess it's the same issue that has been reported here.. I have no pending contract issues.
How do I send an archive without errors? My Xcode version is Version 16.4 (16F6).
Thanks.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I've been waiting since I had Organizer sent my latest IPA to iTunes Connect servers 40 minutes ago. But the App Store Connect site doesn't show it. Is anyone having the same issue? I hate it when it happens because you don't know how long you have to wait.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
I have three toolbar buttons with images from Assets.xcassets. Initially, I didn't use @1x, @2x, @3x sizes. I just put one size (72 x 72) for all of them. It was never a problem till a few days ago.
The reviewer has reported numerous issues, which all seem to originate from miniaturized toolbar images. They have given me a screenshot from an iPad. Now, each of the three to the left has shrunken to 4 x 4, according to them.
Some lines of code are the following.
import SwiftUI
struct ContentView: View {
var body: some View {
NavigationStack {
ZStack {
VStack {
...
...
...
}
.background(.brown)
.navigationBarTitleDisplayMode(.inline)
.navigationBarItems(
leading: HStack(content: {
Button {
} label: {
Image("ToolbarImage1")
.resizable()
.foregroundColor(.red)
.aspectRatio(contentMode: .fit)
.frame(width: 28)
}
Button {
} label: {
Image("ToolbarImage2")
.resizable()
.foregroundColor(.cyan)
.aspectRatio(contentMode: .fit)
.frame(width: 28)
}
Button {
} label: {
Image("ToolbarImage3")
.resizable()
.foregroundColor(.gray)
.aspectRatio(contentMode: .fit)
.frame(width: 28)
}
}),
trailing: HStack(content: {
Button {
} label: {
Text("X")
.font(.body)
.fontWeight(.semibold)
.foregroundStyle(colorScheme == .light ? .white : .black)
.frame(width: 28, height: 28)
.background {
Circle()
.fill(!disableGroupMenu ? .green : .green.opacity(0.6))
}
}
Button {
withAnimation(.easeInOut(duration: 0.2)) {
showCopyMenu.toggle()
manageMenu()
}
} label: {
Text("Y")
.font(.body)
.fontWeight(.semibold)
.foregroundStyle(colorScheme == .light ? .white : .black)
.frame(width: 28, height: 28)
.background {
Circle()
.fill(!disableCopyMenu ? .indigo: .indigo.opacity(0.6))
}
}
})
)
.toolbar {
ToolbarItem(placement: .principal) {
Text("App name")
.bold()
.foregroundColor(.white)
}
}
}
}
}
}
I don't see this minituralization issue on any of my actual devices (iPhone XR, iPhone 14, iPad 9th gen.) on top of various simulator models including iPad A16 with iOS 26. This is my first iOS submission after iOS 26 was released. I don't know if it has something to do with iOS 26. The reviewer hasn't told me about their iPad model or the iOS version. I have the same app for macOS, which was submitted after macOS 26 was released. And they haven't reported the miniaturization issue after 4 or 5 software updates.
If you have any idea as to what's causing it, please let me know. I have submitted a new binary with @3x as a resort. I doubt the issue has been resolved. Thanks.
Initally, I've used Xcode 16.4 to built the app. I have tried building it with Xcode 26. And I don't see the minituralization issue on any of the simulator models (iPad mini, iPad A16...).
Topic:
UI Frameworks
SubTopic:
SwiftUI
I have a SwiftUI app. It fetches records through CoreData. And I want to show some records on a widget. I understand that I need to use AppGroup to share data between an app and its associated widget.
import Foundation
import CoreData
import CloudKit
class DataManager {
static let instance = DataManager()
let container: NSPersistentContainer
let context: NSManagedObjectContext
init() {
container = NSPersistentCloudKitContainer(name: "DataMama")
container.persistentStoreDescriptions = [NSPersistentStoreDescription(url: FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: group identifier)!.appendingPathComponent("Trash.sqlite"))]
container.loadPersistentStores(completionHandler: { (description, error) in
if let error = error as NSError? {
print("Unresolved error \(error), \(error.userInfo)")
}
})
context = container.viewContext
context.automaticallyMergesChangesFromParent = true
context.mergePolicy = NSMergePolicy(merge: .mergeByPropertyObjectTrumpMergePolicyType)
}
func save() {
do {
try container.viewContext.save()
print("Saved successfully")
} catch {
print("Error in saving data: \(error.localizedDescription)")
}
}
}
// ViewModel //
import Foundation
import CoreData
import WidgetKit
class ViewModel: ObservableObject {
let manager = DataManager()
@Published var records: [Little] = []
init() {
fetchRecords()
}
func fetchRecords() {
let request = NSFetchRequest<Little>(entityName: "Little")
do {
records = try manager.context.fetch(request)
records.sort { lhs, rhs in
lhs.trashDate! < rhs.trashDate!
}
} catch {
print("Fetch error for DataManager: \(error.localizedDescription)")
}
WidgetCenter.shared.reloadAllTimelines()
}
}
So I have a view model that fetches data for the app as shown above.
Now, my question is how should my widget get data from CoreData? Should the widget get data from CoreData through DataManager? I have read some questions here and also read some articles around the world. This article ( https://dev.classmethod.jp/articles/widget-coredate-introduction/ ) suggests that you let the Widget struct access CoreData through DataManager. If that's a correct fashion, how should the getTimeline function in the TimelineProvider struct get data? This question also suggests the same. Thank you for your reading my question.