Additional guidance for macOS Sierra.

Discussed new Gatekeeper checks added since OS X v10.11. Added information about signed kexts. Made other editorial improvements.

Cover changes to linking to dynamic libraries outside of an app bundle.

Add reference to the new check-signature tool.

Added v2 signature FAQ and additional guidance for developers transitioning to v2 signatures.

Added clarifications of Mavericks and Yosemite code signing changes.

Updated discussion of significant code signing changes in OS X Mavericks. Other editorial changes.

Added discussion of significant code signing changes in OS X Mavericks. Other editorial changes.

Omitting files from the signature’s seal is deprecated on OS X Mavericks.

New document that intermediate to expert level overview of macOS code signing that details specific options and gotchas

Copyright © 2016 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2016-09-13

Debug System Pref Pane w/10.15 and System Integrity Protection

In the past, I have been able to run/debug a self-developed Preference Pane in System Preferences by self-signing a copy of the System Preferences app, and setting it as the run target in Xcode.

A symbolic link is placed in

/Library/PreferencePanes that points to the output prefPane built by Xcode and everything works. at least it used to under 10.11 through 10.14.

Under 10.15 this breaks. While the prefPane properly loads with the real (Apple-Signed) System Preferences app, when I try to run my prefPane in the self-signed copy of System Preferences, I get «Could not load preference pane». The same thing happens when trying to load any of the Apple built-in pref panes as well.

I have tried both:

No errors are generated in the Console.

My guess is that somewhere in the loading process, it is checking to see if the System Preferences host app is signed by Apple. If I try to use the real System Preferences app as a debug target, I get a System Integrity Protection error.

Is there any way to do this without disabling SIP like there was in 10.11 to 10.14?

The Code Signature Version Is No Longer Supported

The code signature version is no longer supported

An app signed with a codesign version provided on an older macOS, like Catalina (10.15) will not run on iOS 15 because the lastest version you can install is Xcode 12.4.

Xcode 12.5 seems to change the behavior of codesigning. When installing you get the error message:

The code signature version is no longer supported

Is there a workaround?

Answers:

If signing through Xcode, you can add this flag to the OTHER_CODE_SIGN_FLAGS setting in the Build Settings tab.

If codesigning at the command-line:

The source of this information was the Apple Forum thread and the answer from Matt Eaton in DTS at Apple.

In the Xcode 12.5 Release Notes there is also a reference to the new signature format. However, it seems the information is not entirely correct.

* The answers/resolutions are collected from stackoverflow, are licensed under CC BY-SA 4.0

Xcode 8.3 / Xcode 9.0 Refresh provisioning profile devices

I have added some new devices. How can I refresh the provisioning profile, as Xcode 8 automatically manages signing assets?

I have found this question: Refresh devices in team provisioning profile managed by Xcode 7? – but we can’t do that in Xcode 8.3.

I don’t have the device with me so I manually added it in the portal and also edited the provisioning profile but Xcode is not re-downloading it.

5 Answers 5

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is what you need to do:

/Library, you can delete one profile and by the time you’ve returned to Xcode, the profile has already being used.

Remove the .mobileprovision file for the app this way :

The command in the terminal is : rm

Step 1. Click on desktop then from top menu Go > Go to Folders.

Step 2. Write/Paste following path and enter:

Step 3. Select Provisioning Profiles folder and delete all provisions profiles in it

Step 4. Go to xCode Preference > Accounts > Apple ID and then click on Download Manual Profiles button

/Library/MobileDevice/Provisioning\ Profiles/ but no luck, this ended my search.

First delete the provisioning profile from

To add devices to your provisioning profile in Xcode 8 with automatic code signing, you simply need to build to the device in Xcode. Xcode will add the device’s UDID and regenerate the provisioning profile automatically. If you don’t have physical access to the device, I don’t think there is a way to add it to your provisioning profile without going back to manually managing your devices and profiles.

Mac App store Code Signing EXC_CRASH (Code Signature Invalid)

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, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

Termination 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.

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?

Replies

I just ran into the same problem building with XCode 8.3.3 for 10.11.*

I uploaded a build a few days ago without problems; running into code-signing problems with my latest build after having made no change to provisions/capabilities in my project.

Same on Xcode 8.3.1 for 10.11.

Just to let everyone know, we generated updated distribution profiles and built under 10.12.6 and submitted and it worked I guess. I have no clue why, but seems like there must have been some kind of bug either with XCODE and codesigning under 10.11.x or something changed in Apple’s back end which we have no idea about that must have affected code signing recently.

Got the same issue as well. Very minimal bug fix and 2 days later got this rejection even though it launches fine for me. I haven’t done anything to my profiles.

I’m facing the same issue and they have rejected the app. We did not make any entitlement changes for the released version and they have rejected our app twice. Tried resubmitting by re generating provisioning profile but no luck. Any solution for this rejection?

I have exactly the same problem and couldn’t find a way, so far, to fix it. I just made a few changes, submitted my macOS app for review and got it rejected due to the «Code has restricted entitlements, but the validation of its code signature failed.» issue. I have no idea how to even debug this. Did others encounter a similar problem and found a fix or at least an approach to debug the issue?

I turned off automatic code signing and just generated provisioning profiles in the Member Center for my app. Resubmitted and it was approved.

Heh just had two app updates get rejected again. Looks like the code signing crash is happening at launch (again). So my new provisioning profiles I made only a couple weeks ago aren’t working. Really ridiculous amount of time has to be spent on this.

Did you find any solution? We are also facing the same issue.

I can’t comment on how to prevent a provisioning profile to break. But if you get your app rejected during App Store review due to a CODESIGNING crash (without having changed anything relevant), you could try the following if you let Xcode manage code signing automatically in your project:

1) Delete all your provisioning profiles in your Apple developer account

2) Rebuild and archive your app

3) Before uploading it to the app store, you are shown the provisioning profile in use. There’s a small link next to it. Click it and it shows you a cached version on your local drive in Finder. If the creation date of this one is old, move it (and all other cached provisionining profiles) away, e.g. to the Desktop folder.

4) Cancel the upload to the app store.

5) Rebuild and archive your app again. This time Xcode is forced to create a new provisioning profile and a new upload to the app store should now work.

This fixed the problem for me, but I have no idea why the problems happen in the first place.

App Installation failed. No code signature found

I recently upgraded to Xcode 10 and began the process of updating our app to switch 4.2 After a day or so of rebuilding 3rd party frameworks and adding in workarounds to various issues, I was able to run our app on the new simulators.

However, when I tried running on my personal phone (running iOS 12.0 GM) I ran into an error when installing the app as described in the title.

I know that there are a lot of already answered questions regarding this topic on SO & the Internet, however I was unable to get any of these to work.

It’s been blocking me for around a day & a half now so I was wondering if anyone had any insight into how this could be mitigated.

Here are the steps I’ve take so far that have not worked (perhaps they will work for others in the future!):

Any help would be greatly appreciated 🙂

Update: I tried redownloading and rebuilding from the ground up on a fresh machine, and the same issue occurs. Interestingly I can archive and validate the app just fine.

Also tried signing an empty project with the same bundle ID and it worked fine. So the issue is either in our 3rd party frameworks or some weird setting that got enabled while transitioning from Xcode 9.4. Going to start removing 3rd party frameworks one by one until I can get this to compile.

Update 2: Still no luck. Tried clearing out most frameworks and nothing. Here are the device logs, wondering if Skipping a profile because of error 0xe8008012 has something to do with it:

Update 3: So I was able to get it to install, by commenting out the carthage copy-frameworks script in the build phases (and cleaning/nuking derived data after doing so). Of course this means that it crashes on boot since it’s missing those frameworks, but it does mean the issue is either with carthage or one of the linked carthage frameworks. Not our signing certs, provisioning profiles, or codebase. Going to try removing those frameworks one by one and I’ll update here.

Final Update Figured it out finally. The solution turned out to be pretty niche (see below) but hopefully this question serves as a compilation of every solution related to this issue across the internet haha.

The Code Signature Version Is No Longer Supported

The code signature version is no longer supported

An app signed with a codesign version provided on an older macOS, like Catalina (10.15) will not run on iOS 15 because the lastest version you can install is Xcode 12.4.

Xcode 12.5 seems to change the behavior of codesigning. When installing you get the error message:

The code signature version is no longer supported

Is there a workaround?

Answers:

If signing through Xcode, you can add this flag to the OTHER_CODE_SIGN_FLAGS setting in the Build Settings tab.

If codesigning at the command-line:

The source of this information was the Apple Forum thread and the answer from Matt Eaton in DTS at Apple.

In the Xcode 12.5 Release Notes there is also a reference to the new signature format. However, it seems the information is not entirely correct.

* The answers/resolutions are collected from stackoverflow, are licensed under CC BY-SA 4.0

Some Code Answers

More Answers Related The Code Signature Version Is No Longer Supported

The code signature version is no longer supported

1 week ago Jul 21, 2021 · An app signed with a codesign version provided on an older macOS, like Catalina (10.15) will not run on iOS 15 because the lastest version you can install is Xcode 12.4. Xcode 12.5 seems to change the behavior of codesigning. When installing you get the error message: The code signature version is no longer supported.

The code signature version is no longer supported with …

1 week ago Feb 09, 2022 · The code signature version is no longer supported with Xcode 13. I get the message Unable to install «App» when running my Xcode 13 project on a physical iPhone running iOS 15. If I click «Details», I see the below information (most notably The code signature version is no longer supported ).

‘The code signature version is no … | Apple Developer …

4 days ago May 30, 2022 · https://developer.apple.com/documentation/xcode/using-the-latest-code—signature-format. However, if you are using Xcode, Xcode SHOULD be leveraging the latest code signature when signing. If you have multiple versions of Xcode installed, this may not be the case though depending on the Xcode Command Line tools selected.

› See also: Xcode

The code signature version is no l… | Apple Developer …

The code signature version is no l… | Apple Developer …

5 days ago Nov 16, 2021 · The code signature version is no longer supported.”. Version info: 2019 iMac running Catalina (10.15.7) Xcode 10.1. Xojo 2021r2.1. iOS 15.0.2. Steve_Koger (Steve Koger) November 16, 2021, 5:47pm #2. My understanding is that iOS15 requires xcode 13. I see you list your xcode as 10.1.

› See also: Xcode List

iOS15 «The code signature version is no longer supported»

6 days ago Sep 22, 2021 · 2. It appears that Unity Cloud Build is not including DER enabled entitlements in their code-signing process. This prevents the builds from working on iOS 15. You can fix these builds by downloading it, unzipping it, re-signing the app with DER included, re-zipping it and uploading it to UCB as a manual build.

The code signature version is no l… | Apple Developer Forums

5 days ago Dec 28, 2021 · The code signature version is no longer supported Apple has changed the codesign signature to include DER encoded entitlements in addition to the plist encoded entitlements. This additional DER encoded entitlements section is required in iOS 15 and becomes the default behavior of codesign in the latest Xcode

› See also: List

iOS : The code signature version is no longer supported

