Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
10.14.2.0
-
None
-
MacOS 12.4. M1(2020)
-
Normal
-
Embedded/Client difference
Description
First - just thank you - !
The issue I'm reporting pertains to the Derby embedded database within an Eclipse RCP.3/Hibernate/Spring/Derby application in an OS X environment. Signing and notarizing the application without the entitlement "com.apple.security.app-sandbox"<true> allows the app to download and run as expected. It may be downloaded at https://www.corgroup.com/free/freeSignup.html. When functioning as designed an embedded Derby database is created the first time the application is launched. A welcome screen is then displayed and the user is able to complete the setup.
The problem occurs when the entitlement "com.apple.security.app-sandbox"<true> is added during the app signing process. With the sandbox enttitlement set to true the database is not created. Apparently with the sandbox entitlement I am unable lauch the app through the terminal so no useable error is available. Without the sandbox entitlement the application may not be deployed to Apples App Store.
Any guidance will be greatly appreciated.
List of all entitlements:
<key>com.apple.security.app-sandbox</key>
<true/>
<key>com.apple.security.assets.pictures.read-only</key>
<true/>
<key>com.apple.security.cs.allow-dyld-environment-variables</key>
<true/>
<key>com.apple.security.cs.allow-jit</key>
<true/>
<key>com.apple.security.cs.disable-library-validation</key>
<true/>
<key>com.apple.security.files.downloads.read-write</key>
<true/>
<key>com.apple.security.files.user-selected.read-write</key>
<true/>
<key>com.apple.security.network.client</key>
<true/>
<key>com.apple.security.print</key>
<true/>
<key>com.apple.security.cs.allow-unsigned-executable-memory</key>
<true/>
<key>com.apple.security.cs.disable-executable-page-protection</key>
<false/>
<key>com.apple.security.cs.debugger</key>
<false/>
Be well
Ralph Bosson