I’m referring to the button that let you add an unprovisioned iPhone/iPad to the list of devices that you can deploy to. It copied the provisioning profile on to the device and added the device to the list of team members.
I found this out the hard way yesterday when I took my Mac mini to a client’s to add a new iPhone to the test. It was a bit stressful to put it mildly. I had upgraded Xcode to the latest which is 6.0.1.

Xcode Window Devices Menu Item

First the devices are no longer on the main Organizer App window which now shows only Projects and Archives. Click Devices on the Xcode Window menu and you get a form with a list of attached Devices and available Simulators. But No Button! You only got the button when you do this and have an iOS device that hasn’t been provisioned for development yet. Now you have to add the Provisioning Profile through the web interface on Apple’s site. This is surely a retrograde step.

To add a provisioning profile requires the following steps.
1. Log in the Apple Dev Portal and click Certificates, identifiers and Profiles. Click on Devices in the left menu. Note You may have to reset the list before you can add any extra. I assume it’s doing some kind of housekeeping update.

List of provisioned devices

2. You have to copy the UDID from the unprovisioned device and give it a name in the portal. Or you can add up to 100 in one go. 100 is the maximum you can have in your team.

3. Next you have to generate a new provsioning profile. This needs you to have a valid development certificate and all the devices ticked. If you don’t tick the newly added device then you won’t be able to install the provisioning profile on that device.

Generating a Provisioning profile

Back on the Xcode devices list add the provisioning profile to the device. You right click on the Show Provisioning Profiles and click + then browse to where ever the downloaded provisioning profile was. All this instead of one button! Now you can install your App.

A new privacy setting in iOS 8 means that apps using Location services need to have permissions enabled. One way to do this is by adding these extra keys to info.plist. One is for

	NSLocationWhenInUseUsageDescription
        Please allow Location services

        NSLocationAlwaysUsageDescription
        Please allow Location services

Then in settings you’ll see this:

Location Access settings

I noticed this testing an App which relies on GPS. When I ran it on iOS 8, it was not providing location information

My Visual Studio started taking a longish- three to four minutes to load up and then the same when I opened a project. This started after the last Xamarin update. I’ve always found that for best results I have to reboot after an update and then unpair and pair. Sometimes my Mac Mini shows up in the Connection dialog as an IP address and sometime as the name. As the ip is DHCP provided, I figured out using the name was best however..

To cut a long story short, Zone Alarm did not like DNS queries for the Virgin DNS ( 194.168.4.100 and 194.168.8.100 port 53 ) which were resolving the Mac Mini and it was those being blocked that slowed VS down. I figure it must have been a timeout plus maybe some kind of fallback as I could still build projects on the Mac.

So if you ever get that kind of slow down, check your firewall!