Run without Apple Dev cert?

[frdmn]

I am a bit out of the loop lately regarding iOS development. Is it already possible to build and test apps locally without a provisioning profile?

Would love to give this a try

[trenskow]

Hi @frdmn

I think it's possible from Xcode 7 and iOS 9 onwards. Apple has not yet made it possible to run apps locally without a developer account, but at WWDC they mentioned it to be one of the features of Xcode 7. So maybe - if you get a hold of the Xcode 7 beta, you might be able to compile it and run without a provisioning profile?

[frdmn]

Thanks for the quick reply, @trenskow.

I'll give it a shot and report back as soon as I know more :)

[alexbird]

Yes, it works. You'll need to change 'Enable Bitcode' from its default Yes to No, as the AirFloat library isn't compiled with Bitcode. I also increased the deployment target to lose another error which I don't recall. Built and seems to run fine on an iPod Touch (4th gen) running 6.1.3.

[craigeley]

I just wanted to confirm that this works just fine using the Xcode 7 GM—no dev account needed. Here is a screenshot of the bitcode setting that you need to toggle to "No" that @alexbird mentioned

I have this up and running on a device with iOS 8.4.1, with no need to change the deployment target from 5.1.1.

[rboy1]

Can someone build a working version that works with iOS4 and upload for the rest of us :)

[llumiaho]

Xcode 7.1.1 complains that I need an account to compile the app even though I've put "enable bitcode" to No.

[craigeley]

You still need an account—but it can be a free account. You can just connect a dev account to your existing AppleID.

[frdmn]

@rboy1 That won't work. We can't build the project for the mass - you need to build it by yourself.

[chrisjohnson83]

Is this working for iOS 9.2? When I try to build I get tons of errors

[JBA474]

After fiddling with the build options (mostly turning off debug and only active cpu architecture) I am able to deploy a working copy on non-jail broken iOS 9.2.1. I used the free Apple ID for the provisioning profile. There are a large number of deprication warnings but it seems to work fine. I've not tried requiring a password to connect. That might be broken due to deprication of the crypto libs (baseless speculation) but I haven't had the need and haven't verified. YMMV. I've posted my changes to my repo. All credit goes to the authors I am very happy to report their work continues to be successful on the latest hardware and iOS versions. Thank you.

[tomchentw]

Thanks for the great project. I can confirm it running with the following condition:

1. No Apple Developer Membership (I registered as Safari Extension developer before)
2. iOS 9.3 (both on iPad Air 2 and iPhone 6)
3. Xcode 7.3
4. The only thing I need to do is, change bundle id to another namespace. For example,

- com.tren.AirFloat
+ com.SomeOtherValueOfYourChoice.AirFloat

Thanks again!

[vrudikov]

@tomchentw +1 the same worked for me

[Tekl]

Do I have to compile the App every 90 days as the provisioning profile expires?

[JBA474]

Sounds like you're using the free Apple ID (not dev account), same as me. No I don't have to recompile. You don't even have to hook up the iOS device to the Mac. You do have to go into Xcode to generate a new provisioning profile. I've not read up on how it syncs up (speculating- same way as the rest of the App Store apps with Apple kill switch built in). Generating the new provisioning profile without recompiling and without plugging device in, works based on my experience with AirFlow and any other apps I've used my free, self generated provisioning profiles. If a profile expires and app won't launch, I've not seen an error, it just goes back to the springboard. You can fix same way, create the new profile and as long as it can connect to the internet the app will start working again.