Search Results

I am trying to compile Xcode project on an online platform Bitrise. I am facing issue with sign in and provisioning .. after trying 4-5 days I am approaching you. Please solve this. ❌ error: No profiles for 'my app bundle id' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'my app bundle id'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'myapp-Development' from project 'myapp') How to enable this "allowProvisioningUpdates" also why it is too difficult to do such processes with apple development.. I tried for android and it compiled successfully in a single attempt. please help.

Problem I am trying to code sign our application with an EV Code Signing Certificate. When I run this command: % codesign -s "Health Record Corporation" "MedKaz.app" I get the following warning / error message: Warning: unable to build chain to self-signed root for signer "Health Record Corporation" MedKaz.app: errSecInternalComponent % Keychain Access The Health Record Corporation certificate does show up under Certificates area in Keychain Access. I set the certificate to Always Trust in each category under the Trust section. However the certificate DOES NOT show up under My Certificates area. I think this is the issue which is causing the problem above (i.e. certificate should be visible in My Certificates) too. My attempts to resolve I rebooted my system and took out / put back in the secured certificate token USB drive that contains the certificate numerous times. No luck in showing up in My Certificates area. I tried this recommendation to disable System Integrity Protection in Big Sur but to no avail. Any ideas on how to resolve this problem?

I'm building a Unity application and attempting sign, package, and notarize the app for distribution outside of the App Store. I've joined the Developer Program, and created both Application and Installer Developer Certificates and installed them to Keychain. Using a command line build pipeline, I am able to use productbuild, productsign, and xcrun altool to generate my pkg and notarize it. Notarization is successful, and I receive Status: success and Status Message: Package Approved. Then I staple the notarization ticket to my package. However, when running the installer, I'm met with an error saying "MyPackage.pkg can't be installed because its digital signature is not trusted." If I generate the same installer without notarizing it, I have no problem running it and it installs successfully if I alter my security settings to allow apps from unknown developers. Does anyone here have experience packaging Unity apps for Mac? What am I missing here...? All the feedback I'm getting from the notarization process appears to be positive, no errors to indicate that something went wrong until I actually try to test installation.

Hello there 🤓 We have this elderly QuickLook plugin that I am trying to revive for Big Sur... (Well, it seems to be a problem on Big Sur only.) The thing is that it uses NSTemporaryDirectory(). This directory can be written to when built locally in Debug/Release configuration. But when doing an Archive/Notarized builds the plugin cannot write to the directory. I have here found that in this case it gets its NSFileExtendedAttributes set to com.apple.rootless! So somehow System Integration Protection (SIP) kicks-in! I have found two workarounds: If I disable SIP ($ csrutil disable from Recovery mode) then it works. If I enable the Hardened Runtime exception 'Allow DYLD Environment Variables' then is also gets write access to the temp directory. My question is: Can one give a proper explanation for why SIP kicks-in? Could we have misconfigured something? Let me know if you need additional information, thanks. Best regards, Jens Schwarzer.

