Adding application ID to .pkg file seemed to work
Original
<?xml version="1.0" encoding="utf-8"?> <plist version="1.0"> <dict> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.network.client</key> <true/> <key>com.apple.security.files.user-selected.read-write</key> <true/> </dict> </plist>
My modified version
<?xml version="1.0" encoding="utf-8"?> <plist version="1.0"> <key>com.apple.application-identifier</key> <1234567890.com.My.App/> <key>com.apple.developer.team-identifier</key> <com.My.app/> <dict> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.network.client</key> <true/> <key>com.apple.security.files.user-selected.read-write</key> <true/> </dict> </plist>
I created a .pkg file which installed to Applications folder and the app worked fine, but when I uploaded the app with transporter I got the message 'executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true'
I presume you’ve read TestFlight, Provisioning Profiles, and the Mac App Store. If not, please do so now.
As to what’s going wrong, it’s hard to say because I’m not confident that the XML snippets you posted survived the trip into DevForums. In future, I recommend that you put them in a code block. See tip 3 in Quinn’s Top Ten DevForums Tips.
Having said that, there’s an easy way to see what this file should look like:
- Create a dummy Xcode project with the same bundle ID as your app.
- Make sure that automatic code signing is enabled.
- Add some restricted entitlement to the app. See TestFlight, Provisioning Profiles, and the Mac App Store for more about that.
- Build the app.
- Dump its entitlements:
% codesign -d --entitlements - --xml /path/to/your.app
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"