2 days ago iOS : The code signature version is no longer supported [ Gift : Animated Search Engine : https://bit.ly/AnimSearch ] iOS : The code signature version is no.

ApplicationVerificationFailed 0xe8008029 (The code signature version …

6 days ago Nov 17, 2021 · avinashkumar95 changed the title ApplicationVerificationFailed ApplicationVerificationFailed 0xe8008029 (The code signature …

iOS app testing. App installation failed. No code signature found [closed]

I’ve tried to install my app on several iOS devices. But this thing didn’t let me to.

I want to know, what the problem is and how should I solve it.

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

In my case, the problem was unsigned frameworks.

Xcode 11 or above:

Go to Build Phases, expand Embedded Frameworks and select all Code Sign on Copy checkboxes.

Xcode 10 or earlier:

Build Phases > Copy Files > Code Sign on Copy (select all checkboxes)

I had this problem, this is what I did to resolve it:

Only if you have Cocoapods in your project:

Now you can open your fresh Xcode.

Hope this help you.

In my case the problem was created by adding a new cocoa touch framework.

/Library/Developer/Xcode/DerivedData was enough in my case.

If «code sign on copy» fails, then check if you are modifying the frameworks in a run script after the «Embed Frameworks» phase.

If you are, then move the Run script to a position before the «Embed Frameworks» phase.

In my case, I have created an unsigned IPA file and for this i had made some changes in SDKSetting.plist file (changed CODE_SIGNING_REQUIRED = NO) and it should be always YES if you are running application on the device.

To resolve this follow the below steps: Steps to create unsigned IPA (Tested on Xcode 9.4.1)

Step 1: Open finder > Go to Folder.. as below screen

and then copy and past the below line:

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS*.*.sdk/SDKSettings.plist

Open iPhoneOS.sdk as showing in below image:

Step 2: Copy the SDKSettings plist in another folder because you can’t make changes here:

Step 3: Make the change in duplicate

set CODE_SIGNING_REQUIRED to YES

Step 4: Now replace duplicate Plist with the original one (Both names must be the same). This will also ask admin permission to change.

Unable to run (install) app in real device v12.0.2 (Xcode 13.1) #1924

Comments

Elshad commented Oct 26, 2021 •

Checklist before submitting a bug report

Xcode version

Facebook iOS SDK version

Dependency Manager

SDK Framework

Goals

Successfully run app in real device using Xcode 13.1.

Expected results

Actual results

«Unable to install app» dialog in Xcode 13.1

This issue is not present in v12.0.2 in Simulator
This issue is not present in v11.2.1

Steps to reproduce

Use the latest Facebook SDK (v12.0.2) and try run a project using Xcode 13.1 in real device

Code samples & details

The text was updated successfully, but these errors were encountered:

jawwad commented Oct 27, 2021

Elshad commented Oct 28, 2021

Analytics Event: com.apple.dt.IDERunOperationWorkerFinished : <
«device_model» = «iPhone13,4»;
«device_osBuild» = «15.1 (19B74)»;
«device_platform» = «com.apple.platform.iphoneos»;
«launchSession_schemeCommand» = Run;
«launchSession_state» = 1;
«launchSession_targetArch» = arm64;
«operation_duration_ms» = 4405;
«operation_errorCode» = «-402620375»;
«operation_errorDomain» = «com.apple.dt.MobileDeviceErrorDomain»;
«operation_errorWorker» = IDEInstalliPhoneLauncher;
«operation_name» = IDEiPhoneRunOperationWorkerGroup;
«param_consoleMode» = 0;
«param_debugger_attachToExtensions» = 0;
«param_debugger_attachToXPC» = 1;
«param_debugger_type» = 5;
«param_destination_isProxy» = 0;
«param_destination_platform» = «com.apple.platform.iphoneos»;
«param_diag_MainThreadChecker_stopOnIssue» = 0;
«param_diag_MallocStackLogging_enableDuringAttach» = 0;
«param_diag_MallocStackLogging_enableForXPC» = 1;
«param_diag_allowLocationSimulation» = 1;
«param_diag_gpu_frameCapture_enable» = 0;
«param_diag_gpu_shaderValidation_enable» = 0;
«param_diag_gpu_validation_enable» = 0;
«param_diag_memoryGraphOnResourceException» = 0;
«param_diag_queueDebugging_enable» = 1;
«param_diag_runtimeProfile_generate» = 0;
«param_diag_sanitizer_asan_enable» = 0;
«param_diag_sanitizer_tsan_enable» = 0;
«param_diag_sanitizer_tsan_stopOnIssue» = 0;
«param_diag_sanitizer_ubsan_stopOnIssue» = 0;
«param_diag_showNonLocalizedStrings» = 0;
«param_diag_viewDebugging_enabled» = 1;
«param_diag_viewDebugging_insertDylibOnLaunch» = 1;
«param_install_style» = 0;
«param_launcher_UID» = 2;
«param_launcher_allowDeviceSensorReplayData» = 0;
«param_launcher_kind» = 0;
«param_launcher_style» = 0;
«param_launcher_substyle» = 0;
«param_runnable_appExtensionHostRunMode» = 0;
«param_runnable_productType» = «com.apple.product-type.application»;
«param_runnable_swiftVersion» = «5.5.1»;
«param_runnable_type» = 2;
«param_testing_launchedForTesting» = 0;
«param_testing_suppressSimulatorApp» = 0;
«param_testing_usingCLI» = 0;
«sdk_canonicalName» = «iphoneos15.0»;
«sdk_osVersion» = «15.0»;
«sdk_variant» = iphoneos;
>

macOS Version 12.0.1 (Build 21A559)
Xcode 13.1 (19466) (Build 13A1030d)
Timestamp: 2021-10-28T17:37:46+04:00

jawwad commented Oct 29, 2021

So it looks like the underlying error you are getting is:

The code signature version is no longer supported

We weren’t able to reproduce this and have not received any other reports of this so we’re not sure that this is an issue with the SDK itself. You said that the issue isn’t present in v11.2.1. Does that mean if you downgrade back to v11.2.1 you are successfully able to install the app?

Elshad commented Nov 3, 2021

Hello @jawwad, sorry for late answer.

guidev commented Nov 5, 2021 •

I know it’s weird, but I’m having the same issue upgrading from 12.0.2 to 12.1.0.

Downgrading to 12.0.2 solves the issue for me.

Also, when trying to submit the app to the App Store, I get the following error:

» Found an unexpected Mach-O header code: 0x72613c21 «

Error Domain=DVTMachOErrorDomain Code=0 «Found an unexpected Mach-O header code: 0x72613c21» UserInfo=

jawwad commented Nov 5, 2021

I know it’s weird, but I’m having the same issue upgrading from 12.0.2 to 12.1.0.
Downgrading to 12.0.2 solves the issue for me.
Also, when trying to submit the app to the App Store, I get the following error:
» Found an unexpected Mach-O header code: 0x72613c21 «

I don’t think we changed anything with how libraries are built from 12.0.2 from 12.1.0 so this is interesting. Let me see what we can figure out on this. cc @samodom.

jawwad commented Dec 6, 2021

Elshad commented Dec 10, 2021

@jawwad I am still using v11.2.1 and not tested new versions after this issue. Did not risk because i use this SDK in corporate app

jawwad commented Dec 13, 2021

jawwad commented Jan 20, 2022

I’m going to close this issue out for now. Let us know if the problem persists with the latest release of the SDK (v12.3.0) and we’ll re-open to investigate further.

pruthvi-itribe commented Jan 22, 2022

I have tested in facebook latest SDK ( v12.3.1) still the issue is persisting

pruthvi-itribe commented Jan 22, 2022

Elshad commented Feb 1, 2022

Hi @jawwad i also tested 12.3.1 SDK with Xcode 13.2.1, same problem 🙁

code signature version is no longer supported #1078

Comments

jperedadnr commented Dec 28, 2021 •

An app signed with a codesign version provided on an older macOS, like Catalina (10.15) will not run on iOS 15 because the lastest version you can install is Xcode 12.4.

Xcode 12.5 seems to change the behavior of codesigning. When installing you get the error message:

The code signature version is no longer supported

Apple has changed the codesign signature to include DER encoded entitlements in addition to the plist encoded entitlements. This additional DER encoded entitlements section is required in iOS 15 and becomes the default behavior of codesign in the latest Xcode

Modifying codesign with:

fixes the problem for older Xcode versions, and doesn’t hurt with the latest (as DER is already generated).

Expected Behavior

Current Behavior

Steps to Reproduce

Your Environment

The text was updated successfully, but these errors were encountered:

Invalid code signature due to inadequate entitlements

I am trying to run an app on my physical device, it starts to build onto my device then crashes due to an ‘invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.’

I have updated my iPhone and Xcode to the latest release, tried to clean the build and edit run scheme build configuration to ‘Release’ and tried to set my executable to ‘Ask On Launch’. I searched for a Iphone Developer file on keychain and could not seem to find one but i am not sure what i am supposed to do.

Can anyone help?

9 Answers 9

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

The problem is that the developer is not trusted on the device. If you manually try to run the apps on the device, you will see an Untrusted Developer message.

For newer versions on your iPhone (version 14+)

Please check the internet connection of the Testing IOS device, Signature verification fails if device isn’t connected to Internet.

I had the same issue, I just

I hope it helps.

on your iphone, Settings > General > Profiles or Settings > General > Device Management

Developer app. (Click on) for trust.

In my case simply reconnecting the lightning cable did the job.

If nothing works, do this,

This work after upgrading to iOS 15.

If you see this issue happen out of nowhere, one other possible source of the problem is a network outage.

Your device will periodically need to dial out to a service to validate the provisioning profile. I don’t have details on how often this needs to happen but I do know this validation action happens during the app’s startup. If your device can’t connect to the internet or Apple is experiencing an outage, it can interrupt this process and produce this error.

«The Developer of this app needs to update it to work with this version of iOS» pop up coming when launching Enterprise app for iOS 15

We have an enterprise account, and till iOS 14 there were no issues, but as soon as user update their phones to iOS 15, they are getting this alert.

Now, this issue is coming only for enterprise apps running on iOS 15. I have done some research and found this article. https://developer.apple.com/documentation/xcode/using-the-latest-code-signature-format.

In here it states that

To check whether an app called MyApp.app has the new signature, you can use the

Look in the output for a string such as CodeDirectory v=20500. For any value of v less than 20400, you need to re-sign your app.

I did that and my output was indeed v=20400. I have signed the app using Xcode 12.5 running on Mac OS 11.2.3. I don’t think Apple documents are correct for this. (I could be wrong)

Can anyone please help and let me know, what exactly we need to do to get this issue fixed?

EDIT: I was able to solve this issue by upgrading OS to Big Sur. Xcode version was 12.5.

iOS: Code signature invalid/required code signature missing

I’m currently working on an iOS tweak called «LockWatch» that is supposed to display watchOS-like watch faces on the lock screen. This tweak involves a basic plugin system that loads a bundle (name.watchface) from a specified directory, which is working so far.

The problem is, however, that these bundles cannot be executed on a device due to either a missing or an invalid code signature, but inside the iOS Simulator, the bundles are loaded and executed just fine.

I had this working on iOS 9 by adding the «com.apple.backboard.client» entitlement (because the logs said that this particular entitlement was missing and therefore SpringBoard was crashing).

The bundle project itself is a simple Xcode project created with a «Bundle» target from the macOS tab, the Base SDK is set to «Latest iOS (10.2)».

I’ve tried the following signing methods:

The logs changed between these two texts:

Because the binary cannot be executed, its principal class instance cannot be added to an array and SpringBoard crashes.

Unable to install Xamarin watchOS app on device using automatic provisioning

I’m trying to install a Xamarin watchOS app to a device using Visual Studio for Mac automatic provisioning but getting a «this app could not be installed at this time» error on the iPhone.

I’m on macOS Big Sur (11.6), Visual Studio for Mac (8.10.11), watchOS 8.0.1 on an SE (A2354), and iPhone 11 (iOS 15.0.2). I’ve verified that the iPhone and the watch are listed in devices in the Apple developer center, although I did have to add the watch manually as it doesn’t appear that Xamarin automatic provisioning picked it up.

I can install and run the iPhone app from Visual Studio just fine by clicking the run button but the watchOS app is not automatically installed. The watch app is visible in available apps, but clicking the ‘install’ button results in the «this app could not be installed. » error. Everything runs fine on the simulator if I choose the watchOS project in VS for Mac and run using the simulator. If try to run on my watchOS device installation fails with this error:

Are there additional troubleshooting steps or logs I can review to figure out what’s going on?

ios 15 Cannot install adhoc build app. #1063

»xxxx needs to be updated» prompt is noticed upon installing adhoc build.

Beta Was this translation helpful? Give feedback.

3 You must be logged in to vote

Replies

Harman has not released the SDK that will work with iOS 15, but it sounds like they are working on it and it is coming out hopefully soon.

It is so frustrating that Apple has not given warning to developers about what is breaking, and Apple is releasing iOS 15 in maybe a month or so and the next release of Xcode is not final yet, to give Harman assurance. At least when Apple cleared the app store of 32-bit apps they gave a lot of notice. I have started preparing my customers not to update to iOS 15 until I have the app available (at this point, even ‘if’ as we don’t know what Apple has broken from 14 to 15). Of course thanks to Apple I don’t really know all of my customers except for the ones who have opted in. I guess a bunch of early Christmas presents from Apple. not!

Beta Was this translation helpful? Give feedback.

iOS build fails «No code signature found» when multiple code signing identities have the same name #53891

Comments

taz1208 commented Apr 3, 2020 •

I followed this doc manually ‘https://flutter.dev/docs/development/ios-project-migration’
So Emulator bug fixed but real device not build.
my error snippet «No code signature not found.»

I tried all of solutions but not solved my problems.

Currently I go back to the beginning.

The text was updated successfully, but these errors were encountered:

iapicca commented Apr 3, 2020

taz1208 commented Apr 3, 2020 •

All of that? @iapicca
It’s finished build but It too long text 🙁
Then currently physical device work but emulator is not working
If I follow that offical doc. emulator is working but physical device not working

iapicca commented Apr 3, 2020

Hi again @taz1208
if it’s to long to be pasted in a comment
please attach it as txt file
Thank you

IhwanID commented Apr 3, 2020

All of that? @iapicca
It’s finished build but It too long text 🙁
Then currently physical device work but emulator is not working
If I follow that offical doc. emulator is working but physical device not working

same issue but my emulator work and physical not working 🙁

DanielZanchi commented Apr 4, 2020 •

I tried to purge the cocoapds in ios dir, I removed the xcworkspace file but that didn’t solve.

taz1208 commented Apr 6, 2020

taz1208 commented Apr 6, 2020 •

Currently I don’t followed doc.
Then emulator log snippet is

Again, if you follow document.
Emulator is working, physical device is not working

MobiliteDev commented Apr 6, 2020

I have created a new project on Flutter,a nd added some dependancies:

DanielZanchi commented Apr 6, 2020

exact same message

I have created a new project on Flutter,a nd added some dependancies:

iOS App testing: No Code signature found

I do not have iPhone developer account. I want to test my app on my iPod Touch.

iPod iOS version : 5.1 (9B176 build) Xcode Development SDK : 5.1 Simulators : iPhone 5.1 Retina/normal iPad 5.1 Retina/Normal

To bypass code signing etc, I changed changed the project settings like below.

I connected my iPod-Touch to my MacBook Pro, selected iPod as my target (instead simulator), built the project and ran it. Then I am getting the error «No Code Signature found.»

Note: I did not create any app certificate etc. (I don’t have app dev account)

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You can also get this error if a build gets interrupted partway through. It corrupts Xcode’s internal data (why are they saving corruptible data? I have no idea).

Fully Clean Your Project

It helps if you fully clean up build folder. The usual Project > Clean menu item is not thorough. Use the hidden alternative.

Hold down Option key (⌥) while choosing Product > Clean Build Folder…

The Option key transforms that menu item from «Clean» to «Clean Build Folder» and changes its behavior as discussed in this other question, XCode 4 “Clean” vs. “Clean Build Folder”.

You have to code sign if you want to run your app on an iDevice, unless it’s jailbroken.

You have to have a development licence to code sign your apps.

If you don’t want to buy a developer licence and you are a student, you can apply iOS Developer University Program which allows you to test your apps on actual devices but not to submit App Store.

It is fine if you don’t want to code sign it in the settings, but you MUST code sign it if you want to run it in a Device. That is of course unless you jailbreak your device. which is your only choice since you mention you do not have an app dev account.

Cleaning caches and Xcode DerivedData folder helped me to solve this issue. After cleaning product and product build folder exit Xcode and remove everything in

Then remove all files and folders related to Xcode in

I got this error in Xcode 8.2 because I didn’t have enough space on my device. Thanks Xcode for the descriptive error.

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.1.sdk

How to fix Source option 5 is no longer supported. Use 7 or later

Introduction

When we create Maven projects using artifacts and try to run, we sometimes get the following error. Source option 5 is no longer supported. Use 7 or later. In this post, Let’s see the steps involved to fix the error in the Maven project.

The error (Source option 5 is no longer supported) is common when we create a Maven project from the old archetypes. In this case, we need to specify the source and target version to the Maven compiler. We can specify these properties in Maven pom.xml.

Error

The fix for the problem is to use the latest Java environment for the project that is above JDK 7 or Later.

Identify the JDK version installed on your machine or the version the IDE workspace uses. Update the project build path with latest library settings.

Right-click Project properties >> Java compiler.

Click on the Execution Environments link and select the latest or suitable JDK above JDK 1.7

Click on Apply and Close button.

Maven POM.xml

To avoid this error in the Maven project,

Examples

For example, to specify JDK 8 we can add the properties something like below to the POM.xml file:

JDK 14

Change the Java compiler and the project build path. After the changes specify the JDK version in the POM.xml Maven build file.

Example to specify the JDK 14 to the Maven pom.xml.

Sample pom.xml file with JDK 14 version

Verify the fix

Run the Maven project. The error should be fixed now.

After changing the settings and adding the properties information to the pom.xml file. Verify by running the project. Run As >> Maven Build

For more information on the Maven build tool, visit the official website:

The code signature version is no longer supported

xcode

code-signing

An app signed with a codesign version provided on an older macOS, like Catalina (10.15) will not run on iOS 15 because the lastest version you can install is Xcode 12.4.

Xcode 12.5 seems to change the behavior of codesigning. When installing you get the error message:

The code signature version is no longer supported

Is there a workaround?

Cameron Lowell Palmer

1 Answers

If signing through Xcode, you can add this flag to the OTHER_CODE_SIGN_FLAGS setting in the Build Settings tab.

If codesigning at the command-line:

The source of this information was the Apple Forum thread and the answer from Matt Eaton in DTS at Apple.

In the Xcode 12.5 Release Notes there is also a reference to the new signature format. However, it seems the information is not entirely correct.

The code signature version is no longer supported

Able to build the project but not able to run on device. Project includes swift packages, pods and few static frameworks as well.

Screenshots

Complete error

System Information
macOS Version 12.0 (Build 21A344)
Xcode 13.0 (19234) (Build 13A233)

Created at 6 months ago

I am sorry to hear you are having problems, however, we’ll need more information to debug this. Creating a reproducible example would be best but any additional info would be helpful here.

Created at 7 months ago

Won’t be able to share a reproducible snippet but can you please share what might possibly cause it? The project works fine without using tuist but after implementing tuist this comes up every time.

Created at 7 months ago

We can’t possibly give you a cause when there is no real information to go off of. I recommend reading the docs https://docs.tuist.io to understand if there is any configuration missing in your setup.

We’re going to close this since we can’t do much more here, feel free to re-open if you are able to provide more info

Code Signing Guide

Code Signing Tasks

Typically, Xcode handles most code signing tasks for you, helping you manage your code signing identity, and applying your code signature to apps that you build and distribute. Letting Xcode handle code signing is generally the simplest and safest choice, because Xcode is designed with best practices built in. Read this chapter to gain a better understanding of what Xcode does on your behalf, or to handle special cases where you need to intervene in the code signing process.

About the Code Signing Identity

You sign code using a code signing identity, which consists of a private key plus a digital certificate. The private key is an encryption key that only you have, making it impossible for anyone to forge your signature, as long as you keep the key secure. The digital certificate has a usage extension that enables it to be used for signing, and it contains the public key that complements your private key. The certificate is not secret, and is itself generally signed by a certificate authority, which effectively vouches for your identity. The simple act of code signing does not require a certificate authority’s signature on your certificate, but your signature is much more useful this way because anyone encountering your signature can be confident of its origin.

You can use more than one signing identity, each for its own purpose, such as one for beta seeds and one for final, released products. Also, you typically have different identities for iOS and macOS apps. However, most organizations use a single identity for a given platform and purpose. In other words, you typically do not have more than one Mac App Distribution identity, even if you publish many different apps, but you do have different identities for distributing macOS apps and iOS apps.

Before You Obtain a Signing Identity

Before you obtain a code signing identity and sign your code, consider the following points:

Depending on your company’s internal policies, you might have to involve your company’s build and integration, legal, and marketing departments in decisions about what sort of signing identity to use and how to obtain it. Start this process well in advance of the time you need to actually sign the code for distribution to customers.

Any signed version of your code that gets into the hands of users will appear to have been endorsed by your company for use. Therefore, you might not want to use your “final” signing identity to sign code that is still in development.

A signing identity, no matter how obtained, is completely compromised if it is ever out of the physical control of whoever is authorized to sign the code. That means that the signing identity’s private key must never, under any circumstances, be given to end users, and should be restricted to one or a small number of trusted persons within your company. Before obtaining a signing identity and proceeding to sign code, determine who within your company will possess the identity, who can use it, and how it will be kept safe. For example, if the identity must be used by more than one person, you can keep it in the keychain of a secure computer and give the password of the keychain only to authorized users, or you can put the identity on a smart card to which only authorized users have the PIN.

Important: If you lose control of your Apple-issued signing identity, such as your Developer ID or Mac App Distribution identity, report this to Apple immediately. Apple will invalidate the old identity and help you to replace it. While this seems like a lot of work, it’s critical, because anyone possessing your identity can distribute potentially malicious or destructive code that looks like it came from you.

Obtaining Your Signing Identities

The usual way to obtain a certificate for your signing identity is to get it from Apple. When you sign up for the Apple Developer Program, you gain access to the developer portal, where you can generate certificates for a variety of purposes, including Developer ID certificates (for public distribution of Mac apps), Mac App Distribution certificates (for submitting to the Mac App Store), iOS Distribution certificates (for submitting to the App Store), and others.

Note: Apple uses the industry-standard form and format of code signing certificates. Therefore, if your company already has a third-party signing identity that you use to sign code on other systems, you can use it with the macOS codesign command. Similarly, if your company is a certificate issuing authority, contact your IT department to find out how to get a signing certificate issued by your company. However, while these valid certificates allow you to sign your code, you can only distribute through the App Store or through the Developer ID program when you sign with a certificate issued by Apple.

Xcode helps manage your code signing identities when you use the certificates available through the developer portal. For details on how to use Xcode to do this, see Manage signing certificates in Xcode Help.

If you choose to manage your signing identities manually because you are using a certificate authority other than Apple, you create them using the Certificate Assistant, which is provided as part of the Keychain Access application. You use this tool to create a public/private key pair, add these keys to your keychain, and generate a certificate request that you send to a certificate authority. In response, the certificate authority sends you a signed certificate that, in combination with the private key stored only on your system and known only to you, completes your digital identity. These are essentially the same steps Xcode carries out on your behalf (using Apple as the certificate authority) when it manages your code signing identity.

Open Applications > Utilities > Keychain Access.

From the Keychain Access menu, choose Certificate Assistant > Request a Certificate from a Certificate Authority….

Select a place to store the request on disk, and click Save.

Certificate Assistant generates the public and private keys and stores them in your keychain, while storing the matching certificate request on disk.

Figure 3-2 Observing public and private keys in Keychain Access

Upload the certificate request to the certificate authority (for example, to Apple using the developer portal, as part of the certificate generation flow).

Download the generated certificate (a file with a cer extension).

Open the certificate file by double clicking on it.

Keychain Access imports the certificate and associates it with the corresponding private key you created earlier.

Note: If the private key is not already in your keychain when you import the certificate, for example because you move to another development machine, you must export the private key from the original system using the Keychain Access app, and import it on the new system as a separate step. The private key is not part of the certificate. When you use Certificate Assistant to generate the certificate request, the one and only copy of the private key is the one Certificate Assistant placed in your keychain at that time.

Alternatively, you can create and self-sign a certificate using Certificate Assistant, and not involve a certificate authority. This can be useful during internal testing and development.

Open Applications > Utilities > Keychain Access.

From the Keychain Access menu, choose Certificate Assistant > Create a Certificate.

Fill in a name for the certificate. This name appears in the Keychain Access utility as the name of the certificate.

Choose Self Signed Root from the Identity Type pop-up menu.

Choose Code Signing from the Certificate Type pop-up menu.

Specify a serial number for the certificate.

Any number will do as long as you have no other certificate with the same name and serial number.

Accept the defaults for the rest of the dialogs.

Adding an Info.plist to Single-File Tools

Add an Info.plist file to your project.

Make sure the Info.plist file has at least the following keys:

As an example, Listing 3-1 gives the contents of the Info.plist file for the codesign command.

Listing 3-1 The Info.plist file contents for the codesign command

Signing Your Code Manually

Whether Xcode manages your signing identity or you set it up manually, Xcode normally signs code that you build using the codesign tool. Xcode does this as the final step in the build process, and again when exporting for distribution. In the unusual case that you sign your code manually, or to interrogate an app for details about its signature, you use the codesign command line tool directly. See the codesign man page for a complete enumeration of the options this tool takes.

What to Code Sign

You sign all the individual components of your app, leaving no gaps, including:

Nested code. First, you recursively sign all of the helpers, tools, libraries, frameworks, and other components that your app relies on, and that are bundled with your app. See Ensuring Proper Code Signatures for Nested Code for a discussion of how to properly embed and sign nested code in your app bundle. Also see Using Library Validation for additional information about verifying libraries as a matter of system policy.

Mach-O executables. The signing software applies individual signatures to each architectural component of a universal binary that represents the main executable of your app. These are independent, and usually only the native architecture on the end user’s system is verified. To apply the signature, the codesign utility adds the signature directly to the executable file.

When to Code Sign

You sign as the last step before shipping your product, after all development and testing are done. Making changes after you sign invalidates the signature. Consider a signed application bundle as a read-only entity. Also, because code that you sign with a distribution certificate bears your stamp of approval, avoid handing out signed code that is not final.

In practice, Xcode applies your signature when you export your app for distribution. Alternatively, you can run codesign at any time on any system running macOS 10.5 or later, provided you have access to the signing identity. You can for example include it as a step in custom Makefile scripts.

How to Code Sign Manually

Xcode normally signs on your behalf. You simply choose a signing identity in the General tab of a given target, and Xcode takes care of the details. This is usually the best option, because Xcode evolves with each new version to match changes in recommended code signing procedures and settings. Any customizations you introduce, on the other hand, require explicit maintenance.

Figure 3-7 Adding codesign flags using build settings in Xcode

In rare cases when you need to sign manually (or to interrogate an existing code signature, as described in Examining a Code Signature ), you use the codesign command directly, as described below. This is generally the option of last resort, but may be helpful in certain special cases, especially when trying to debug an issue. Note that your signing identity must be in a keychain for codesign commands to work.

Signing Code Manually

The value may be a bundle folder or a specific code binary. See What to Code Sign for more details.

If you have built your own certificate hierarchy (perhaps using Certificate Assistant—see About the Code Signing Identity ), and want to use your certificate’s anchor to form a designated requirement for your program:

Note: The requirement source language accepts either an SHA1 hash of a certificate (for example H»abcd. » ) or a path to the DER encoded certificate in a file. It does not currently accept a reference to the certificate in a keychain, so you have to export the certificate before executing this command.

Here are some other examples of requirements:

anchor apple – The code is signed by Apple.

anchor trusted – The anchor is trusted (for code signing) by the system.

certificate leaf = /path/to/certificate – The leaf (signing) certificate is the one specified.

certificate leaf = /path/to/certificate and identifier «com.mycorp.myprog» – The leaf certificate and program identifier are as specified.

Except for the explicit anchor trusted requirement, the system does not consult its trust settings database when verifying a code requirement. Therefore, as long as you don’t add this designated requirement to your code signature, the anchor certificate you use for signing your code does not have to be introduced to the user’s system for validation to succeed.

Adding Entitlements for Sandboxing Manually

For a list of entitlement keys that can appear in the entitlement property list, see Entitlement Key Reference. For more information about App Sandbox, read App Sandbox Design Guide.

Sharing a Designated Requirement

If your application consists of a main executable with one or more helper tools that work together, appearing to the user as a single app, you can make these pieces of code indistinguishable to code signing by giving them all the same designated requirement. In that case, all your program components have access to the same keychain items and validate as the same program. Do this only if the programs involved are truly meant to form a single entity, with no distinctions made.

Ensuring Proper Code Signatures for Nested Code

Starting in macOS 10.9, the code signing tool records nested code (such as frameworks or XPC services that you add to your app) in the embedding code’s resource envelope using the nested codes’s own code signature. This means that when a code signature is created for an item, all the nested code that item contains must already be signed correctly or the signing attempt fails. Xcode nests code like this by default, as long as all of the nested items exist as targets in your project, and your app’s build depends on these targets. Figure 3-8 shows an example of Xcode’s Build Phases panel for an XPC service called MyAppHelper properly nested in the MyApp app. Xcode begins the signing process at the deepest level of hierarchy (which in this case is the MyAppHelper service), working outward, and signing your top level app bundle as the final step.

Figure 3-8 Target dependencies for nested code

Top content directory of the bundle

Helper apps and tools

Plug-ins, both loadable and extensions

Helper apps and tools

Installable login items

Privileged helper tools installed by the ServiceManagement framework

The system expects these locations to contain only code. When evaluating an app bundle’s code signature, the system will reject arbitrary data files found in these locations because they’re unsigned. Conversely, the code signing machinery considers anything not in one of these directories, including code, to be a resource. Any code not in one of these directories is therefore sealed twice: once as code, and once as a resource in the outer signature. This wastes both signing and verification time and storage space. Also, this can break the outer signature of apps that use their own update mechanisms to replace nested code. If this nested code is being treated as a resource, the outer signature doesn’t know that this nested content is actually code.

The code signing machinery performs some framework checks specifically on frameworks that are nested within other code. It’s possible that signing a framework will succeed, but the result fails to validate when placed into another bundle’s Frameworks directory. Make sure the framework is structured correctly per the requirements above.

If signing or validation using the codesign command fails due to problems with nested code, the command outputs an additional line:

This output indicates which nested code caused the problem. Always look for this line to correctly interpret a code signing failure. If Xcode produces a code signing error during distribution signing, and you have nested code, this is something to check for.

Using Library Validation

Starting in iOS 8 and macOS 10.10, the system offers library validation as a policy for the dynamic libraries that a process links against. The policy is simple: A program may link against any library with the same team identifier in its code signature as the main executable, or with any Apple system library. Requests to link against other libraries are denied.

In iOS, library validation is always enabled for all apps. There is nothing you need to do to opt in. In macOS, you may opt in to library validation by passing the library flag to the codesign tool when signing manually:

Figure 3-9 Enabling library validation using build settings in Xcode

To avoid signing errors when using library validation in your project, create embedded frameworks as Xcode targets of the same project, and build with standard settings. This ensures that the main executable and all frameworks are signed with the same certificate, and thus have the same team identifier. If you forget to sign frameworks that are built externally to the project and later copied into the bundle, library validation fails.

Signing Installer Packages

As with signed code, when you create a flat-file installation package, any modification after signing invalidates the signature.

Note: Bundle-style installer packages are no longer supported.

Signing Disk Images

Beginning in macOS 10.11.5, you can apply a code signature to read-only, compressed disk images that you use to distribute content. This is the recommended alternative to the deprecated xip file format, which is a signed archive you create with the xip command line utility.

Xcode does not handle signing disk images. Instead, use the command line codesign tool to do this manually:

When you sign your app with a Developer ID and distribute it using a disk image, it is possible to package additional unsigned code, such as dynamic libraries or scripts, together with the signed app bundle on the same disk image. If your app loads this extra content at runtime using a file system path relative to its own bundle, you have introduced a security risk. Because the extra code is outside the app bundle, and thus not covered by the app’s code signature, you can’t be certain that the extra content is intact. This is known as the repackaging problem because a bad actor can repackage your app bundle with a different, potentially malicious version of the external resources, and distribute the altered disk image as if it came from you.

To combat this problem, beginning in macOS 10.12, when an app is launched from a read-only disk image, the operating system employs Gatekeeper path randomization. The system copies the app to a random location in the file system before executing it, invalidating any relative paths that the app uses to access unprotected content outside its own app bundle.

You can bypass path randomization by code signing your disk image before you distribute it. When launching an app from a code-signed disk image, Gatekeeper disables path randomization because all the contents of the disk image are covered by a code signature.

Note: Whether or not Gatekeeper employs path randomization, it still evaluates an app and its code signature on first launch as usual. In other words, even when you distribute an app using a signed disk image, you still separately sign your app bundle in the usual way, before adding it to the disk image.

Examining a Code Signature

Whether you code sign manually or Xcode does it for you, when you want to test the integrity of signed code or evaluate the way in which the system is going to treat signed code, you use the codesign and spctl command line tools.

Using codesign to Investigate a Code Signature

If you pass a number rather than a path to the verify option, codesign takes the number to be the process ID (pid) of a running process, and performs dynamic validation instead.

Using spctl to Test a Code Signature Against System Policies

After you have produced your final deliverable, but before you ship it, you can use the spctl(8) tool to test your code signatures against various system policies that the user may set. Because the tool evaluates against the policies on the local machine, the outcome is affected by the settings in the Security preferences pane, and can further be modified by parental controls, remote management, and so on. Conversely, changes made with spctl (such as adding or disabling rules) affect future Gatekeeper judgments directly.

The basic syntax for code signing assessment is shown below:

This prints the following output:

To approve a program (exactly as if done through a user prompt), type:

Note that this removes all rules that match the label, which means that it is a handy way to clean up after testing. You can also temporarily suspend your rules by typing:

and reenable them later by typing:

The resulting list of rules might look like this:

Notice that the list above includes a number of predefined rules that describe the handling of certain classes of code. For example, rule 5 captures all applications signed by a Developer ID. You can disable those applications by typing:

This command tells the system to no longer allow execution of any Developer ID-signed applications that the user has not previously run. This is exactly what happens when you use the preference UI to switch to «Mac App Store only».

Each rule in the list has a unique number that can be used to address it. For example, if you type:

you might get a list of rules that looks like this:

Notice that there are separate rules for execution (5) and installation (6), and you can enable and disable them separately. For example, to enable installation of new applications signed with a Developer ID, you can type:

Finally, spctl allows you to enable or disable the security assessment policy subsystem.

Checking Gatekeeper Conformance

It’s a good idea to test your app for Gatekeeper conformance before you ship, especially if you sign your app with a Developer ID and distribute by some means other than the Mac App Store, such as through a website.

Gatekeeper is a configurable system facility that examines files that you download to your Mac, for example from a website or in an email attachment. It applies rules to decide whether to allow or reject an attempt to open an item for the first time on a given system. When deciding whether to allow an app to run, Gatekeeper uses the app’s code signature to test the integrity and authorship of the app. By default, Gatekeeper only allows apps that have an intact signature, and that are downloaded from the Mac App Store or are signed with a Developer ID.

In addition to this primary tactic, Gatekeeper does the following:

Beginning with macOS 10.10.4, Gatekeeper verifies that no libraries are loaded from outside an app bundle. If an app uses @rpath or an absolute path to link to a dynamic library outside of the app, Gatekeeper rejects the app. This restriction applies to the app’s main executable and any other executable in the bundle, including libraries. This restriction applies even if the path does not exist (which normally causes the dynamic linker to fall back to a library inside the bundle). The error will appear in the system log, with a message like the following for an app MyApp.app trying to link against the library libLibrary.dylib in the nonstandard location /foo :

Beginning with macOS 10.11, Gatekeeper rejects code signed with signatures that don’t cover the entire app bundle. This should not affect anyone using normal build tools. Gatekeeper also rejects apps containing symbolic links that:

Point to nowhere.

Point to places that are legitimately excluded from the app’s signature.

A nested bundle may contain symlinks that point into the enclosing bundle.

Testing Conformance with Command Line Tools

To get a sense of whether your app conforms to Gatekeeper policies when you distribute with Developer ID, you can use the following codesign command to mimic what Gatekeeper does:

If your app is signed properly, the output looks like this:

Alternately, the spctl utility is actually a command-line interface to the same security assessment policy subsystem that Gatekeeper uses. Like Gatekeeper, spctl only accepts Developer ID signed apps and apps downloaded from the Mac App Store by default. Run spctl on your app like this:

This is the output if your app’s signature is accepted:

Testing Conformance Explicitly

The codesign and spctl tools give a good sense of how Gatekeeper will respond to your app, but they are not exhaustive. For example, they do not test for the condition that libraries be loaded from inside the bundle or from one of the standard system locations. Therefore, it is best to actually invoke Gatekeeper as a final test before shipping. To do this:

Package your app the way you ship it, such as in a disk image.

Download your app from its website, mail it to yourself, or send it to yourself using AirDrop or Message. This quarantines the app. This is necessary to trigger the Gatekeeper check as Gatekeeper only checks quarantined files the first time they’re opened.

Drag-install your app to the /Applications folder and launch it.

If there is no dialog at all, you missed a step. Check the instructions and repeat the test.

If you see the dialog with a message that the app you are trying to open is from the Internet, and providing an Open button, the test succeeded.

If you get any other complaint, your signature is broken.

Using Hash Agility

Beginning in macOS 10.11.5, stronger cryptographic hashing is available to both create and evaluate code signatures. When you build and code sign using macOS 10.11.5 or later, the code signing machinery uses the improved hashing to create a code signature. There is nothing you need to do to adopt this behavior. At the same time, to maintain backward compatibility, the system includes a legacy code signature alongside the modern one, in a way that works transparently with older systems.

Similarly, during code signature evaluation on macOS 10.11.5 or later, the system uses the stronger signature if it is available, but still interprets older signatures if necessary. As with signing, there is nothing you need to do to adopt the improved hashing during code signature evaluation. Together, these are referred to as hash agility.

Note: When you set the deployment target in Xcode build settings to 10.12 or higher, the code signing machinery generates only the modern code signature for Mach-O binaries. A binary executable is always unsuitable for systems older than the specified deployment target, but in this case, older systems also fail to interpret the code signature.

Shipping and Updating Your Product

Maintaining the integrity of a code signature requires the signed code installed on the user’s system to be identical to the code that you signed. It does not matter how you package, deliver, or install your product as long as you don’t introduce any changes into the product. Compression, encoding, and encrypting the code are all fine because decompression, decoding, and decryption reverse these processes exactly. You can even use binary patching, because that process updates both the code and the embedded signature simultaneously. You can use any installer you like, as long as it doesn’t write anything into the product as it installs it. Drag-installs are fine as well. As long as the final product on the user’s system is bit-for-bit identical to the signed code you produced, the signature remains intact.

When you have qualified a new version of your product, sign it just as you signed the previous version, with the same identifier and the same designated requirement. The user’s system considers the new version of your product to be the same program as the previous version. For example, Keychain Services does not distinguish older and newer versions of your program as long as both are signed and the unique Identifier remains constant.

Copyright © 2016 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2016-09-13

Comments

IkhwanSI13 commented Jun 19, 2020

I have run my apps at iOS, and all work as my expectation and I tried to archive to the App Store. But, I get this error in my email. I tried to look for it but only found this error in Xamarin and Xcode with old versions.

My flutter doctor:

The text was updated successfully, but these errors were encountered:

brorhb commented Jun 19, 2020 •

TBH, I suspect someone were a bit quick on the trigger to depricate signing from Xcode 11.5 and we might get 11.6 on moday (WWDC week). Similar things have happend before

giandifra commented Jun 19, 2020

blackcodefr commented Jun 19, 2020

Had the same issue with a fully native iOS app (that doesn’t use Flutter at all). I simply cleaned the project, made a new build and that one went through without any issue. Seems like an Xcode / Apple bug.

giandifra commented Jun 19, 2020

@blackcodefr it’s true, i cleaned the project, rebuild and it’s ok now.

blackcodefr commented Jun 19, 2020

FYI. I made more builds afterwards and got the same error. Then sent 2 news builds (for the same bundle id) and didn’t get it. Something weird is happening at Apple.

jmagman commented Jun 19, 2020 •

I made a new non-Flutter Xcode project in 11.6 beta 11N700h, set the iOS deployment to 9.0 to get the Swift libraries embedded, and libswiftCore.dylib is signed with my team identifier:

It looks the same as my Flutter app, except for the Signed Time timestamp.

You can see your team identifier with:

I simply cleaned the project, made a new build and that one went through without any issue.

That means a flutter clean might «fix» it, since that runs a clean on the workspace.

kjawadDeveloper commented Apr 5, 2021

jmagman commented Apr 5, 2021

kjawadDeveloper commented Apr 5, 2021

[!] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.2.4)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin installed
• Dart plugin version 202.8070

[!] Connected device
! No devices available

dedvalson commented Apr 6, 2021

I am seeing this as well on Stable channel.

Unable to install «iPad.app»

I have an iOS project that was created a couple Xcode versions ago bundling some XCFrameworks.

As of recently (still with Xcode 13.4.1 (13F100)) the app won’t launch anymore on actual devices with the dreaded Unable to install «XYZ» error.

I have several other projects using one or other of the XCFrameworks, all using the same team and code signing options, and in any of the other apps still work fine on my test device.

I’ve compared settings between the apps that launch and the one that doesn’t but I can’t spot any difference that could cause an issue..

Is there any way to track down the specific problem with this app?
This is the detailed output when launching on device fails:

And this is the output of codesign on the app:

Any hints appreciated.

Replies

I don’t have any specific hints for you, but I do have some suggestions:

Try restarted both your Mac and the device.

Try deleting the app from the device and then re-installing from scratch.

Create a new project with the same App ID. Does that also fail? If not, that tells you that your project is the issue.

Immediately after the failure, trigger a sysdiagnose log. Then grab the log, unpack it, and look in the system log for the 0xE8008029 error code. Do you see anything meaningful proximate to that?

For system log hints and tips, see Your Friend the System Log.

The code signature version is no longer supported #4045

Comments

himshikhar-sc commented Jan 25, 2022

Able to build the project but not able to run on device. Project includes swift packages, pods and few static frameworks as well.

Screenshots

Complete error

System Information
macOS Version 12.0 (Build 21A344)
Xcode 13.0 (19234) (Build 13A233)

The text was updated successfully, but these errors were encountered:

fortmarek commented Jan 25, 2022

I am sorry to hear you are having problems, however, we’ll need more information to debug this. Creating a reproducible example would be best but any additional info would be helpful here.

himshikhar-sc commented Jan 25, 2022

Won’t be able to share a reproducible snippet but can you please share what might possibly cause it? The project works fine without using tuist but after implementing tuist this comes up every time.

luispadron commented Jan 26, 2022

We can’t possibly give you a cause when there is no real information to go off of. I recommend reading the docs https://docs.tuist.io to understand if there is any configuration missing in your setup.

We’re going to close this since we can’t do much more here, feel free to re-open if you are able to provide more info

Sideloading iOS Apps No Longer Possible on M1 Macs

macsorcery

macrumors 6502a

Limeybasturd

macrumors demi-goddess

Limeybasturd

macrumors demi-goddess

Leon88

macrumors regular

seek3r

macrumors 65816

Leon88

macrumors regular

macrumors regular

sofakng

macrumors 6502

I’ve installed 11.3 but something is different.

I can re-install IPA files that I’ve previously transferred from my iPhone. I can also run these side-loaded apps without any problem.

However, I just transferred some new IPAs using iMazing (and Apple Configurator 2) but it errors during install:

«This app cannot be installed because it’s integrity could not be verified.»

The Console (system logs) show the following error:

«The code signature version is no longer supported»

Apple_Robert

Contributor

I’ve installed 11.3 but something is different.

I can re-install IPA files that I’ve previously transferred from my iPhone. I can also run these side-loaded apps without any problem.

However, I just transferred some new IPAs using iMazing (and Apple Configurator 2) but it errors during install:

«This app cannot be installed because it’s integrity could not be verified.»

The Console (system logs) show the following error:

«The code signature version is no longer supported»

Unable to install inhouse iPA files on iOS 15 (same app works on iOS 14) #139

Comments

rpayne381 commented Jul 22, 2021

Anyone have a fix or a pull request for this issue yet? testing on iOS 15 Beta 3

ERROR: Install failed. Got error «ApplicationVerificationFailed» with code 0xe8008029: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.95tGvj/extracted/Payload/MYAPP.app : 0xe8008029 (The code signature version is no longer supported.) 14:39:13 installation_proxy.c:192 instproxy_lock(): Locked 14:39:13 installation_proxy.c:427 instproxy_receive_status_loop_thread(): done, cleaning up. 14:39:13 installation_proxy.c:203 instproxy_unlock(): Unlocked»>

The text was updated successfully, but these errors were encountered:

nikias commented Jul 24, 2021

Well as you can see it clearly tells you the problem: The code signature version is no longer supported.
You have to sign it with a newer codesign I guess.

Application verification fails on ios 15 with an older version of Xcode about robovm HOT 7 CLOSED

Issue details

Starting with iOS 15, the system checks a new signature format (DER) so that applications can run on current OS.
For lower versions of XCode 12.5 it is necessary to include the generate-entitlement-der flag.

Robovm must sign with generate-entitlement-der flag for older XCode versions.

Reproduction steps/code

Build and run a app in real device with iOS15 in Xcode 12.4

Robovm output

ideviceinstaller output

Configuration

Build Tools:

Versions:

Build Targets:

References

Comments (7)

check your certificate in keychain access, I think it is not trusted

avazquezdev commented on October 22, 2021

check your certificate in keychain access, I think it is not trusted
Hi, I check my certificate and I did not find any problems and it is a valid certificate.
Do you suggest any other test?

bachtrong43 commented on October 22, 2021

Try to update your xcode, I think xcode 12.4 does not support ios 15

guillerodriguez commented on October 22, 2021

Try to update your xcode, I think xcode 12.4 does not support ios 15

You clearly haven’t even tried to read the original issue report? The OP is saying that starting with iOS 15 the signature format has changed and that for XCode dkimitsa commented on October 22, 2021 2

hi All, I will add and test it probably today

dkimitsa commented on October 23, 2021

please report if there is any issue with it especially in projects that contains another frameworks/extension

avazquezdev commented on October 28, 2021

Thanks dkimitsa! The problem is solve.

please report if there is any issue with it especially in projects that contains another frameworks/extension

No problem, If I found any issue more, I will report.

Related Issues (20)

Recommend Projects

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Comments

jelenalecic commented Nov 14, 2018 •

when trying to run app on any real device.

On simulator, it all works as expected.

On Android side, everything goes smoothly, also!

Steps to Reproduce

to BuildPhases Run Script
5. Make simple button and onClick listener to open FlutterViewController
6. Build successful, after I set:

without this, i get a linking error.

Signing is set to automatically

Device that I’m currently using is an iphone 8, iOS 12.1

I believe it must be some binding issue with podhelper.rb, ‘cos i have to switch off manually Enable Bitcode, to be able to build the app.

I have tried everything I could think of. Please help 🙂
Thanks!

The text was updated successfully, but these errors were encountered:

kangwang1988 commented Nov 14, 2018

@jelenacarnegie
Yes, as Flutter.framework doesn’t contain bitcode, you have to disable the bitcode setting for the target’s buildsetting.

kangwang1988 commented Nov 14, 2018

Besides, when you specified a DEVELOPMENT_TEAM in your build_settings, flutter will respect it.
If you specified one, can you make sure that the code-signing works fine from Xcode using your personal team?

jelenalecic commented Nov 14, 2018

@kangwang1988
It works fine for other apps(without flutter module).
I haven’t done anything different than usual.

dnfield commented Nov 14, 2018

The process should have automatically disabled bitcode for you, but probably doesn’t handle some situations.

Alternatively go through all your targets and make sure that Iis set. Right now that seems like your primary issue. If that is done and you’re still having signing issues there may be another issue, but hopefully you get better output once bitcode is disabled for all targets.

jelenalecic commented Nov 14, 2018

I’ve disabled it in Xcode

and in Android Studio in files:

but still the same :/

dnfield commented Nov 14, 2018

jelenalecic commented Nov 14, 2018

I’m sorry, but I don’t know how to get those values.

I see them there(. flutter/packages/flutter_tools/bin/xcode_backend.sh):

. but I’m not sure how to debug this file, cos it’s outside of my ios project.

I’m an android developer and I would probably need some help from my iOS colleagues 🙂

Invalid signature format on watchOS8 with watchos_application/watchos_extension (no issues on watchOS7) #1225

Comments

rsahara commented Aug 24, 2021 •

The issue

We’re getting an error («failed to install») when we try to install our watch app built with watchos_application/watchos_extension with an enterprise account, on watchOS8.

In the iPhone’s logs, we have this line during the error:

The same app can be installed without problems on watchOS7.

Some investigations

I found a discussion about this error: https://developer.apple.com/forums/thread/682775?page=2.
This error should only happen when an app is built on Catarina or older OS, but our app was built on Big Sur.

Some workarounds

Re-signing

Passing the option to codesign

to where we’re using watchos_extension ( codesignopts available) and watchos_application (with a few changes to hardcode codesignopts ), the resulting IPA was OK.

The text was updated successfully, but these errors were encountered:

after resigning app is not installing [Install: VerifyingApplication (40%)ERROR: Install failed. Got error «ApplicationVerificationFailed» with code 0xe8008029: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.PzILa6/extracted/Payload/Adv.app : 0xe8008029 (The code signature version is no longer supported.)] #19688

Comments

rohitsainier commented Dec 9, 2021 •

The text was updated successfully, but these errors were encountered:

fastlane-bot commented Dec 9, 2021

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

fastlane-bot commented Jan 15, 2022

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

fastlane-bot commented Feb 14, 2022

This issue will be auto-closed because there hasn’t been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

The code signature version is no longer supported

I am integrating the latest TalkableSDK.xcframework into our build (1.4.12). When I build and run on simulator, it works fine. However, when I try to install to an iOS device, I get the following «code signature version is no longer supported» version. I am building using Xcode Version 13.4 (13F17a) on a M1 MacBook Pro running MacOS Monterey (macOS 12.4) and trying to install to an iPhone 11 running iOS 15.5.

Here is the error:

This is blocking completely our usage of Talkable in our app.

Created at 3 weeks ago

More on this. According to this Apple documentation, I ran the codesign utility on the ios-arm64_armv7 embedded framework:

and I see the output:

Note the following line from above:

According to Apple’s documentation above:

Look in the output for a string such as CodeDirectory v=20500. For any value of v less than 20400, you need to re-sign your app.

So this TalkableSDK.xcframework is unusable in Xcode 13 and above when trying to install on iOS 15+ devices.

Created at 2 months ago

Hi @ehyche,
Thanks so much for the detailed explanation of the issue!
We’re currently on it and will let you know once have updates.
Sorry for the inconvenience.

Created at 2 months ago

@ehyche Looks like we found a way to resolve this: please change «Embed» setting to «Do Not Embed» for Talkable framework:

Broken AdHoc builds, incorrect code signing #270

Comments

AlexanderKhudyakov commented May 23, 2016 •

Hello, I’m trying to build adhoc, but no luck so far. «gradle archive package» does the job without any errors, but output *.ipa won’t install on any of my devices.
Error message on install is
May 23 19:39:31 iPad atc[864] : 0x16e58f000 __MobileInstallationInstallForLaunchServices_block_invoke222: Returned error Error Domain=MIInstallerErrorDomain Code=13 «Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.KJ5SAH/extracted/Payload/MyProject.app : 0xe8008016 (The executable was signed with invalid entitlements.)» UserInfo=

My script looks like this:

So, is it a bug of some kind, or I’m doing something wrong?

The text was updated successfully, but these errors were encountered:

Missing Info.plist in MapboxEvents.framework error with CocoaPods 1.10.0 & Xcode 12.2. #555

Comments

mkieselmann commented Nov 21, 2020 •

Missing Info.plist in MapboxEvents.framework error when installing Mapbox iOS SDK with CocoaPods 1.10.0 & Xcode 12.2.

Steps to reproduce

Expected behavior

App launches properly with Mapbox iOS SDK linked.

Actual behavior

Before the app actually launches Xcode shows the error of a missing Info.plist:

Removing use frameworks! from the Podfile as suggested here does not work either. Then, Mapbox.framework cannot find the statically linked MapboxEvents.framework and dynamic linking fails at app start.

Configuration

Mapbox SDK versions: 6.3.0, 6.2.2
iOS/macOS versions: 14.2
Device/simulator models: any
Xcode version: 12.2
CocoaPods version: 1.10.0

The text was updated successfully, but these errors were encountered:

mkieselmann commented Nov 21, 2020

Could be related to #503

mkieselmann commented Nov 21, 2020 •

mkieselmann commented Nov 22, 2020 •

Using a fixed version of MapboxMobileEvents doesn’t work either. The problem is probably related to the new Cocoapods version that doesn’t need use frameworks! anymore. By default MapboxMobileEvents is linked statically while Mapbox.framework links it dynamically.

I’ve now remove Mapbox from my Podfile and installed the prebuild Frameworks manually.

seanclin commented Nov 23, 2020

I believe this has something to do with XCode 12.2, I am able to build fine on 12.1 but my coworker is not able to build with 12.2

Hless commented May 31, 2021 •

I just ran into the same issue and the info.plist was literally missing from MapboxMobileEvents/Support Files Pod directory. I checked with co-workers who had the same XCode version, same OS, same CocoaPods version same lockfile, and they had the Info.plist. I checked our CI server (which does a clean reinstall with the same OS/CocoaPods/XCode versions too), also had the Info.plist.

So I Copied the Info.plist from a co-workers system to the Support Files directory on my system and added it in the settings of the MapboxMobileEvents target and everything started working again.

I’m at a complete loss why my system does not download this info.plist. It’s the only file missing on my system, and cleaning derived data, the Pods directory and all other caches I can think of does not fix the problem. I simply don’t understand why this is happening.

Hless commented May 31, 2021 •

Still not sure why this happens, but I suspect some problem with CocoaPods’ caching system.

Edit
Versions for those wondering:
XCode 12.5
CocoaPods 1.10.1
MacOS Big Sur
iOS 14.5.1
MapBox SDK 6.3.0

ghadeeraqraa1992 commented Jun 20, 2021

Hless commented Jun 21, 2021

@ghadeeraqraa1992 Have you tried my solution? If you have this problem locally, you should remove all pod caches you can find ($HOME/Library/Caches/CocoaPods most notably), your Pods directory inside the project etc and reinitiate. It fixed the problem for me. The info.plist was literally missing in the Support Files of MapboxMobileEvents.

ghadeeraqraa1992 commented Jun 21, 2021

I tried the below steps :

ghadeeraqraa1992 commented Jun 21, 2021

@ghadeeraqraa1992 Have you tried my solution? If you have this problem locally, you should remove all pod caches you can find ($HOME/Library/Caches/CocoaPods most notably), your Pods directory inside the project etc and reinitiate. It fixed the problem for me. The info.plist was literally missing in the Support Files of MapboxMobileEvents.

I got the same issue

Could not install at this time. Failed to load Info.plist from bundle at path /Users/Ghadeer/Library/Developer/CoreSimulator/Devices/77062086-4859-4E6A-A712-B029E9DEF6C7/data/Library/Caches/com.apple.mobile.installd.staging/temp.sFhRhc/extracted/Payload/myApp.app/Frameworks/MapboxMobileEvents.framework; Extra info about plist: ACL=

Hless commented Jun 21, 2021 •

> 6.3′ in Podfile), and removed all related cache files (pods dir, pod caches, xcode build caches, derived files, possibly even podfile.lock), you should be able to resolve it. I suspect you could be missing some steps here.

Edit: Also, while it is my belief that it’s undrelated, I also installed all homebrew, apple system updates and rebooted the system before reinstalling my pods. You never know, always worth a shot

ghadeeraqraa1992 commented Jun 21, 2021

> 6.3′ in Podfile), and removed all related cache files (pods dir, pod caches, xcode build caches, derived files, possibly even podfile.lock), you should be able to resolve it. I suspect you could be missing some steps here.

