User Profile

We have run into a security scoping issue with the newer macOS releases (specifically macOS 11.6.x and macOS 12). First and foremost, all of our code is signed and notarized. Our software is made of multiple parts and its mainly a plug-in for Adobe's software products (so its distributed outside of the app store). When you install our software, during the installation process a helper app is also installed in addition to the plug-in for Adobe's software. When the plug-in is invoked from the Adobe application the plug-in then launches an external helper that is installed in the Library/Application Support folder. The external helper app performs the brunt of the computation. We use openApplicationAtURL to launch the faceless background helper app but with newer macOS releases sometimes it gets terminated after launching immediately. The user needs to double click it once from what we have observed. We suspect this is due to a macOS security scope (thats the only conclusion we can come up with). This behavior never used to exist before (macOS 10.15 or earlier). This doesnt occur with all users but a handful of people and on newer macOS releases. We are wondering what can be done to solve this or what are we doing wrong? Do we need to file a bug report?

We are loading image(s) from file(s) using initWithContentsOfFile. While the image(s) load properly we noticed that the memory our app is consuming is increasing even after calling a release on the loaded image(s).  We've observed this using Activity Monitor and looking at the memory our App is taking up.  Basically, the memory space is increase by the size of the image(s) we are loading (even after a release call). When our app starts up, it consumes maybe 20-30MB but as we start loading the images repeatedly and disposing this ends up growing to the Gigabyte range.  So, the question is how can we stop this memory leak from occurring? Basically we are executing the following code and observing an increase in our app's memory usage footprint: NSImage *image = [[NSImage alloc] initWithContentsOfFile:filepath]; [image release];

We have a question with respect to the Live Text feature shown in the Keynote. Is there an API or Framework available for this? Also, if there is a Framework/API available can we leverage it on macOS?

We have a set of questions about Notarization. We create plug-ins for various 3rd party software. Our plug-ins operate under the 3rd party software. So for example Photoshop (our is not a typical Mac App store app - we make these also so we know how Mac App store code-signing etc works).Our infrasturcture is something like "plug-ins" for each version of Photoshop we support (which gets installed in the Photoshop plug-ins folder). Then component libraries that are installed in Library/Application Support/OurProduct folder and the Applications folder (we also create a folder in the Applications folder and stick in various other parts and libraries, readme, userguide etc). So its basically a set of libraries really thats all over.Then we take all of those components and we package (using Package Maker under 10.11.6) it and create flat package installers (which contain installer plug-ins at the end) which we deliver to our end user. The final installer are signed using th Apple 3rd party install certificate.None of these parts are code-signed as we never had to.So, we have multiple questions here. Do we have i to codesign each library/plug/bundle/component included in the pkg file? When we submit for notarization, do we just submit the final pkg (the pkg can contain other pkg files) file. Now when the Photoshop plug-in access our other libraries/bundles (they are loaded dynamically) will it cause loading/binding/excution problems?

Hello -We have been trying for the past 2 days to get our Mac App submitted passed through the Mac App review process. We have updated our signing certificates and even created new provisioning profiles for signing and using the XCODE - Organizer to validate and upload to the Mac App store. We confirmed the bundle receipt etc.However the Mac App store review board keeps on telling us our app is crashing on launch time with the following under 10.12.6 during the review process:Exception Type: EXC_CRASH (Code Signature Invalid)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace CODESIGNING, Code 0x1Termination Details: CODESIGNING, When validating /Applications/PDF2Office for iWork 2017.app/Contents/MacOS/PDF2Office for iWork 2017: Code has restricted entitlements, but the validation of its code signature failed.Unsatisfied Entitlements:We are using 10.11.6 and XCODE 7.3.1 but we just dont get it. The App review were able to test the app about 4 days ago and recommend we make some minor UI changes due to Mac App store policies but now its not getting past the startup. Our application has the main App and plug-ins in the plug-ins folder. So why does it crash due to a Code Signing validation saying the signature is invalid?Are we supposed to build using XCODE 8.3.3 and 10.12.6?