When I tried to make an IPA out of my Xcode project (out of my Unity project), this error appeared and I don't know why:
Automatic signing is unable to resolve an issue
The project runs without any problems directly in mobile, and we tried the bundle identifier on other projects, it works. We tried rebuilding the Unity project from other PCs, this project has the same error. We can't make an IPA out of the archive.
Is there someone who knows where to locate the issue and how do we fix it ?
Thank you in advance !
Found it ! This solution worked, if someone is in the same case. https://forum.unity.com/threads/ios-build-failing-fccore-bundle-has-conflicting-provisioning-settings-xcode-9-2-automatic-signi.520730/
Related
I am trying to create a build from Unity Xcode project but getting this error.
I think that it might be related to firebase & PromiseObjC framework.
I don't know if is there any build setting that i am missing or overlooking.
It would be great if anyone has any idea about this
Thank you.
I recently forked an iOS library on GitHub to add support to it for the Swift Package Manager. Here's the repository: https://github.com/skelpo/mapbox-gl-native-ios
When I add it to a completely new iOS app and try to build it, I get this error:
Unable to resolve build file: XCBCore.BuildFile (The workspace has a reference to a missing target with GUID 'PACKAGE-TARGET:Mapbox')
I've found posts for similar errors, such as this one, but the reason for the build file failing to resolve is different.
I have tried the usual cleaning the build folder, deleting derived data, and restarting Xcode, but that hasn't helped.
What is the reason for this specific resolution failure, and how would I fix it?
I ran into a similar problem after upgrading to Xcode 12 recently, and found a fix for my case.
A major hint that led to the solution came from Aaron's May 3, 2019 answer on this page.
What fixed it for me was to select the root of the Xcode project, and change the Project Format from "Xcode 11.0-compatible" to "XCode 12.0-compatible".
I just downloaded and installed xcode from app store. But when i open it I get Plugin failed error. I tried searching on web about this problem. Found that it was some python related issues. SO i tried installing different versions of python, but still no success.
I dont know where is the actual problem... So i need ur help in troubleshooting this problem.
Thanx in advance....
I just plugged in a new iPhone 6, created a provisioning profile and then I launched the app I'm developing on the device. It compiled fine, but at linking stage it errored out with:
ProcessProductPackaging
...
error: class '(null)' of input object does not respond to either selector writeToFile:options:error: or writeToFile:atomically
I cannot find any information of what that is. I do not get any specific code reference to relate it to. Did anyone experience this?
Personally I was able to solve this issue by rebuilding the project a second time. I think I was only experiencing it after revoking and requesting a certificate.
Odd for it to jump at me and disappear though.
I just restarted Xcode then the error was disappeared
I've tried turning the "Automatically managed signing" off and on again, then the issue disappeared. Note: rebuilding didn't help for me, cleaning either.
I removed an external library and related code I had and it's now working.
I just changed some provisioning setting and then restarted the xcode afterwards the error was disappeared and archived and then uploaded successfully
Rebuilding the project does the job for me. Actually I was making changes in capabilities while Xcode was building that makes build failed.
The error occurred after I made manual changes to the Xcode .entitlements and Info.plist files: I removed some entries. None of the above mentioned solution attempts worked for me. Every try to create an archive failed.
The solution was to go to Xcode's Capabilities section and switched everything on and off again.
I had the same problem specifically on an App Extension we used for Push Notifications, and I was using Automatically manage signing but it seems the App Groups in capabilities were failing, so I just had to make sure the App Groups were retrieved correctly and this fix it.
Also if you have .entitlements files, and you have App Groups there, make sure they are the same you are using in the capabilities configuration.
Restarted XCode and enabled and disabled to Automatically manage signing
So, i finished my application and i'm stuck on the uploading part. I've tried to upload it with Application Loader and with Organizer (with the app archived) in XCode (i'm using XCode 4.0.2 SDK 4.3), but this warning \ error shows up in both the programs:
Application failed codesign
verification. The signature was
invalid, or it was not signed with an
Apple submission certificate. (-19011)
Now, all my provisioning profiles are ok, i did even make some new fresh certificates \ app id \ profiles. But the thing i don't understand it's how to set the Project Build Settings and the Target Build Settings. I'm really going crazy. I've googled a lot but i didn't find any solution to my problem. I've really tried ANYTHING.
Thanks to anyone who will help me!
I solved, thanks to the help of an Apple Technic Engineer, that way:
In targets, on Build Settings - Product name, i had the name of the app with spaces and special characters ( ? char). After changing that,and changing the Bundle Name too, i solved all the problems i got with that.
Hope this will help someone, one day.