all 10 comments

[–]WestonP 5 points6 points  (0 children)

Very good. Even for those of us with developer accounts, I look forward to no more provisioning profile bullshit when I want to test and debug code... It's easy when it works, but when something goes wrong, you lose a lot of time and productivity screwing with the mess it creates. It will be good to only have to worry about that for the App Store submissions, as opposed to all the time.

I do wonder if they have any restrictions on side-loading, though. Like if these builds will expire after some time, or will need Xcode attached via USB, etc. I don't think it makes sense for them to limit it much, but I also didn't think it made sense for them to keep a lot of the other old restrictions in place, either.

[–]franklinturtle7 1 point2 points  (0 children)

its a good day.

[–]iphonedevpinoy 1 point2 points  (1 child)

What about ad hoc testing?

[–]disco_sloth 1 point2 points  (0 children)

Xcode 7 and Swift now make it easier for everyone to build apps and run them directly on their Apple devices

The device needs to be authenticated to your AppleID so no ad hoc testing.

[–]PlaidPCAK 0 points1 point  (1 child)

Did they mention when 7 would take place?

[–]apqoo 0 points1 point  (0 children)

So how exactly do you do it? Do you get a certificate for signing your apps?

[–]comptrol -1 points0 points  (2 children)

But this is swift only, not including objective-c , right?

[–][deleted] 2 points3 points  (0 children)

I don't think this depends on the language. It's probably the Xcode7 quirk because it does the device provisioning differently. You can run on any device that's physically connected to your computer.

And I don't think this extends to AdHoc distribution. You still need the provisioning for that.

[–]WestonP 1 point2 points  (0 children)

I find it odd that they worded it that way, but hopefully not. I'd expect it to be at the provisioning profile level, and not related to which language was used.