Edit: Also, while it is my belief that it’s undrelated, I also installed all homebrew, apple system updates and rebooted the system before reinstalling my pods. You never know, always worth a shot

Hless commented Jun 21, 2021

Not the literal podfile since I have some custom stuff in there, but something similar to:

@react-native-mapbox-gl/maps version 8.2.0-beta2
RN 0.64

ghadeeraqraa1992 commented Jun 21, 2021

Not the literal podfile since I have some custom stuff in there, but something similar to:

@react-native-mapbox-gl/maps version 8.2.0-beta2
RN 0.64

Hless commented Jun 21, 2021

Not likely related to the problem you are having, which I still believe is a caching problem. If I were you I would try to verify if the correct MapboxMobileEvents pod is loaded, the one where the Info.plist actually exists inside the MapboxMobileEvents/Support Files directory. As long as it doesn’t you will keep having the problem. I can’t help you any further, so I hope you can figure it out from here. Best of luck!

Hless commented Jun 21, 2021

Also, you can try to put the Info.plist there manually as I did, and verify if that fixes the problem. Then you actually have something to go on.

I’m talking about this one:

ghadeeraqraa1992 commented Jun 22, 2021

Also, you can try to put the Info.plist there manually as I did, and verify if that fixes the problem. Then you actually have something to go on.