I turned on the sign to run locally, and get the following error: x.app/Contents/Frameworks/***.framework/Versions/A: no such file or directory This is third party framework and the folder structure is ...Versions/1.1.0/... Is there a way to tell the Xcode to using the right path?

I have been having problems signing an app with jpackage. I am confused and I'm not sure if it's because I don't have the correct certificate from Apple. Or I am doing something wrong when I pass the signature to apple. I find Apple certificates very confusing. And I think I have made several unnecessary certificates while trying to figure this out. What I think is the problem is Jpackager seems to want the certificate to be of type: "Developer ID Application" and I seem to be only able to create "Apple Development" or "Mac Development" signatures. My role on my team ris a "developer" and I am wondering if I need my boss to create the correct certificate? I have been googling like crazy and am not even sure if I understand what values are needed. For "signing-prefix" or "key-user-name" `--mac-bundle-signing-prefix --mac-sign --mac-signing-keychain --mac-signing-key-user-name ` I have used the following and Keychain Access to view my codesign values: security find-identity -v -p codesigning P.S. My program uses Swing and needs to run on MacOS, Windows 10 and linux which is why I use Java in the first place.

Have an iPhone project where we use XCode to develop and use xcodebuild to create our production releases. We have a complete build system and scripts that we have been using for years, across many versions of MacOS and XCode, and without problems. Problem: I just moved to a new Mac Mini M1 and the xcodebuild process now generates an error and fails. There have been no other changes in the code or the project between building on my old Mac Mini and the new M1 Mini. WAS USING: MacOS 10.15.7, on Mac mini (Late 2012) XCode version: 12.2 NOW USING MacOS 11.0.1, on Mac mini (M1, 2020) XCode version: 12.2 The "xcodebuild archive" produces the following error: error: Provisioning profile "XXXXXXX Development Profile" doesn't include the currently selected device "Chris’s Mac mini" (identifier XXXXXX-XXXXXXXXXX). (in target 'XXXXXXX' from project 'XXXXXX') Now, "Chris’s Mac mini" is the name of my new development machine. I'm building a iPhone app, and our provisioning profile DOES contain a number of device IDs for various iPhones we test on. Why would it care that my Mini is not in that list? When I try, I can't even add a Mac ID to the provisioning profile Our normal xcodebuild command line is rather complex, but even if I run it with: xcodebuild -scheme <MyTargetName> and nothing else, I still get the error. noted above Any suggestion appreciated. Chris

I'm trying to debug my iOS app which designed only for iPhone on a M1 mac. But I got the error about signing. Xcode automatic signing failed with the note below: "Xcode failed to provision this target. Please file a bug report at https://feedbackXx and include the Update Signing report from the Report navigator." "Provisioning profile "iOS Team Provisioning Profile: com.XX" doesn't include the currently selected device "XX的MacBook Pro" (identifier XX)." How can I fixe it?

Hello, I am trying to set up manual codesigning in an automated build script that runs in Github Actions. The process was hanging because the codesign command prompts for a password. I tried to get around this in several ways: passing the password to codesign in the script (doesn't seem to work) using the -T /usr/bin/codesign option when doing security import <certificate> using the -A option when doing security import <certificate> unlocking the keychain, and extending the timeout time The UI prompt would still always appear. I finally found this question: https://stackoverflow.com/questions/39868578/security-codesign-in-sierra-keychain-ignores-access-control-settings-and-ui-p which seems to be the same issue. The solution suggested there, security set-key-partition-list -S apple-tool:,apple: -s -k <keychain password> <keychain name> solves the problem. I couldn't find any answers on these forums explaining this command. I have two questions: 1) Why did the first things I tried not work? 2) Could I get some confirmation that this is the correct and secure way to do this? Thanks!

In Xcode, i have this issue where it is telling me to revoke a certificate because the account already has a signing certificate but it is not present in my keychain. And that to create a new one, i need to revoke the existing one. I went to the developer portal and tried and revoked all the certificates and tried again. No avail. I can revoke it once, but if i go to a new target and do the same (as it is asking me to) the other one needs revoking again. I do not have a clue what to do.

Our developer account was renewed, and none of our apps are working now. None of the apps are on the app store, they are loaded onto different devices. I am not sure how to relaunch the apps so that they can work on the devices again. (For context, the devices aren't with me)

Hello everyone, I currently have an issue when signing my application using an iOS enterprise distribution certificate. I've revoked the current certificate which would expires next week and I've created a new one. However, after downloading this new one and adding it to the keychain I've checked my account certificates and it's displaying the following: iOS distribution [creator's name blank] 12/11/2020 iOS distribution Gustavo Serra 12/11/2020 Not in keychain It seems that my local certificate is not been recognized as the created one. Can someone help me? I've already tried to re-create another certificate, remove and re-include my account, nothing helped.... Thank you guys, Gustavo

I had to reset my computer and have lost the private key for our developer certificates and the distribution certificates. I'm nervous to just revoke those and start over new, but I need to update an existing and published app. I have found info for compromised private keys and for expiring certificates, but nothing for this exactly. Will the update be accepted as an update even though it's signed with different certificates than the previous versions of the app?