I am running Xcode 9.1 on a mac with Xcode Server. We have it setup to run our bots but every time a bot is created when it gets to the tab that says signing we always see this error...
Every time I click Add Server to Team and it adds it and moves on but the next time I set up a bot the same thing occurs.
My issue is with people who are not admins then can't click on the button so I need to make the bots for them. Is there a way around this? Am I missing something/doing it wrong?
This turned out to be something stupid but will leave it here in case someone else experiences it. Another one of my teammates had re-built key/cert pair and had never re-built the provision for it. So we were still using the old on the server. Once I added the new one that problem went away
Related
I'm trying to set up continuous integration (CI) in Xcode 9 with it's new built-in Xcode Server functionality. (MacBook Pro, macOS High Sierra)
I've been following various tutorials, such as Tutorial: Continuous Integration with Xcode 9 and FastLane, Xcode Server and Continuous Integration Guide: Configure Bots to Perform Continuous Integration, and a few others.
Everything seems to work fine, till I get to the Product -> Create Bot... step. The window opens with a yellow triangle/exclamation mark warning symbol to the right of the Server dropdown:
The Previous and Next buttons are disabled. Nothing happens if I click on the warning triangle, and there are no other related messages I can see in Xcode or the macOS console.
I performed the same setup on another MacBook Pro running High Sierra and the same version of Xcode 9. There was no triangle on that one, and I was able to select Next and continue the process.
Update: The triangle is present for any project I create. And, I've tried closing/restarting both Xcode and the MacBook Pro.
I've searched repeatedly for things like create bot yellow triangle, create bot warning symbol, xcode 9 continuous integration warning symbol, etc, but found nothing relevant.
Has anybody seen this, and what does it mean/how do I fix it???
Ah, the actual problem was that, in Accounts, I used the integration user I had set up. That was incorrect. I needed to put myself or another registered user into the Account section.
Once I added my own user's Name and Password into the Accounts/Xcode Server section, I was able to successfully create a bot.
Your Server & Bots option in Xcode Preferences is still not enabled even though you did it earlier.
Re-enable it and this should fix the issue.
As shown here
Also make sure permissions are set correctly, As shown here
Since Apple moved to their new and improved TestFlight website, none of my internal or external users are receiving push notifications or emails when I make a new build available for testing.
These are testers who previously were getting push and emails with each new build.
If the tester goes to the TestFlight app on their device, they do see the new build is available for update there.
I see a couple threads about this in the Apple Developer forums but nobody seems to know how to work around this problem:
https://forums.developer.apple.com/thread/76020
https://forums.developer.apple.com/thread/76131
Anyone here found a workaround for this problem?
when submitting a build for beta approval, uncheck 'automatically notify' in lower left corner. then after beta is approved for external testing, click 'notify testers' in upper right corner. if i recall next time i do this, i'll include screenshots.
this solution is from #boozedog, it fixed the issue for me, and i am submitting #boozedog's comments as an answer. the text of his comment:
"
The Automatically Notify checkbox appears in the bottom left of the dialog box when you submit the build to beta approval on the iTunes Connect website. Make sure you clear that checkbox. And then, after the beta approval is complete, go back in to that build in iTunes Connect website and you should see an action button in the top right corner "Notify Testers."
"
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.
Well, I submitted an app to the app store, but my little cousin went on my computer and screwed up the project so badly that I had to start from scratch. So I rebuilt everything back to how it was, and I am trying to submit it to the app store and it obviously isn't recognizing it as the same app,
(Please make sure that you have set up a record for this application
on iTunes Connect.)
although the bundle ID is the same as the old one. How can I go about doing this? I have to get this update out fast, any replies are greatly appreciated!
Have you prepared the app in iTunesconnect to receive an update?
After you have chosen to "Add version", you still have to press the button "Ready to upload binary" in the top right corner of the details screen of the app.
It should be sufficient to keep the app bundle the same in order to update.
You also have to use the same provisioning profiles as you used before.
Been trying tonight to obtain a receipt for my app. However, I've been unsuccessful. Here's the steps I've done:
Code signed with developer cert
Made sure minimum version in the info.plist is 10.7
Checked for the presence of the receipt file and called exit(173) if not found
Built from XCode 4.2
Added a new version of the app and some in-app metadata in itunesconnect. The app status is now waiting for a new binary.
I've then done clean, build, right clicked on the app in XCode's project view and opened it in finder to launch it, hopefully failing validation and pulling a receipt back from the store.
However, this never seems to happen (don't get asked for any itunes login etc) and the app terminates immediately.
I've also gone through an entire build/archive/create installer type process as well but that didn't pop up the login either.
Am I missing something obvious?
Thanks!
I've finally got it working. In case anyone else has a similar problem, the real help for me was finding out about console.app. In running this I could see my app didn't appear to be signed.
I deleted all the certificates etc and re-installed new ones. Seems it HAS to be the Mac 3rd party developer. Nothing else seemed to work.