I've updated my app to use Swift 1.2, which I'm realizing requires Xcode 6.3, which is still in beta. I tried to submit it to TestFlight, but as it's a beta version TestFlight said I couldn't use it for external testing.
How would I go about using TestFlight with my app, while being able to keep all my pretty as! statements?
The beta error you are reporting has to do with your provisioning profile. Make sure your AD-HOC provisioning profile has testflight enabled.
Edit it, enable test flight, Save, Re-download the provisioning profile
Then you will be able to use the iOS TestFlight features on your build.
Do you have any external testers configured in iTunes Connect? Remember external testers will only be able to test builds that have been "beta reviewed". If you want to just push builds quickly and get people testing then you have to add them as Internal Testers by adding them to your iTunes connect profile with limited privileges.
Personally I much prefer the way TestFlight used to work but now that I've got my team setup as internal testers and my provisioning profile re-built with the "BETA TestFlight" setting enabled it isn't so bad.
Related
I have a normal Apple Developer Program (not the Enterprise one)
and I need to distribute an iOS application without adding each UDID to the provisioning profile. I do not want to jailbreak iphones.
It is possible to make an Enterprise provisioning profile where the signed applications can be installed on any device without adding it to the provisioning profile. (Correct?)
And it is possible only with Enterprise program. (Correct?)
Are there any other ways to get rid of this dummy need of adding the betatester's UDIDs and recompiling the app whenever new testers come, with Apple Developer Program only?
Providing you're already registered with the Apple Developer Programme, you can upload your build and from within iTunesConnect use the TestFlight options to make your app available for download.
There are two options, 'Internal Testing' and 'External Testing'.
(In answer to question about the profiles, you don't need to have an Enterprise Provisioning Profile.)
As you wish to make the app available for unknown devices, you will need to use external testing. Here is a link to Apple's info on it https://developer.apple.com/testflight/
You will need the email addresses of the beta users (up to 1000 users) as those will be used to send an invitation to download via TestFlight from the device they wish to download to.
For external testing, your app will need to be submitted to Apple for Beta Review, which normally only takes a day or so for them to approve. Once approved this build is available to invite the beta testers to download
I hope this helps
I'm done with testing my app on all my devices through building the app on Xcode Project. Do I now need a distribution certificate or can I use my development certificate to use iTunes Connect pre-release internal testing thing?
I'm the only one who worked on my app so what would be the difference between testing my app on iTunes Connect pre-release internal tester and the way i've been doing it by building app onto device with Xcode project from desktop?
I'm fairly certain that you do need a distribution certificate and provisioning file since you are uploading a build into iTunesConnect which could then be used for app submission.
In addition to the distribution provisioning, one other difference between an Xcode install and uploading to iTunesConnect is that your binary will go thru the verification process - that process may find issues with missing icon sizes, etc.
I developed an iOS app using Titanium on a macbook. I need to create the IPA file for allowing other testers to try my app on their devices (via TestFlight). I have no iPhone nor iPad, but accordingly to plenty of articles on the web this is not a problem at all.
BUT, I need a Provisioning Profile and I cannot create one without a device.
So, how can I compile?
In order to compile it to be installable on their devices via TestFlight, you must add their devices to your account and then add those to the provisioning profile. Then you can build the app and upload it to TestFlight.
The way TestFlight works is that when you add testers to your team, it will send you their device UDIDs. Then you will go to the iOS developer portal and add them to your devices list, then you'll (re)create the provisioning profile with those devices added.
EDIT:
I don't know why I was downvoted for a right answer, but in case clear steps are necessary, here it is:
Create TestFlight account
Do "Add Application" so that you have your app entry in the TestFlight system
Invite your testers to your team
Wait for your testers to accept, and add their devices to their TestFlight account
Take the UDIDs for their devices that TestFlight sends you, and go enter those devices into your iOS developer account
Create your provisioning profile using those devices that you just entered
Create your IPA using that provisioning profile
Upload your IPA to TestFlight
Give your testers permission to download the build from the Permissions tab in TestFlight
I think you were making the incorrect assumption that you needed the IPA first, which is not true. TestFlight is first the mechanism to get the UDIDs of your testers devices, before you create the IPA. After that, TestFlight is your mechanism to distribute the app to your testers. I and many other people have done exactly the above steps many times, and you can be assured that you don't have to have the IPA first, you only create it after you have the device UDIDs of your testers.
try this code
ti build -p ios -T dist-adhoc
or
ti build -p ios --deploy-type production --ios-version 9.0 --keychain --target dist-adhoc --output-dir
My iOS app just working on my developer devices other phones can't install I'm using phonegap. Other devices can download but when install get full its sticking in install. I think Problem in the Provesion or certificate.
If you haven't added the other devices to your provisioning profile, you will need to.
Also, take a look at TestFlightApp.com to help with the app distribution process during testing.
You need to add all devices you want to test on into provisioning profile you are using.
Here is a good answer how to do it:
How do I add a device to my provisioning profile?
You have to keep list of devices you are using for development only during development phase.
Apple is protecting themselves from you publishing application outside Appstore.
For submitting app to Appstore you need to use Distribution certificated - than everyone can install it - but only when downloading from Appstore - you won't be able to install that build outside Appstore flow.
During development you are only allowed to add up to 100 devices on your account. On enterprise account however there is an option to release "in-house" build - which allows you to install app on many devices - but you are not allowed to use that to distribute an app.
I am working on my iphone app and now I want to send my app to my testers. But how should I send it to them ? Plus, they don't have an Xcode. Is it necessary?
Take a look at Test Flight. We are currently using it and it offers a lot of great tools and is very easy to set up.
testflightapp.com
It distributes it adhoc and then you can push it directly to the testers and allows you to see install statuses. Time spent and other analytic tools.
To answer your other questions. The don't need Xcode. They just need to have their UDID registered on your apple account. They will get sent an email that will ask to download the latest release. The app then installs over the air.
Since iOS 4.0, users have been able to install Ad-Hoc apps over the air. Please note you're required to get the testers' device UDIDs and add them to your device list on developer.apple.com and to the app's the provisioning profile.
You can host the IPA yourself, but I would recommend using TestFlightApp.com.
Macworld wrote a decent article about the gist of it, and TestFlight is fairly straightforward to use, especially since it allows you to send an email or link to your testers and collect the needed UDID from them.
Try diawi.
I find it very simple and very friendly to use. Also there is no wait in the queue type registration stuff. When you open it just drag and drop the .ipa file and the provisioning profile. To verify whether or not your app has been installed, just add your email id in the field mentioned and you will get a confirmatory email about your app installation. For installation at the tester's end they simply need Safari to install the app and the profile.
Below are the steps to create .ipa file (xcode 4.2)
Select iOS Device>Go to Product>Archive>Share>Choose iOS App Store Package (.ipa)>Provide a path to save.
Easily done!!!
From 26 feb 15 Testflight is closed their service...
I have used new link for creating installation link of ipa and distribute link to your client, tester etc.
open this link
http://www.diawi.com/index.php
upload provisioning profile(drag and drop) to their dashboard.
upload ipa(drag and drop) to their dashboard.
click on send button.
after that copy generated link and share to your client and tester.
With iOS 8, Xcode 6, iTunes Connect and TestFlight you don't need UDIDs and Ad Hocs anymore. You will just need an Apple ID from your beta tester. Right now you can only beta test your app with 25 internal testers, but soon 1000 external testers will be available too. This blog post show you how to set up a beta test with internal testers,
http://blog.thebetafamily.com/2014/09/10/testflight-beta-testing-ios-8/