I’m talking about this one:

there is no Info.plist

I tried to add it manually but this doesn’t fix the issue

samuelcai-chancetop commented Jul 26, 2021

I had same issue, and I tried @Hless ‘s solution, but only did some of it: did a repo update, did a pod deintegrate followed by pod install.
It successes for the first time, but several hours later the info.plist is missing again (I can’t remember what I did), and I tried same solution again, not working.
Last Friday the problem was still there, but today (this Monday), I did a regular «pod install», and found the info.plist was there. So I think it’s related to cocoapod (especially cache). But I still don’t know the root cause.

Hless commented Jul 26, 2021

@samuelcai-chancetop Glad to see that you got it working, albeit partially. I’m still very much confused why this happens. It hasn’t happened to me for a long time now, nor did any of our CI tasks ever fail because of this issue. So I agree that this must be some sort of caching issue. Perhaps if you do all the steps it will fully fix it for you? I did verify the Pods cache when I first tried to fix it, and the info.plist was missing there too. Hence these suggestions.

acoulon99 commented Nov 28, 2021 •

I’m running into this similar issue from a React Native project. I’ve tried all suggestions including clearing the cocoapod cache, reinstalling cocoapods, clearing all build directories, and creating a new project from scratch. Going to keep digging and post anything definitive I find.

