I'm working with apple itunes connect website.
I want that my friend with an iphone can install my app from testflight.
My friend isn't part of my work team so he isn't listed in itunes connect users and cannot be an internal tester.
The "standard process" will be:
send app-beta review request.
wait for the review result
once is approved send invitation to external tester
I need that my friend will be able to run my app without waiting for beta-review (review request are disabled on holidays).
So i do the following:
add my friend to itunes connect users and give him developer privileges (he will have these privileges for a short time - and will not even know he has them).
he has to read the email received and click the link to activate itunes account.
add him to testflight internal tester so he can install my app.
finally my friend install my app from testflight
then, i remove my friend from both internal tester and itunes connect users so he has my app installed without wait the app review.
Will my app remain installed even if he is removed by internal testers and also by itunes connect users?
If yes this is a good method to skip the "so frustrating" apple app beta review process.
Actually, there is a way to skip review process. When you upload new build you just change Build, and not Version. You pass review for particular Version and then stack your Build's under this version without review (still, when you submit, button Submit to review is active but you will pass instantly). Enjoy.
If the AppStore were open, I would say to just wait for review. Each additional review for betas of the same version are automatic.
But, since that is not the case, you can do as you describe and it will work.
Another way is to get the UDID of the user, add it to your developer.apple.com account, make AdHoc profiles and make an AdHoc build. Then use something like Hockey to get them the build.
Related
After submitting the app to for review, I'am not able to add new testers or new test groups to the build. On clicking the add button in the Test Flight tab under the build in App Store connect a pop up is displayed with message "You can only submit one build from version 1.9.5 to Beta App Review".
Other than App Store Connect users a build that is under review cannot be made available to any testers. Although the error message is not very clear you can't add external users to a build that is not approved. Once it is approved you will be able to add new groups of users to it.
You can check the Internal or External Testing capabilities in https://developer.apple.com/testflight/ and find out what is going wrong with your case.
I want to make my app available for the testers without adding their UUIDs to the distribution profile. Is there any way to achieve this. I know about Enterprise distribution but my app will eventually be uploaded to AppStore.
So I also want to know is it possible to use same Apple ID for both Enterprise App and App Store app.
Thank you
Yes, you can use the new Testflight feature on the developer portal: https://developer.apple.com/testflight/
You have two options when using this. For internal testing anyone who is tied to your account can test it. For external testing your app has to go through the approval process, and you can give out an email that will allow them to test it, or put their email in and it will send out an invitation to that person to install the app. Any updates to the app have to be approved before it can go to external testers.
UDID is no longer required. The focus is on test users rather than device. A single user may have multiple devices on which the beta app may be installed.
You can enable up to 25 users from your iTunes Connect team to be
internal testers and up to 1000 users to be external testers. External
testers do not need to be in your organisation; you can invite any
user with an email address to become one of your external testers.
reference from below link :
https://subodhnpushpak.wordpress.com/2015/01/05/deploying-ios-apps-without-udid-to-beta-testers-using-testflight-beta-testing/
Now when I open testflight link on iPhone I get an error:
"The requested app is not available or doesn't exist." Earlier everything was ok. How to resolve this issue?
(See comments on question)
I had the same problem yesterday. The only working solution was to delete the affected tester accounts from iTunesConnect and to invite them (and add them as internal testers) again.
Make sure that you are logged in with the correct iTunes account on the device, as it will not show the app if you are using a different iTunes account from the one specified in the iTunes Connect private beta
I was able to fix my problem.
log into itunes Connect
on itunes connect user, click +
I created a new user (same email but with + portion) ie user+testing#gmail.com
Give them a role that includes In-App Purchase Tester
make sure to add them to a group (this is the thing I missed)
verify from the apple id email for that user
create apple id account
back in itunes connect click on My Apps
click on prerelease
click on internal testers
make sure they have a check in the check box, click save
click on Builds
click on Testers
make sure they exist in the list of testers now
I then turned off the beta test for that build, and then reenabled the testflight beta testing, so that it resends the notification
I've developed a phonegap app and have it working and deployed to Android. But I don't know much about iOS and don't have a ton of Apple gear. I have a developer account to deploy to the store, but would like to pass the apps to some friends with various devices to take a look at it before I deploy it to the store. These friends aren't local (as in, plugging in the devices).
What are my options with this? Can I create an ad-hoc certificate and send them the app to install or what do I do?
Any guides etc would be helpful. At this stage, I really don't want to go spending £1000 on Apple gear.
Go for TestFlight. Apple bought it and integrate with itune connect for Testing purpose. You have to create a provisioning profile to distribute your application with it and you have have internal test and even 1000 testers external with need of there UDID.
You guess is right, create an Ad-Hoc profile, make sure your friends device UDID is linked in the profile and send it to him.
The other option is to use iTunesConnect TestFlight, upload the app to iTunesConnect and release it a an internal beta. Register your friend as an technical member of you iTunesConnect account which will allow him to install the app use the TestFlight app from the App Store.
Last option is a public beta in TestFlight, for this option you do not need to register you friend as technical member of you iTunesConnect account. But you will have to send in your app for review with Apple. After review you can invited up to a 1000 beta test by mail.
The main advantage of the iTunesConnect Testflight it that you do not need the device UDID of your friends device. He can install the app on multiple device with the use of the same Apple ID that he registered for the invite.
I am trying to use the new iTunesConnect beta testing. I am trying to invite a user to test however he already has an iTunes Developer account and it won't let me invite him because it of this:
The email address you entered already belongs to an iTunes Connect
account. To continue, enter a different email address.
I searched around but found no solution. What are my options in this case?
Thanks.
Currently you can only invite internal testers beta testing through Apples beta testing system. The definition of an internal tester is someone who is actually in your iTunes Connect team. An email address can only be associated with one iTunes Connect team and because your tester already belongs to another team they can't be added to yours.
You can always do an AdHoc build for them just the same as you would have done before the Apple beta testing system came online. Provision their device, archive and build an ipa and then upload it to TestFlight.
You can also send them the build (.ipa file) of your app and they can re-code sign the app with their developer certificate (see image). They can then install it on their devices or put it on the iOS simulator.
Here is the (re)code sign terminal command:
#! /bin/bash
export CODESIGN_ALLOCATE=/Developer/Platforms/iPhoneOS.platform /Developer/usr/bin/codesign_allocate
codesign -f -s "iPhone Developer" $1.app
My approach is simple:
All client Apple Ids as internal testers (if possible).
All my company Ids assigned as external testers in client's account. It's not so problematic task when you maintain CSV in format John,Appleseed,appleseed_john#mac.com that you can import in iTunes Connect:
It also kind of makes sense, that you need to fill a "what should testers test" form for external users (my company's testers), because client in most cases knows what should be tested - unlike my testers, who needs to be notified somehow what is the status of the build and what should be tested.