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
Related
I can't launch my app anymore on Android. The iOS counterpart seems to be fine.
The full error is:
ADB0000: Could not determin the installation path for package.com.company.appname.
'adb shell pm path com.company.appname' returned.
It was working. I pulled some changes from the repo, none of which should have affected any app properties. Actually it was initially launching, but I was getting some odd behavior within the app, so I uninstalled the whole thing off of my phone. Now I cannot launch it at all. What I could find about this error was that my AndroidManifest.xml might have a typo, but I couldn't find anything that stuck out. And like I said, there shouldn't have been any changes in there recently. Any help would be greatly appreciated.
Steps I have already taken:
1. Clean and rebuild
2. restart VS
3. delete obj and bin folders
4. search for solution on here and xamarin forums
UPDATE:
I just successfully launched it on another android device. So it seems to be a problem with my Pixel 2 XL. How do I make sure all traces of the app are gone so I can start fresh?
This usually happens when you have more than one user in an Android device (I still cannot figure out why is this).
As mentioned in the comment by using the adb uninstall full.package.name command it will uninstall the app.
But there's another way which does not require command line or nothing related to that.
If you go to the Settings -> Apps and Notifications on the Android device you will be able to uninstall it from there.
Let's use the UnoQuickStart.Droid app as example here. As you can see it's already in the same state as it was yours.
Once in the App details both Uninstall and Force Stop are disabled. But do you see those 3 dots image at the right upper corner? Click on it.
This will bring you a context menu with a single option "Uninstall for all users". You can click on it with confidence.
As expected, a warning message telling you what's gonna happen. Just click "Ok".
As you can see the App is not longer installed and you will now be able to install it again.
Hope this helps.-
As per apineda's instructions, using adb unistall com.company.appname fixed the problem. I was able to get to the ADB location by navigating through Visual Studio -> Tools -> Android -> Android ADB Command Prompt.
Before I did that, I looked at the App list for my phone, which listed the app, but apparently not installed for this user. The Uninstall and Force Stop buttons were disabled and several of the fields just said loading... or something like that.
I specifically need help getting the app build into my apps. I am so new to the MAC ecosystem. I need to get my app build from my windows 10 box (parallels) running VS2017/Xamarin Forms project uploaded to My Apps. What i have found is helpful if you are using xcode on the mac.
I have read tons of pages and help files and with all of that what I have includes:
created an app in VS2017/Xamarin that runs happily on the emulator from the MAC (MacBook Pro)
purchased the app dev subcription from apple
created a Production certificate (I don't need this yet but I was in there so...)
created a Development certificate
created a key pair from the Dev cert (that show up in the keychain)
created an App Group
created my app's placeholder under My Apps on App Store Connect
added my iPhone to devices via connecting to the Mac getting the UDID from iTunes
created a development provisioning profile for my iPhone (Not sure how this helps my testflight plight)
Assumptions
You must submit for review the same way for both TestFlight and Prod release to the actual store.
You don't need to open the app in xcode outside Xamarin
There is a tool or concept I am missing out on.
For development outside of Xcode, you will want to use Apple's Application Loader App to upload your app to App Store Connect.
As I said in comment to Matt below his correct answer to my actual question above, I needed to get the project right to get to that point.
Here are the more intimate details for the lurkers. I hope this helps some of you.
I was getting, or trying, to get all of this in place manually instead of letting VS do it's work getting this stuff together while I got to coding. FastLane FTW
Open the account management window, go to Tools > Options > Xamarin > Apple Accounts
Add your AppleID
Click on your appleID
Click the add button
Select your id in the lower text area
then add your distro cert. As is proper you deploy to TestFlight as a prod release.
Then get over to to your iOS project properties:
Make sure that your project is outputting an IPA. (Not Beer ;) )
These are my settings that worked. There could be other configurations that work as well.
I never get the automatic provisioning to work. And while this bundle signing settings look like it will not work, it does. I have received my apple approval for beta and users are in testflight.
Also, make sure you update the version of the app in the plist for subsequent releases. This change is not carried through from the AssemblyInfo.cs as one might expect. viola.
If you see this during debug make sure your debug version has Developer (Automatic) set for your debug settings.
FWIW - My VS2017:
While this does not perfectly match the info # https://learn.microsoft.com/en-us/xamarin/cross-platform/macios/apple-account-management?tabs=windows it worked for me. That page was key to the solution and deserves citing. Your mileage may vary.
If I missed something please reach out and I will update this.
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
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.
I'm making a release for the first time since upgrading to Xcode 4.3.1.
While having a look to see if my profiles were up to date I also noticed that automatically updating device provisioning is no longer displayed (i.e. where it should appear in this screen shot doesn't appear for me How to add a new device to a team provisioning profile) but it used to there before I upgraded.
Is this something that has been removed with 4.3.1? If not, why is it no longer appearing for me?
xCode 4.3 now has the Refresh link on the far right, and there is no longer a checkbox for "Automatic Device Provisioning," at least that I can find.
Just clicking the Refresh link on the right is all that's needed to update the app's provisioning profile from developer.apple.com.
I'm not seeing it either. I'm having lots of troubles with code signing and ad hoc distribution, so I'm trying to follow Apple's (recently updated!) step by step instructions. However, they don't appear to match the options I have in XCode. It appears that "automatic device provisioning" has been silently removed as an option, or my Organizer install is corrupted.