IBDesignables, no suitable image found, required code signature missing

Aframework is a placeholder for multiple Pod frameworks I have as dependencies. These worked fine before I modified xcassets.

I tried everything I could find related to this but I’ve gotten nowhere: Cleaned Derived Data, ran clean/build, removed all XCode cache folders, reinstalled XCode entirely, Refresh all views etc. It compiles and runs fine, everything works in the app (and no images or resources are missing), but all my Storyboards are blank (all white), which makes it pretty hard to work.

EDIT: I Completely reinstalled OSX and cloned the repo from Git from a working configuration. No change. This must be something other than the xcassets-theory, because even if I check out commits from weeks ago (where I know for sure this wasn’t a problem) I still get the error. Maybe something was updated by Apple between now and the last time it worked. I’ve given up and moved on for now. I’ll just click through the views in the explorer on the left side instead of inside the storyboard. Hopefully someone somewhere figures this out at some point.

Can’t install on device with Xcode 13.2 RC about Parse-SDK-iOS-OSX HOT 6 CLOSED

New Issue Checklist

Issue Description

Steps to reproduce

Actual Outcome

Expected Outcome

Environment

Comments (6)

Thanks for opening this issue!

JuLink commented on January 14, 2022

MaartenZonneveld commented on February 11, 2022

