Thanks very much for the speedy replies, guys. As you can probably tell, I'm really a Windows person, but my app is cross-platform. JWWalker, I mentioned signage because this video - Packages for macOS: Packaging and Re-packing apps https://www.youtube.com/watch?v=EyXG2JHq9ds seemed to suggest that signing and notarizing are two separate processes (?). To address eskimo's query: at present, I'm targetting Windows and macOS. I hope to get support on Kickstarter to extend the app to iOS. Thanks again. Regards, Lar

Thanks for the clarifications. Regards, Lar

Thanks for the tips. I'll try to post my query again and revert.

ForumPost.txt

Unable to determine what was prompting my AI censorship, and tiring of this tedious version of Marco Polo, I posted my query as a txt file and jpg. Has it slipped through?

Thanks for the speedy reply, Quinn. It seems to have done the trick. I'm puzzled, though. No agreements were flagged on my profile as requiring my agreement, and I don't recall pressing any 'accept' buttons. I did open an agreement in search of such a button, but didn't find one. Not that it matters now, but is this all I need to do in future to 'agree' a document?

Quinn, Thank you very much for the prompt and detailed reply. Do you happen to know if the problem might be caused by a plugin that is no longer being used but may still be referenced within my app? I ask because the only difference between the first version of my app (that sailed through to the launch file stage) and the one that fell at the first hurdle is that I added a plugin to the latter; then removed it. I tried removing all plugins from my runtime, and signing it again, but it made no difference. Thanks again.

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?

Etresoft, thanks for taking the time to reply further. You're right about the deprecation of the runtime, of course. Filemaker had been threatening to do as much for a decade. Many developers believed it would never happen, but the company went ahead with the canning just after I completed the first version of my app. So, I shelved it—for public consumption, at least. I continued to use it for my own ends. It runs on the latest versions of Windows and Mac. I use it almost every day. Later, noting that no one else had produced a similar desktop app in the interim period, I wondered whether I might offer it for little to no cost as a springboard for development in another programming language. If enough people bought into the premise, I hoped I might elicit interest in the proposal via a crowd-sourcing platform. So, I returned to it; adding a ‘silent’ data saving script that ensured that, should the app fail under a new OS, the raw data written to the last version would be stored on each user’s harddisk. I’m still not sure exactly what the deprecation means regarding continued use. None of the features added to FM after 18 would appear in the runtime, but that wasn’t an issue, per se. And I still have ‘canary’ runtimes built in Filemaker 5, 6 and 7 that run today. Of course, there’s no guarantee that what has been will continue to be...