Since Xcode Cloud was launched last year I'd been able to connect from the Xcode wizard to my Github.com account and the CI worked like a charm, however today I'd been trying to create an Xcode Cloud for a new app and it doesn't finish the wizard flow throwing an error
Connecting Xcode Cloud with your source control provider was incomplete.
Repository not accessible
On the GitHub.com side everything seems to be working, did tried this from 2 different computers with the same results, has anyone else gone through this issue?, is there a solution for this or filing a radar to Apple is the only option here?.
I was facing same issue as I had two account connected in the Team for signing in capabilities.
my solution, remove other account and keep main account for Xcode Cloud.
-Tenant
I had this issue as I have two developer accounts - a work account and a personal account. The issue arose when the signing certificate used in the project in Xcode did not match the App Store Connect account that was signed in.
Check your signing certificate / team in Xcode and that you are logged into App Store Connect with the correct details.
Related
I’m trying to add an apple developer account to VS 2019 Community ver. 16.9.2 for Windows.
Once I set the Apple ID and Password and click on Login, I get the following message:
“There was an error while trying to log in: Authentication service is unavailable.”
The Apple ID and Passwords are correct, in fact, if I type in the wrong credentials then Visual Studio complains about invalid id/password combination.
I disabled the firewall during the process so this should not be a connection issue.
Also, I made sure I have no pending agreements on Apple Store Connect. My apple developer account is valid and has no issues. In fact, I can use the same account on xcode just fine.
Is there some workaround?
THIS ISSUE IS FIXED IN THE 16.9.6 VISUAL STUDIO UPDATE !!!
(old workarounds)
There are some workarounds but none of them worked for me and updating to the latest version didn't help either (Visual Studio 2019 16.9.4). For as far as I know this issue persists even on version 16.7.5 of VS2019. For some people the workarounds seem to work so I will list them here so hopefully some of us can get on with our projects.
Workaround 1 (offered by Xamarin team):
Close Visual Studio 2019
Delete the following folder %LOCALAPPDATA%\Temp\Xamarin\XMA
Open project -> clean sollution
Set Automatic for bundle signing in the iOS project settings
Rebuild
(- if it doesn't work try again after restarting pc)
Workaround 2:
Delete your apple account from VS2019 through Tools–> Options --> Xamarin–> Apple Accounts
Sign back in again
Download your provisioning profile from developer.apple.com account to you pc
Copy and paste it into: \Users\YOUR_USERACCOUNT\AppData\Local\Xamarin\iOS\Provisioning\Profiles
If it doesn't work, perform in combination with workaround 1
Workaround 3:
Delete apple account from VS
Remove certificates from AppData\Local\Xamarin\iOS\Provisioning\Certificates
Remove profiles from AppData\Local\Xamarin\iOS\Provisioning\Profiles
Add Apple account
Set to Automatic Provisioning and select team, it will error again but will reinstall the certificates
Manually download provisioning profile and copy it to - AppData\Local\Xamarin\iOS\Provisioning\Profiles
Run the archiving process should error out again but the “id” or name of the provisioning will be displayed in the error
Rename the provisioning file to match and rerun archiving.
As I said these workarounds don't work for me but I hope they do for you. If it doesn't then you're in the same boat as me and you're going to need to follow this thread:
https://developercommunity.visualstudio.com/t/Error-adding-Apple-Developer-Account:-au/1380749?viewtype=all
I was able to use a combination of several workarounds from Michael's answer to get the app signed and deployed on an iPhone (for debugging). Here are the steps in correct order that worked for me:
Set Automatic for bundle signing in the iOS project settings
Delete your apple account from VS2019 through Tools–> Options --> Xamarin–> Apple Accounts
Close Visual Studio 2019
Delete the following folder %LOCALAPPDATA%\Temp\Xamarin\XMA
Delete all "obj", "bin" and ".vs" folders for the solution
Download your provisioning profile from developer.apple.com account to you PC and save it to %LOCALAPPDATA%\Xamarin\iOS\Provisioning\Profiles
Open Visual Studio 2019
Add your apple account from VS2019 through Tools–> Options --> Xamarin–> Apple Accounts
Build. It will error out while signing the app.
Look at the error. It should specify the expected file name for your provisioning profile. The file name is a long string of hex digits with extension ".mobileprovision".
Go to %LOCALAPPDATA%\Xamarin\iOS\Provisioning\Profiles and rename your provisioning profile file into file name from the error message.
Build again. It should work now!
I just went through the exact same problem and it took forever to work out. I'd had my app running locally and debugging on my iphone just fine. A few months later this bug popped up... I needed to simply update iTunes. iTunes handles the handshake stuff for your iOs devices and Windows.
I have been an android developer and was thinking the life is not easy but then I found the iOS developer account and its relativity with project creation and other certifications.
I have developed the app, then in that App, I need to add FCM notifications. For this, I have installed FCM pod. And made necessary changes in the project.
Now its turn for me to connect my project with FCM ios ( and ios APNS with FCM server)
So good so far. Now I want to create a different team for this project. But When I create a distribution certificate it always creates a file with the name of the team I was using before i.e ABCD. I tried to create another profile but it just creates ABCD named file.
Can anyone tell what could be the problem?
2nd what are the steps required to create a production certificate for FCM to launch the app in the store?
Please discuss the first point in detail why it is happening? Why I can't change the name of the certificate.
Note: Whenever I try to create a development certificate it take another name
Please let me know what is going on..........
Xcode generates certificate fully automatic these days. You should let it automatically build them for you till you experienced more with apple signing process.
you can change any identifiers you want before sending any kind of build to appStore, (for example for test flight)
If you didn't upload to appstore yet, you can just login with your other account in Xcode and choose it from the team dropdown in signing section of general tap in Xcode. Then Xcode tries to sign the app with new credentials.
For FCM, follow the original documentation of FCM.
And at the end, Welcome to iOS world ;)
I'm currently using the new Xcode-Beta as of the 30th July. I have been playing around and I found some Projects on GitHub that I have been looking at. I have been able to package them and then run them on my iPhone, however when I go to create my own project and run it, I receive this error message:
No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
I'm not sure what the issue is, as I cannot run the app on the simulator or my iPhone
Thanks for your help!
Its because the people on Github posting their own apps have signed them with their apple developer account. You need an apple developer account to create signed applications. Its 100$ a year. https://developer.apple.com
We had to change our development ID (apple ID) due to a change in email addresses.
We changed the email in the dev portal and via Apple ID.
Everything seemed fine - we could log into the portal and iTunes Connect and see our apps/certificates etc etc for the iOS dev team.
Tried to build our app, however, and Xcode seems to have other ideas, claiming that our (now new) Apple ID is not part of a development team!
The below are the steps we've been using to try to resolve the problem, to no avail:
Removed all certificates from keychain
Also removed any saved login-passwords from keychain
Went to Apple Member Centre, entered with new email address now being used for development.
Navigate to iOS Dev Centre
Navigate to Certificates
Downloaded Development and Distribution certificates (note that we did create brand new certificates)
Moved certificates from 6 into Keychain log-in
Download Provisioning profile (not sure why - can't seem to do anything with it since it looks like Xcode manages this itself)
Opened Xcode, go to Prefs > Accounts
Added account using new Apple ID
Account is added, however, it shows under the ID "xxxx#xxx.com is not on any development teams"
We have repeated the above steps (including reboot of mac) over and over again, with no changes. This is our development account (i can log into dev centre and iTunes connect fine and see our apps etc)... but Xcode tells us it isn't ><
Hope someone can shed some light on this, as we're all out of ideas here.
Cheers
I would either contact Apple or reboot your computer.
If those don't work, comment here for more help.
WHY DIDNT WE DO THIS FIRST?!
A lesson for us for the future.
We're using Unity to develop our app.
All we needed to do to resolve the issue is create a brand new build (we deleted the old one), rather than just do an amend build through unity.
Creating a fresh build resolved this developer ID issue.
I'm setting up a CI machine and the problem I'm facing is that the build fails with a profile/signing error when built using the bot.
However if I manually clone the project onto the CI machine and build it manually from within XCode on the build machine then it is successful - this shows that the CI machine's keychain is correctly set up and the profiles/signing setting of the project are all ok.
That fact that I can manually build it on my dev machine and on the CI machine but not using the bot suggests to me that the bot is running as a different user?
So my question is how do I set up the X Code server account / bot to be the correct user? The Apple Xcode CI document isn't very clear on this area, I've followed the instructions for configuring the server, configuring the bot, adding group members to the XCode server etc. but something must have been incorrectly configured. Trouble is I've followed the documentation step by step but don't know where I could have gone wrong.
Anybody know of a good alternative bot tutorial as an alternative to Apple's documentation or have an idea what the problem might be?
Copy the relevant provisioning profiles from
~/Library/MobileDevice/Provisioning Profiles
to
/Library/Server/Xcode/Data/ProvisioningProfiles
and it'll build fine.
You might need admin permission to access that folder, though.
And if that doesn't work, copy the relevant certificates/private keys from the login keychain to the System keychain.
The reason behind this is because..Xcode only downloads provisioning profiles that are managed by Xcode, which are the Team Provisioning profiles.
So you would only need to copy the ones that are not managed, like Adhoc Distribution profiles, and other custom provisioning profiles that are not created by default after creating a new Application ID.