Post not yet marked as solved
Hello, I have uploaded a new version 1.1.5 of my mac apple store desktop app using the MacOS Transporter program.
The app was uploaded successfully, except with a warning message:
"Cannot be used with TestFlight because the signature for the bundle at “RenderTune.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight." (90886)
However when I browse my builds, there is no version for 1.1.5 that I can delete. So is there anyway I can upload and publish version 1.1.5 or is it forever lost? I can't just skip versions, I need to be able to increment by one and release version 1.1.5. But transporter won't let me.
Post not yet marked as solved
Electron-Builder Version: 24.12.0
Electron-Builder-notarize Version: 1.5.1
Node Version: v15.14.0
Electron Version: 11.3.0
Electron-updater version: ^4.3.5
Target: Mac Apple Store (mas)
Hello, I am trying to build and sign a new version of my electron app for the mac apple store (mas), but when I get to the final step of uploading the RenderTune.pkg file to the mac transporter app, I get a failed status with 22 errors all the same formatting like so:
Asset validation failed (90284)
Invalid Code Signing. The executable 'com.martinbarker.digifyunique.pkg/Payload/RenderTune.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/etc....dylib' must be signed with the certificate that is contained in the provisioning profile. (ID: abc-abc-abc-abc-abc)
In order to build and sign this RenderTune.pkg file, first I run the command npm run build-mas locally while on branch v1.1.5 ( code here )
Which runs the following command:
"build-mas": "electron-builder build --mac && sh signmasscript.sh",
So first it runs electron-builder build --mac and gives this output:
Martins-MacBook-Air:rendertune-v1.1.5-feb-24 martinbarker$ npm run build-mas
> rendertune@1.1.5 build-mas
> electron-builder build --mac && sh signmasscript.sh
• electron-builder version=24.12.0 os=20.6.0
• loaded configuration file=package.json ("build" field)
• writing effective config file=dist/builder-effective-config.yaml
• packaging platform=darwin arch=x64 electron=11.3.0 appOutDir=dist/mac
• signing file=dist/mac/RenderTune.app platform=darwin type=distribution identity=ACBACBACBACBACBACBACBACBACB provisioningProfile=none
• skipped macOS notarization reason=`notarize` options were not provided
• building target=DMG arch=x64 file=dist/RenderTune-mac.dmg
• building target=macOS zip arch=x64 file=dist/RenderTune-mac.zip
• building block map blockMapFile=dist/RenderTune-mac.dmg.blockmap
• building block map blockMapFile=dist/RenderTune-mac.zip.blockmap
Completes without issue. The next part is running the signmasscript.sh file, which does complete but gives these errors:
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1
productbuild: Adding component at /Users/martinbarker/Documents/projects/rendertune-v1.1.5-feb-24/dist/mas/RenderTune.app
productbuild: Signing product with identity "3rd Party Mac Developer Installer: Martin Barker (LV6WXG529F)" from keychain /Users/martinbarker/Library/Keychains/login.keychain-db
productbuild: Adding certificate "Apple Worldwide Developer Relations Certification Authority"
productbuild: Adding certificate "Apple Root CA"
productbuild: Wrote product to /Users/martinbarker/Documents/projects/rendertune-v1.1.5-feb-24/RenderTune.pkg
productbuild: Supported OS versions: [10.10.0, )
The final output RenderTune.pkg file gives 22 error messages saying `` when I try to deliver it via the mac os transport app.
Asset validation failed (90284)
Invalid Code Signing. The executable must be signed with the certificate that is contained in the provisioning profile
Is my app even being signed correctly? Or is there just one file that I need to fix? Please help me out !
Post not yet marked as solved
Hello, I am trying to use XCode to generate a 'embedded.provisionprofile' file. My Xcode macos project keeps giving me an error saying:
Provisioning profile "BRandNewMebedded" doesn't include signing certificate "Apple Distribution: Martin Barker (LV6WXG529F)".
When I download the Provisioning Profile file "BRandNewMebedded" from online, I make sure it has "Mac App Distribution" checked, but even if i edit it to use the first option "Distribution" and re-download it, my XCode keeps saying the same error in red.
Post not yet marked as solved
Hello, I am trying to publish an electron app on the apple mac store. My program can be built for mac / linux / windows, but if I try to build it for the mac apple store (mas) ffmpeg fails with the error:
ffmpeg was killed with signal SIGILL
when I try to use my app in it's built mas sandboxed mode.
Since ffmpeg works fine when I run locally and build for any other platform, I think there is an issue with my mas build entitlements. This is my first time ever making an electron app for the mac apple store so any help would be much appreciated.
My electron app has this code which initiates ffmpeg using the npm libarary fluent-ffmpeg:
				//begin get ffmpeg info
				const ffmpeg = require('fluent-ffmpeg');
				//Get the paths to the packaged versions of the binaries we want to use
				var ffmpegPath = require('ffmpeg-static-electron').path;
				ffmpegPath = ffmpegPath.replace('app.asar', 'app.asar.unpacked')
				var ffprobePath = require('ffprobe-static-electron').path;
				ffprobePath = ffprobePath.replace('app.asar', 'app.asar.unpacked')
				//tell the ffmpeg package where it can find the needed binaries.
				ffmpeg.setFfmpegPath(ffmpegPath); //"./src/ffmpeg/ffmpeg"); //ffmpegPath
				ffmpeg.setFfprobePath(ffprobePath); //"./src/ffmpeg/ffprobe"); //ffprobePath
				//end set ffmpeg info
Inside my package.json file I have the following build code:
	"build": {
		"asarUnpack": [
			"node_modules/ffmpeg-static/bin/${os}/${arch}/ffmpeg",
			"node_modules/ffmpeg-static/index.js",
			"node_modules/ffmpeg-static/package.json"
		],
		"appId": "com.martinbarker.digify",
		"productName": "Digify-mac",
		"buildVersion": "1",
		"copyright": "Copyright © 2020 Martin Barker/company",
		"mac": {
			"icon": "build/icon.icns",
			"hardenedRuntime": true,
			"entitlements": "build/entitlements.mas.plist",
			"type": "distribution",
			"provisioningProfile": "embedded.provisionprofile",
			"target": [
				"mas"
			]
		},
My entitlements.mas.plist file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
		<dict>
				<key>com.apple.security.app-sandbox</key>
				<true/>
				<key>com.apple.security.inherit</key>
				<true/>
				<key>com.apple.security.application-groups</key>
				<string>##TEAMID###.com.martinbarker.digify</string>
				
				<key>com.apple.security.files.user-selected.read-only</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.device.audio-input</key>
				<true/>
				
				<key>com.apple.security.personal-information.location</key>
				<true/>
		
		</dict>
</plist>
In order to build my MAS .app file, I run:
electron-builder build --mac
from my mac terminal. Once it finishes, I sign my .app file with this command:
sudo codesign --deep --force --verbose --sign '##MAC-DEVELOPER-ID##' dist/mas/Digify-mac.app
Once signed, I can open the .app file, but when I try to run an ffmpeg command, I get the ffmpeg was killed with signal SIGILL error.
I have been trying to get ffmpeg to run when my app is in this sandboxed stage, but with no luck. This issue was mentioned previously in this developer post that I've been trying to follow but with no luck:
https://developer.apple.com/forums/thread/87849
MartinBarker.