I haven’t encountered this problem anymore.
I’m not sure if it was resolved in Xcode 13.2.1 (up from 13.2 RC) or I initially incorrectly embedded the Parse framework in our app, thinking it was a dynamic framework, while it is actually static.

drdaz commented on February 12, 2022

It’s pretty awesome when things fix themselves.

@JuLink can you confirm?

JuLink commented on February 12, 2022

I’m not sure, I did not had to update again since the last time.

But I recall that it was not an issue with Parse SDK, because during my debugging of the issue I had remove all traces of the Parse SDK from my project configuration, comment all code related to Parse and still had the issue during deploy on device.
That’s why I was thinking that the issue was from the Facebook SDK (the pre-built binaries) because it’s an old version and I still had the Facebook dependencies in the project. Building with the no-use-binaries fixed the issue at the time so I did not look any further.

Anyway I’m glad the issue seems to be magically fixed 😅

drdaz commented on March 9, 2022

Closing this. You’re welcome to reopen if it comes back.

Related Issues (20)

Recommend Projects

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Invalid Code Signature Error on Electron App After Signing with Hardened Runtime

I’ve been running into issues with codesigning my Electron application with hardened runtime. The application verifies as being properly codesigned using codesign verify, passes notarization and is stapled properly, passes gatekeeper checks using spctl, and also passes Apple’s check-signature tool.

