Post not yet marked as solved
10k
Views
I keep getting this error despite having installed new certificates. I have 3rd Party Mac Developer Application, AddTrust External CA Root, Apple Application Inegration Certification Authority, Developer ID Application, Apple Worldwide Developer Relations Certification Authority, Developer ID Application, Developer ID Certification Authority, Developer ID Installer and some others. Why does it give me this error?
Post not yet marked as solved
29
Views
The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10826 "kLSNoLaunchPermissionErr: User doesn't have permission to launch the app (managed networks)" UserInfo={_LSFunction=_LSLaunchWithRunningboard, _LSLine=2539, NSUnderlyingError=0x7f7f76b11c10 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x7f7f76b124d0 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 111}}}}}**
Post not yet marked as solved
532
Views
Whenever I'm trying to open Eclipse or SpringToolSuite 4 I'm getting the same permission related issues It was working fine a day before yesterday but now It's showing weird stuff.
You do not have permission to open the application “SpringToolSuite4”.
You do not have permission to open the application “Eclipse”.
If anyone has any solutions please share
Post not yet marked as solved
70
Views
Hello, I'm keeping on getting a failure when trying to install an App from Samsung Dex. The report says to "disconnect your phone to install" but NO phone is connected. I tried various command line and numerous troubleshooting to reset and refresh some KEXT but still issue exists.
Here is the install.log below. What could be the work around this bug? How to reset and proceed with installation?
Thank you
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px 'Helvetica Neue'; color: #262626; -webkit-text-stroke: #262626; background-color: #ffffff}
span.s1 {font-kerning: none}
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: @(#)PROGRAM:Install PROJECT:Install-1000
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: @(#)PROGRAM:Installer PROJECT:Installer-1020
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Hardware: iMac18,2 @ 3.00 GHz (x 4), 32768 MB RAM
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Running OS Build: macOS 11.4 (20F71)
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: USER=KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: __CFBundleIdentifier=com.apple.installer
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: COMMAND_MODE=unix2003
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: LOGNAME=KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.LsIZhGSQv0/Listeners
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: SHELL=/bin/zsh
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: HOME=/Users/KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: TMPDIR=/var/folders/d_/hqzchb455m9ct55v66n3n2_w0000gn/T/
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: XPC_SERVICE_NAME=application.com.apple.installer.1152921500312163432.1152921500312163437
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: XPC_FLAGS=0x0
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Samsung DeX Installation Log
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Opened from: /Volumes/Samsung DeX/Install Samsung DeX.pkg
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Failed to load specified background image
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Product archive /Volumes/Samsung DeX/Install Samsung DeX.pkg trustLevel=350
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: External component packages (2) trustLevel=350
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Could not load resource readme: (null)
2021-07-08 19:33:16-04 KPs-iMac Installer[9137]: Installation checks failed.
2021-07-08 19:33:16-04 KPs-iMac Installer[9137]: Installation check failure. . Disconnect your phone to install..
Post not yet marked as solved
70
Views
Hello,
I'm keeping on getting a failure when trying to install an App from Samsung Dex. The report says to "disconnect your phone to install" but NO phone is connected. I tried various command line and numerous troubleshooting to reset and refresh some KEXT but still issue exists.
Here is the install.log below.
What could be the work around this bug?
How to reset and proceed with installation?
Thank you
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px 'Helvetica Neue'; color: #262626; -webkit-text-stroke: #262626; background-color: #ffffff}
span.s1 {font-kerning: none}
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: @(#)PROGRAM:Install PROJECT:Install-1000
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: @(#)PROGRAM:Installer PROJECT:Installer-1020
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Hardware: iMac18,2 @ 3.00 GHz (x 4), 32768 MB RAM
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Running OS Build: macOS 11.4 (20F71)
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: USER=KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: __CFBundleIdentifier=com.apple.installer
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: COMMAND_MODE=unix2003
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: LOGNAME=KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.LsIZhGSQv0/Listeners
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: SHELL=/bin/zsh
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: HOME=/Users/KP
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: TMPDIR=/var/folders/d_/hqzchb455m9ct55v66n3n2_w0000gn/T/
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: XPC_SERVICE_NAME=application.com.apple.installer.1152921500312163432.1152921500312163437
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Env: XPC_FLAGS=0x0
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Samsung DeX Installation Log
2021-07-08 19:33:08-04 KPs-iMac Installer[9137]: Opened from: /Volumes/Samsung DeX/Install Samsung DeX.pkg
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Package Authoring Error: has an unsupported MIME type: X-NSObject/NSNumber
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Failed to load specified background image
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Product archive /Volumes/Samsung DeX/Install Samsung DeX.pkg trustLevel=350
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: External component packages (2) trustLevel=350
2021-07-08 19:33:09-04 KPs-iMac Installer[9137]: Could not load resource readme: (null)
2021-07-08 19:33:16-04 KPs-iMac Installer[9137]: Installation checks failed.
2021-07-08 19:33:16-04 KPs-iMac Installer[9137]: Installation check failure. . Disconnect your phone to install..
Post not yet marked as solved
651
Views
This is a solved problem, but a detail not in any docs I could find and I could only get answered from support. Figured I'd add it to the index.App-specific passwords are not supported with Managed Apple ID created through Business Manager. You will simply not see the option to create an app-specific password even if you do have two-factor authentication turned on.
Post marked as solved
165
Views
Hello again. We have a sandboxed app in macOS App Store.
It has to load dylib files using dlopen(). The dylib files are signed by our vendor. When the app tries to load them, we see this error similar to "mapping process and mapped file have different Team IDs".
We tried adding disable-library-validation but when we do so, the app refuses even to start.
Is there a way to achieve loading of dylibs signed by another team?
Also, this issue happens with only a few users. I don't see this issue on my development machines.
Post marked as solved
150
Views
Hi, currently I have a macOS app that contains an executable I compiled of openvpn, when I try to notarize the macOS application that contains openvpn I get the following error message.
Currently I compile openvpn like this for x86_64 (Intel):
https://gist.github.com/lecksfrawen/fab1a1690ab7b80b4acac617cb5be403
Is there a way to add to autoconf (make && make install) something similar to cmake's XCODE_ATTRIBUTE_ENABLE_HARDENED_RUNTIME to allow the project to be compiled with the hardened runtime?
Or should I use Hardened Runtime exception in Signing & Capabilities in my main app?
Thanks.
Post not yet marked as solved
324
Views
HiNotarisation of audio plugin bundles in the AAX format (Pro Tools compatible) is causing a problem. The AAX formatted plugins define a non-standard CFBundlePackageType value of "TDMw" in their Info.plist and that appears to prevent them from being recognised by the notarisation process. If this is artificially changed to "BNDL" as in other plug-in formats notarisation and stapling is successful.Although some level of success is observed when attempting to notarise, it is only the Pace components in the bundle that notarise correctly (all AAX plug-ins must be signed by a third party tool from Pace). The actual plug-in fails to notarise unless the package type is changed, so when looking to staple this fails as not everything in the bundle got through the process.Is it possible to address this on the notary servers please? It is important to the audio community that we are able to notarise AAX plug-ins and the pkg files that may contain them (this obviously causes the entire pkg installer to fail to staple as well).I can provide further details and log files if necessary.Thank youMatt
Post marked as solved
166
Views
Hello,
I have a sandboxed app distributed through macOS AppStore. It downloads some 'dylib' files from a server(internet) and later loads using dlopen(). But the downloaded files have quarantine flag set and thus Gatekeeper shows a warning when the app loads them.
Added LSFileQuarantineEnabled in info.plist and set to false but it didn't help.
Tried to run a shell command "xattr -d filename" from the app itself but that doesn't work too due to "operation not permitted" error.
Tried [file1 setResourceValue:nil forKey:NSURLQuarantinePropertiesKey error:nil] but even this doesn't make any difference. Although the return value of the call is "YES", the quarantine flag is still there. Note : when i run this method from a non-sandboxed app, it works.
Now I don't have any more options. Is there any way a sandboxed app can download a file and remove the quarantine attribute?
Post not yet marked as solved
2.1k
Views
For Mac OS X application getting error while validating app while using 3rd party App Developer Certificate for signing : App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: It is referring about the executable build in MacOS folder with same name as your application's product name.Tried Clearing Dervied Data etc, All certificate delete & install (including Apple's certificates), different versions of Xcode (8.3.3. & 9.2) but nothing worked. Any help would be more appreciated.
Post not yet marked as solved
983
Views
Hello!I'm trying to submit a Java app to the Apple Mac Store, so I have to do this manually. I could fix 23 of 25 issues but I stuck on the last 2 😉ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-identifier]. Please re-build your archive with an up-to-date version of Xcode, and submit again."ERROR ITMS-90230: "Invalid product archive metadata. Error in keyPath [product-metadata.product-version]. Please re-build your archive with an up-to-date version of Xcode, and submit again."For both of them I couldn't find anything useful in the net. What does ist mean and how to fix it???The result is the same in the Transporter app and when uploading manually in the terminal.Thanks in advance for any hint!Thomas
Post not yet marked as solved
179
Views
Hello,
My .pkg is certify, indeed I have notarize with an Developer ID Installer but when I download my .pkg on my website I have this message :
cannot open because apple cannot verify it for malware
Can you help me because I don't understand why I have this error then my .pkg is signed.
Post not yet marked as solved
1.4k
Views
When opening a pkg file on Mojave and Catalina I'm seeing following Package Authoring Errors in Installer log (/var/log/install.log):Package Authoring Error: <background> has an unsupported MIME type: image/data
Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
Package Authoring Error: <layout-direction> has an unsupported MIME type: X-NSObject/NSNumberwhich is weird because background is defined in pkg Distribution XML as:<background file="background.tiff" alignment="bottomleft" scaling="none" mime-type="image/tiff"/>based on specification of Distribution file in https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.htmlSimilar problems can be seen even on pkg installers that contain no background XML element. That also includes pkg files downloaded from Apple website.Is there any explanation where these errors are coming from?
Post marked as solved
161
Views
Hello,
Our Production packages and executables were signed with a Developer ID installer and application certificates, that have expired yesterday. These packages were notarised but not stapled.
After the certificate is expired, will the users be able to download and install the packages that were signed those certificates.
(In our quick test we are able to download and install these packages but will they continue to work )
