Re: Catalina Entitlements or Permissions (was Possible Catalina problem)

> http://newosxbook.com/ent.jl > > Now, if only I could figure out from the database which ones I need to add. Wow, that is an AWESOME tool! I hate that Apple won't pull a single engineer off a project to write some documentation. A similar solution I use is to make-up for Apple’s confusing de

Re: Catalina Entitlements or Permissions (was Possible Catalina problem)

Arghh! So I am Googling and Googling and hunting around the Apple Developer site to try to find a comprehensive list of macOS entitlements so I can code sign my app with the the entitlements my app needs to not generate errors under Catalina. I want to execute: codesign --verbose --deep --fo

Re: Catalina Entitlements or Permissions (was Possible Catalina problem)

Hi Panos, Thank you very much. The discussion in the bug entry answered  lot of my questions. I have one last thing I hope you or someone can point me two, which is a list of Apple macOS "entitlements" From the bug entry I see: com.apple.security.device.audio-input c

Re: Catalina Entitlements or Permissions (was Possible Catalina problem)

We use App Wrapper 3 to sign and notarize our apps. You can control all of these details from inside the app. It makes it pretty easy. I think you can try the app for free and see if this works for you. https://www.ohanaware.com/appwrapper/ Best regards,

Re: Catalina Entitlements or Permissions (was Possible Catalina problem)

Hello Paul, I guess you can sign the standalone mac app with entitlements, i.e. use a file that will contain all the necessary entitlements, and include it in the params passed to the codesign command. See this report for more details: https://quality.livecode.com/show_bug.cgi?id=22660 Kind rega

Catalina Entitlements or Permissions (was Possible Catalina problem)

We're having some macOS Catalina permissions/entitlements issues We have applications that we deliver for Catalina where the application (LiveCode standalone) is code-signed. It is then packaged in an installers (LiveCode standalone) and the installer is code signed. That is then placed in a D

Re: Possible Catalina problem...

Well, goofy as it may seem . . . MacOS 10.15.5 / LiveCode 9.6.0 Community I made a stack containing 1 butoon and NO code and called it "example 1" and ran off a Mac standalone. The I renamed the stack "example 2" and did exactly the same thing. Both of the resultant standalones lauched witho

Re: Possible Catalina problem...

On 6/8/20 7:55 AM, Paul Dupuis via use-livecode wrote: Our hope is that this is a problem SPECIFIC to our single Catalina mac and not a LC Engine or tsNet Catalina specific bug of some sort. To know that some one else has run multiple LC 9 standalones at the same time on Catalina and seen no e

Re: Possible Catalina problem...

Torsten, Thank you. That is encouraging. I may take you up on your offer later to run a test on your Catalina Mac. -- Paul On 6/8/2020 11:10 AM, Torsten Holmer via use-livecode wrote: Hi Paul, I have started three LiveCode standalones on Catalina with no problems. But they are just standal

Re: Possible Catalina problem...

Hi Paul, I have started three LiveCode standalones on Catalina with no problems. But they are just standalones created frome the IDE with no signing etc. If you like, I can test your apps on my MacBook with Catalina in order to check if the problems are replicable. CU, Torsten > Am 08.06.202

Possible Catalina problem...

We have run into a possible problem. Researchware makes two applications, HyperRESEARCH and HyperTRANSCRIBE. We have new forthcoming versions of both built on LiveCode 9.5.1. These two applications are code signed and the DMG is code signed, notarized, and stapled for Catalina. They both work