The application itself isn’t built with xcode but rather by using Electron’s prebuilt binaries and then moving our javascript, css, and other non-code resources into the respective folder (.app/Content/Resources/app). I codesign via commandline using xcode 10.1 on Mac OS X 10.14.1.

I’ve tried reducing the application down to the bare Electron startup, but it still fails.

Redacted Crash Report Snippet:

Replies

The problem here is that notarisation requires the hardened runtime and the hardened runtime, by default, prevents apps from generating code on the fly. The backtrace here strongly suggests that your app is crashing because the V8 JavaScript engine is doing just that.

The best way to resolve such issues depends on the exact behaviour of the third-party tools in question. For more background on this, see this thread.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

As a followup, I have also built an Electron app from the ground up using their prebuilt binaries and then dropping in their Hello World app (https://electronjs.org/docs/tutorial/first-app) verbatim into the right folder. This also passes every codesign verification as well as gatekeeper and notarization checks however it fials with the exact same error despite being passed in the following entitlements:

I’m sorry but I’ve reached the limits of the help I can provide you. DTS’s role here at Apple is to support Apple’s APIs and tools. We do not support third-party tools. If you have questions about how to use such tools, you must escalate those with your tool’s vendor.

If your tools vendor has questions about how their tool interacts with the hardened runtime, I’m happy to help them. They can post here if they want, but it’d probably be better to open a DTS tech support incident. Keep in mind, however, that DTS will only accept such questions if they come from the tools vendor [1].

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

[1] In the case of an open source project, this translates to someone who is familiar with the code and can make changes to it.

The code signature version is no longer supported

Questions : The code signature version is no longer supported

An app signed with a codesign version anycodings_ios provided on an older macOS, like Catalina anycodings_ios (10.15) will not run on iOS 15 because the anycodings_ios lastest version you can install is Xcode anycodings_ios 12.4.

Xcode 12.5 seems to change the behavior of anycodings_ios codesigning. When installing you get the anycodings_ios error message:

The code signature version is no longer anycodings_ios supported

Is there a workaround?

Answers 1 : of The code signature version is no longer supported

If signing through Xcode, you can add anycodings_code-signing this flag to the OTHER_CODE_SIGN_FLAGS anycodings_code-signing setting in the Build Settings tab.

If codesigning at the command-line:

The source of this information was the anycodings_code-signing Apple Forum thread and the answer from anycodings_code-signing Matt Eaton in DTS at Apple.

In the Xcode 12.5 Release Notes there is anycodings_code-signing also a reference to the new signature anycodings_code-signing format. However, it seems the anycodings_code-signing information is not entirely correct.

Answers 2 : of The code signature version is no longer supported

Here are some visual directions to anycodings_code-signing @CameronLowellPalmer’s answer.

I got the steps from @WayneHenderson’s anycodings_code-signing comment underneath the accepted answer.

The most important thing is step 4, make anycodings_code-signing sure to select All or you won’t find the anycodings_code-signing Other Code Signing Flags options.

For step 5 just enter Other Code Signing anycodings_code-signing Flags into the search container.

Answers 3 : of The code signature version is no longer supported

Answers 4 : of The code signature version is no longer supported

Answers 5 : of The code signature version is no longer supported

After testing all solutions, Only one anycodings_code-signing worked for me. Because XCode adds sign anycodings_code-signing signature automatically when you add anycodings_code-signing Framework, Any Framework that needs to anycodings_code-signing Embed & Sign should remove, and add anycodings_code-signing again. Xcode will add the new sign anycodings_code-signing signature automatically.

Now clean and run your app on your anycodings_code-signing device.

Answers 6 : of The code signature version is no longer supported

I want to share my solution. This worked anycodings_code-signing for me using XCode 12.3, macOS Catalina, anycodings_code-signing and tested using Adhoc distribution.

Build, archive, export ipa as usual anycodings_code-signing using XCode.

Now you have the IPA file, then rename anycodings_code-signing it to zip extension. (make a backup if anycodings_code-signing needed)

Extract it. There should be a Payload anycodings_code-signing folder.

Open terminal, cd to your IPA directory, anycodings_code-signing then run command:

CERTIFICATE_NAME is your certificate anycodings_code-signing name located in keychain. It maybe looks anycodings_code-signing like this: Apple Distribution: XCompany anycodings_code-signing (XXXXXX)

This warning showed up, I ignored it.

Then run zip command:

Done. You can redistribute the new IPA.

Answers 7 : of The code signature version is no longer supported

Just my two cents.

Output example log:

Some additional tips.

After the ipa zip archive creation, you anycodings_code-signing can use the Gem ipa_analyzer anycodings_code-signing (https://github.com/bitrise-io/ipa_analyzer) anycodings_code-signing to verify if the app is correctly anycodings_code-signing signed:

As additional references about this anycodings_code-signing issue, you can read also this Apple anycodings_code-signing documentation page and this Apple forum anycodings_code-signing post.

Answers 8 : of The code signature version is no longer supported

I have spent 2 days to find this issue, anycodings_code-signing Finally i got the solution here from the anycodings_code-signing person Lance Samaria. I would like to anycodings_code-signing share it.

Also I renewed Provisioning Profile and anycodings_code-signing IOS Distribution Certificates.

Now Clean Build Folder and Run Your anycodings_code-signing Project.

Thank you so Much for Lance Samaria

Answers 9 : of The code signature version is no longer supported

Answers 10 : of The code signature version is no longer supported

Sometimes, like in my case, it’s solved anycodings_code-signing just by doing a clean build folder:

Or by using ⌘ + ⇧ anycodings_code-signing + K

Code signature (codesign) fail on arm compiled PyInstaller Mach-O

I’ve used PyInstaller to create an arm mach-o of a «hello world» python file. I then tried to sign the file using codesign and got the following error:

When I create an x86_64 mach-o using the same method the codesign works without any issues.

I’m using an arm64 only python 3.9 and PyInstaller version 4.3

I’ve tried codesigning on both M1 and intel, and codesigning a «hello world» compiled from C file with gcc works.
Also, I’ve tried looking at the file compiled with PyInstaller using otool and haven’t seen any issues.

Replies

This is something you should escalate via the support channel for the third-party tool you’re using. If the tool’s author needs help getting this to work, they can open a thread here on DevForums or, better yet, open a DTS tech support incident, where I’ll be able to dedicate more time to help them [1].

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = «eskimo» + «1» + «@» + «apple.com»

[1] If they don’t have any TSIs to spare, you should sponsor them one. There’s no formal mechanism to do that, but you can just open a TSI and then loop in the tool vendor.

Mac app can’t be opened after re-signing with distribution provisioning profile

I’m new on Apple development and need some help for an issue about re-signing my app with distribution cert and provisioning profile.

My app is built, archived and exported in DevOps pipeline, using my Developer ID certificate (assigned by my company) and development provisioning profile. The build can be opened on a registered Mac but not on a non-registered Mac, which is expected as I’m using development provisioning profile.

For publishing the app on Mac App Store, here are re-signing steps in my company:

I can see the embedded provisioning profile has been replaced with the distribution one, but unfortunately it can’t be opened on any Mac, registered or not. I can’t tell what the reason is? Could anyone help?

Some error in console log:

App entitlements before re-signing:

Entitlements in development provisioning profile:

App entitlements after re-signing:

Entitlements in distribution provisioning profile:

Unable to install inhouse iPA files on iOS 15 (same app works on iOS 14) about ideviceinstaller HOT 1 OPEN

Anyone have a fix or a pull request for this issue yet? testing on iOS 15 Beta 3

ERROR: Install failed. Got error «ApplicationVerificationFailed» with code 0xe8008029: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.95tGvj/extracted/Payload/MYAPP.app : 0xe8008029 (The code signature version is no longer supported.) 14:39:13 installation_proxy.c:192 instproxy_lock(): Locked 14:39:13 installation_proxy.c:427 instproxy_receive_status_loop_thread(): done, cleaning up. 14:39:13 installation_proxy.c:203 instproxy_unlock(): Unlocked»>

Comments (1)

Well as you can see it clearly tells you the problem: The code signature version is no longer supported.
You have to sign it with a newer codesign I guess.

Related Issues (20)

Recommend Projects

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Can’t install WatchKit app on Apple Watch

I have a WatchKit app that runs fine in the Simulator. But when I try to run it on an actual device it never finishes installing and never provides any error message or feedback.

The iOS app installs and runs fine. I bring up the Apple Watch app on the iPhone and it lists the app and shows the correct icon. Selecting that, the «Show App on Apple Watch» switch is on. Underneath it it says, «Installing. «. And it stays there.

I can also see the app icon on the Apple Watch. Selecting it just shows the spinning wheel indicator as if it is trying to load.

Things I’ve tried based on other suggestions I’ve found here, on the Apple Developer forums, and around the web:

Verified that all app bundle IDs are correct and match.

Verified that the deployment target is iOS 8.2.

Verified that the WatchKit App runs in the simulator.

Verified that my provisioning profile includes my Apple Watch’s UDID.

Verified that my Apple Watch shows up as a «Paired Watch» in Devices.

Deleted the app from my phone, and then rebooted my phone, watch, and Macbook before reinstalling.

The code signature version is no longer supported.

calioptrix opened this issue 7 months ago · comments

Checklist before submitting a bug report

Xcode version

Facebook iOS SDK version

Dependency Manager

SDK Framework

Goals

install an app using the framework onto iphone with ios15

Expected results

app should build and run on the iphone

Actual results

When attempting to run the app on an actual phone, it gives an error unable to install. The details button says this:

macOS Version 10.15.7 (Build 19H1713)
Xcode 12.4 (17801) (Build 12D4e)
Timestamp: 2022-02-05T23:10:40-05:00

It is suggested to set the framework to «do not embed» but the «embed» column under project > target > general > Frameworks, libraries, and embedded content is blank. It only shows the names of the frameworks. xcode does not state if the frameworks are embedded, and there is no option to specify whether it should be embedded or not.

Steps to reproduce

create a blank project. add the facebook sdk from File > Swift Packages

Code samples & details

You mentioned that this is occurring with a new blank project, however we weren’t able to reproduce it with a blank project. Can you attach that project that it’s occurring with for you, so that we can take a closer look?

Also could you try upgrading to Xcode 13 to see if this issue still occurs?

Attached is a blank project that does not run once the facebook sdk is included.

I am unable to upgrade to xcode 13 as it requires macOS 11. I have a 2012 iMac and 2012 mac mini. Both are limited to macOS 10. I am experiencing the same issue on both systems.

Hi, this issue happens when you add FBAudienceNetwork xcframework static file into the project and run on device.
I created a repo that reproduce this issue. This issue also happening on XCode 13.2.1.

Invalid signature format on watchOS8 with watchos_application/watchos_extension (no issues on watchOS7) about rules_apple HOT 7 OPEN

The issue

We’re getting an error («failed to install») when we try to install our watch app built with watchos_application/watchos_extension with an enterprise account, on watchOS8.

In the iPhone’s logs, we have this line during the error:

The same app can be installed without problems on watchOS7.

Some investigations

I found a discussion about this error: https://developer.apple.com/forums/thread/682775?page=2.
This error should only happen when an app is built on Catarina or older OS, but our app was built on Big Sur.

Some workarounds

Re-signing

Passing the option to codesign

to where we’re using watchos_extension ( codesignopts available) and watchos_application (with a few changes to hardcode codesignopts ), the resulting IPA was OK.

Comments (7)

Are you on Big Sur? And using Xcode 12.5?

rsahara commented on August 25, 2021

Yes, on Big Sur 11.5.1, using Xcode 12.5.1.

keith commented on August 27, 2021

Hearing from some folks that this is an Xcode bug that was supposed to be fixed in 13.0 beta 5 but was not, and happens with xcodebuild as well. If we’re just missing a flag that Xcode started passing we can probably add that

keith commented on September 25, 2021

It looks like your value of CodeDirectory v=20400 is mentioned to be «the old format» (it should be 20500 ). Based on this doc I think all you have to do is regenerate your provisioning profile and rebuild like normal

rsahara commented on September 27, 2021

Thanks, I’ll try again.

fatenumber25 commented on October 2, 2021

Hi rsahara. Did you solve the problem?

I also compiled project using XCode13 on Big Sur 11.6, but it was exactly the same and it didn’t solve the problem. 😥

rsahara commented on October 4, 2021

I just tried by regenerating the provisioning profiles but I still have the same problem.
I’m still using the workaround ( codesignopts = [«—generate-entitlement-der»] ) for now.

Related Issues (20)

Recommend Projects

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

How to troubleshoot app package signature errors

An app deployment failure can be caused by a failure to validate the digital signature of the app package. Learn how to recognize these failures, and what to do about them.

When you deploy a packaged Windows app, Windows always attempts to validate the digital signature on the app package. Failures during signature validation block deployment of the package. But why the package didn’t validate might not be obvious. In particular, if you sign your packages with private certificates for local testing, you often must manage the trust for those certificates as well. An incorrect certificate trust configuration can lead to signature validation failures.

What you need to know

Technologies

Prerequisites

Instructions

Step 1: Examine event logs for diagnostic information

Depending on how you attempted to deploy your app, you might not have received a meaningful error code for the deployment failure. In this case, you can usually get the error code directly from the event logs.

To get the error code from the event logs

Run eventvwr.msc.

Go to Event Viewer (Local) > Applications and Services Logs > Microsoft > Windows.

The first log to check is AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational.

Deployment-related errors are recorded in AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.

For deployment errors, search for the most recent error event 404. This error event provides you with the error code and a description of why the deployment failed. If an error event 465 preceded the 404 event, there was a problem opening the package.

If the 465 error didn’t occur, see general Troubleshooting packaging, deployment, and query of Windows apps. Otherwise, refer to this table for common error codes that can show up in the error string for error event 465:

Step 2: Determine the certificate chain used to sign the app package

To figure out the certificates that the local computer must trust, you can examine the certificate chain for the digital signature on the app package.

To determine the certificate chain

The top certificate in the chain is the root certificate and the bottom certificate is the signing certificate. If only a single certificate is in the chain, the signing certificate is also its own root certificate. You can determine the serial number for each certificate that you then use with Certutil:

To determine the serial number for each certificate

Step 3: Determine the certificates trusted by the local machine

To be able to deploy an app package, it must not only be trusted in the user’s context but also the local computer context. As a result, the digital signature can appear valid when viewed in the Digital Signatures tab from the previous step but still fail validation during deployment of the app package.

To determine if the certificate chain used to sign the app package is specifically trusted by the local computer

Run this command:

Run this command:

If you don’t specify the certificate serial number, Certutil lists all certificates that are trusted by the local computer for that store.

The package may fail to install due to certificate chaining errors, even if the signing certificate is not self-signed and the root certificate is in the root store of the local computer. In this case, there might be an issue with trust for the intermediate certificate authorities. For more info about this issue, see Working with Certificates.

Remarks

If you determined that the package couldn’t be deployed because the signing certificate isn’t trusted, don’t install the package unless you know where it originated and you trust it.

If you want to manually trust the app for install (for example, to install your own test-signed app package), you can manually add the certificate to the local computer certificate trust from the app package.

To manually add the certificate to the local computer certificate trust

After this manual addition, you can see that the certificate is now trusted in the Certificate dialog.

You can remove the certificate after you no longer need it.

To remove the certificate

Run Cmd.exe as administrator.

In the administrator command prompt, run this command:

Look for the serial number of the certificate that you installed. This number is the certID.

Run this command:

We recommend that you avoid manually adding root certificates to the local machine Trusted Root Certification Authorities Certificate Store. Having several applications that are signed with certificates that chain to the same root certificate, such as line of business applications, can be more efficient than installing individual certificates to the Trusted People store. The Trusted People store contains certificates that are considered trusted by default and so aren’t verified by higher authorities or certificate trust lists or chains. For considerations around adding certificates to the Trusted Root Certification Authorities certificate store, see Code-Signing Best Practices.

Security Considerations

By adding a certificate to local machine certificate stores, you affect the certificate trust of all users on the computer. We recommend that you install any code signing certificates that you want for testing app packages to the Trusted People certificate store. Promptly remove those certificates when they are no longer necessary, to prevent them from being used to compromise system trust. If you create your own test certificates for signing app packages, we also recommend that you restrict the privileges that are associated with the test certificate. For info about creating test certificates for signing app packages, see How to create an app package signing certificate.

• ← The code execution cannot proceed because msvcp140 dll was not found
• The contours do you love me →