Executable Issues

Unable to check executable as the plist is invalid

There were errors with Info.plist checker, which means App Wrapper doesn't know the name of the main executable file.

Unable to check executable as Info.plist is missing "CFBundleExecutable"

There were errors with Info.plist checker, which means App Wrapper doesn't know the name of the main executable file.

Unable to check executable as "CFBundleExecutable" is blank

There were errors with Info.plist checker, which means App Wrapper doesn't know the name of the main executable file.

Unable to read "<file/>" <errorMessage>

App Wrapper wasn't able to open the file or encountered a problem when doing so.

<file/> <architecture/> has the file type of <type/> and not executable

The main executable file should be marked as an executable file, instead it is marked as <type/>. While this may not cause any problems at the moment, it should be corrected in a future version of this application, to prevent it from becoming a problem down the road.

<file/> doesn't contain any allowed architectures, only <architecture/>

The solution is to rebuild the library, executable so that it does contain the architectures that the application is intended to ship with. In some circumstances this can be temporarily ignored.

32-Bit Intel is not allowed for new apps or feature updates on the  App Store

This is a general rule and some developers are allowed to ship 32-Bit Intel apps, however the application should be rebuilt to whatever architecture Apple is promoting this week.

Unable to check <Path/> as the path appears invalid

This generally happens when the application or components of the application are deleted while App Wrapper is still scanning the application. Please wait for App Wrapper to finish scanning the application before trying to remove components.

Unable to check <Path/> as it doesn't exist

This generally happens when the application or components of the application are deleted while App Wrapper is still scanning the application. Please wait for App Wrapper to finish scanning the application before trying to remove components.

<Path/> <architecture/> links to <library/>, prohibited on the  App Store.

The  App Store some some very specific rules about what libraries can and can not be used (most are unpublished). Remove these libraries from the application and use alternatives if possible.

The minOS identifies this as a <appType/> application and not a Mac app

The executable file contains meta data on what platform it is for. Ideally the application should be rebuilt, check with the developer tools documentation on how to specify this as a Mac app. As Apple continues to merge iOS, iPadOS and macOS, this may no longer be relevant in future versions of the macOS.

<Path/> <architecture/> requires macOS <version/>

The executable file contains meta data on what the minimum OS is that it will run on. This version is higher than the minimum OS specified on the "General" Page.

It is possible to specify different OS versions for different architectures, but this document hasn't been updated to cover arm architectures and all requests to Apple for information have not yet been fulfilled.

<Path/> <architecture/> needs updating to 10.9 SDK

Apple's Notarization services requires all executables and libraries to require a minimum of Mac OS X 10.9. Ideally rebuild the application or library in a newer version of the development tools and against a newer SDK. A future version of App Wrapper will allow manual specification for nested executables and libraries.

Unable to check minOS & SDK for <architecture/> <Path/>

Means that App Wrapper couldn't find the minimum OS meta data for this file. Ideally the library should be rebuilt and this information set during the build. Apple may reject the application for this.

<Path/> <architecture/> requires a LC_UUID

Apple requires executables and libraries to be given a specific identifier for that architecture and version. Rebuild this file in the development tools and make sure that one is being included. A future version of App Wrapper may include functionality to add one.

<Path/> doesn't match main app architectures <architecture/>

Ideally all nested executables and libraries should match the main executable in architectures. This may cause problems, it may not.