“SwiftData inheritance relationship”

Inno Setup was a sweet app. I used to use that when I made Windows software. I don't know anything about Filemaker. A quick search says that runtimes were deprecated and removed years ago. Apparently Filemaker 18 was the last version to support them. There is some kind of iOS App SDK that may still be supported. It doesn't sound like this would be a quick and/or easy solution, but that seems to be all there is. After Hypercard, there was never the same kind of custom database app community (Clipper, Access, Paradox, etc.) as on PCs. I don't know what you mean by inherited icons. A DMG is just a disk image. Its use in installing software is problematic. Why use a zip files or pkg installer when you can use DMGs that make it 3 times more difficult? Look at the pkgutil tool. All you need is a folder with the app you want to install. Create a directory tree of all the locations where you want to install files. Then use pkgutil to create an installer for that. Forget everything I said about the Mac App St

Etresoft, thanks for the reply. I assure you, I'm not trying to make work for myself or others, merely attempting to package a Filemaker 18 Runtime app. A Windows bod, I had no trouble creating a signed exe using Inno Setup, but have been pulling teeth trying to do the equivalent for the Mac version. I began by reading the official Mac guides, but found them impenetrable, so turned to Copilot and Chatgpt. After many weeks of toing and froing, I have reached the stage where I can script create a DMG, but am currently having trouble with inherited icons. Are you saying that if I had merely uploaded my runtime to the Mac App Store, I might have avoided all of this?

Just a quick update: This fix helps avoid the crash but it does not solve the issue cause by iOS26.1, which automatically changes SwiftData Arrays or Sets attributes from .externalStorage to .transformable. This in consequence blocks the iCloud sync mirroring and results with the full disappearance Customer's data after updating. It is a serious bug that needs to be address by Apple ASAP.

A server-to-server key is for a server script to authenticate with CloudKit and make API calls to a public database with the inherited privileges of the creator of the key. To access a private database with CloudKit web service, consider using an API token, as described here. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hi Chen, I don't believe it has anything to do with Transformables, in my opinion that is some another warning for handling image formats or colors but the image gets through just fine. I've had that warning way long before. I honestly think Apple should hold on the iOS26.2 before they fix this. It's messing millions of SwiftData Apps already published (customers are already pissed). Look at this answer I posted a few hours ago, it might help: https://developer.apple.com/forums/thread/808020

SharedModelContainer.txt Folks who filed their feedback report may have gotten responses from the feedback system. For people who see the same issue but haven't yet filed any feedback report, I'd like to share our investigation here to hopefully help. To give you more context, SwiftData (with DefaultStore) uses Core Data as its underlying storage mechanism. At runtime, SwiftData converts the schema to an in-memory Core Data model (NSManagedObjectModel), and uses the model to load and persist the data store. Before system 26.1, when handling an attribute of an array type, SwiftData converts the array type to Binary Data. On system 26.1, it instead converts the type to Transformable. This change leads to a difference between the in-memory model and the model used in the persisted data store, triggering a migration error with the following message: Error Domain=NSCocoaErrorDomain Code=134140 Persistent store migration failed, missing mapping model.” To work around the issue, you might

Thanks for the post, can you tell me a little bit more about what is under your swift data? Any changes? I'm not an expert in SwiftData at all, hopefully as you post your model other people can help you find why, however when I see that error I will consider a staged migration and I think, you should also consider a staged migration to resolve this type incompatibility: https://developer.apple.com/documentation/coredata/staged-migrations?language=objc Albert Pascual
  Worldwide Developer Relations.

Issue resolved: using the @Relationship macro on both sides instead of one is the issue. After I removed one @Relationship macro from one side, app compiles neatly.