I'm using the new beta version functionality in iTunes Connect. I uploaded a build (98) to iTunes Connect, set up some internal testers and they downloaded that build.
Now I've updated the build with a new version (build 99) and that's been uploaded to iTunes Connect, but I can't see how to provoke the system into pushing this new version out to the users and their TestFlight app.
I'm set up as a tester on a couple of devices (both with my developer ID as well as with another id) and I can still only see build 98.
On the iTunes Connect screen build 98 is listed as inactive (which is correct because it has been superseded by build 99), but build 99 only says 'invite testers', but I've invited all those I want to invite.
It says that users will 'automatically receive new builds', but how long does it take? I was hoping it would be instant. Is there a way to provoke iTunes Connect into sending out the update notifications so my users can test the new version?
I'm not sure if this is a bug in TestFlight but toggle off and then on again the "TestFlight Beta Testing" switch. As soon as you do it all your internal testers should get notified of the new build.
Another option is to simply go into the new Build Details and save it.
Related
How to remove the current build from iTunes Connect where the app is in "Developer Removed from Sale" status? Also, the older version should be made "Ready for Sale". Please help me. I have unknowingly Released the version of that app.
I cannot remove the current build from iTunes Connect now. The build doesn't show up any delete button.
You have to submit a new version with a new build. It's both not possible to a) either update the build of a live version (which was on the store) nor b) to switch to an older version.
Your flow will look like this:
1) Create new version in iTunes Connect
2) Create & upload new build with fixes for this version
3) Submit to the store. If it's a critical bug fix, you might want to request an expedited app review. https://developer.apple.com/support/app-review/
Expedited App Review:
If you face extenuating circumstances, you can request the review of your app to be expedited. These circumstances include fixing a critical bug in your app on the App Store or releasing your app to coincide with an event you are directly associated with.
Urgent Bug Fix:
If you've submitted an update to fix a critical bug in your app on the App Store and you are requesting an expedited review, be sure to include the steps to reproduce the bug on the current version of your app.
Downloading beta app from testflight app gives error at the end, says "Unable to download app at this time" on all my devices.
No error is in itune connect upload. App displayed and received notification on adding new app to testflight beta. But everytime same error.
This happened to me when I wasn't using the correct provisioning profile. Very frustrating error that doesn't provide any useful info, and leaves the previous installed version of your test build in a state where it cannot be launched. After I switched my provisioning profile to 'Automatic', bumped the build number, and submitted a new version to iTunes connect I was able to download the new build.
I'm seeing a similar error. I don't know for sure, but I suspect doing things in this order may have something to do with it (this seems to mirror what emrys57 is facing).
You have issued a previous TestFlight release (download/install was working).
You then submitted that version for formal review for publication in the App Store.
While the app submission is still under review, now you uploaded a new TestFlight build with an updated version number (but did not resubmit for App Store review).
It could be that while the app is under review something prevents the download. I seem to recall reading about something like this in one of the guides, but I can't remember where off the top of my head. In my case, as an internal tester I even face the error "Unable to download app at this time", regardless of whether I already have a previous version with the same bundle ID already installed or if I don't have the app already installed (i.e., it's fully uninstalled). I wonder if an accepted App Store review will clear up the issue; it doesn't seem like a good idea to resubmit that latest build for further App Store review if the version previously submitted is what you actually want released.
In my case, for the general testing audience, I have a separate bundle ID that is exclusively for beta testing. And that version is never submitted for App Store review (the one that's slated for App Store review I only use for the purpose of smoketesting the upgrade process with internal testers). That bundle ID for beta had to go through the one-time full TestFlight external review for the initial TestFlight external beta testing. But I've been able to keep adding new versions to that beta-only bundle ID for subsequent TestFlight releases without an issue.
When I try to validate my build using xcode 6 GM release I am getting this error.
Error : itunes store operation failed no eligible software found. Make sure this software is owned by your developer organization.
Can anybody here suggest some solution?
Probably you're using a different AppleID for iTunes Connect than for Developer Portal. You can use such a workaround:
Export archive in Organizer (Save for iOS App Store Deployment) and then use Application Loader (Xcode > Open Developer Tools > Application Loader) to upload it to iTunes Connect. It allows you to input credentials
Try using application loader. I had the same issue with Xcode and using the loader worked for me.
I had this same issue and it resolved by making sure it logged in with the correct account.
When the modal dialog asks to select a "Development Team to use for provisioning"
Choose "View Accounts..." make sure the correct account shows in the "Apple IDs" list.
If the Apple ID is not there, use the plus sign to add a new Apple ID account.
Close the Accounts screen.
On the "Development Team to use for provisioning" use the drop down to select the account you just added, select Choose and then Validate and it will work.
I had this problem too and as some commenters point out, the reason was the different Apple ID used on itunesconnect vs. xCode.
I was able to solve it on xCode adding my itunesconnect Apple ID on xCode preferences and making sure it is selected during validation. The right team was not enough for me, it has to be the right team on right account.
I'd recommend ensuring that the account in question has been invited as both the apple developer and iTunesConnect account. This should resolve the problem. You may have to go into Preference in Xcode and re-add the account.
That happened to me with many projects , so just try to re choose your provisioning profile and code signing identity in the build settings for your project
Try using Xcode6. Xcode6.1 GM seed's iOS SDK version is now beta 8.1. You can't submit a beta binary to iTunes Store.
To publish an IPA
I go to publish -> Distribute ad hoc/enterprise -> and then I publish the app
However, I can only publish an IPA with a distribution profile, this means I don't get any debugging on my phone.
How can I publish distributed profiles on test flight?
Solved it.
For ANYONE having this problem (i.e. being able to use a development certificate instead of production), follow the following steps.
---- Downgrade your ITunes VERSION to 11.1.5, otherwise it will complain when you try to do an iTunes sync that iTunes doesn't have enough memory!! (Titanium need to fix this!)
1) Download 11.1.5 from here http://mac.filehorse.com/download-itunes/4050/
2) Go to Applications, and Delete itunes... If you get an error message saying something like "This app is require by OSX" just go to Get Info > Sharing & Permissions > Everyone ... it has to say Read & Write.
3) Install the itunes you just downloaded
4) Open it (You might need to hold you "alt" key while opening so you can create a new library (11.2 changed something in your library that is not compatible with 11.1.5)
Then publish app USING ITUNES SYNC. (this is the ONLY way to get the development .IPA)
The app will now be in your app folder within iTunes.
You will now be able to upload your app onto test flight - a development version using a development APNS certificate. Also because it is in development mode, means that you will be able to see all error problems either through Xcode or Iphone configuration. If you publish an ad-hoc system based on production, it will not print out any Ti.App.Info etc commands in the device console.
Hope this helps! :)
First off let me be clear. I have several iOS devices. On the devices that have 7.0.6 I have no issues. When I updated one of the devices to 7.1 I'm having an issue. Let me explain.
On the iOS device that has 7.1 I navigate to the workbench URL and then I go to Manage applications and select install. I then get this message "Cannot install applications because the certificate for >ip address< is not vald. This process works on devices that have 7.0.6. I'm assuming there are issues with the new iOS update.
Now I did some searching and I found something that said there's an issue when trying to download an app from a HTTP site, so I changed a Web Reports setting (found in Eclipse Preferences -> Test -> Performance Test Reports -> Web Reports) to "Security is required to access reports". Thus it changed the port number to "8443". I then navigate back to the workbench URL using the https : // ip:port and try to install the app again. This time it just says Cannot open.
Any ideas on this?
Here is a workaround to be able to test with iOS 7.1
1) Get the zip of instrumented Application from developer or other who can run rtwBuildXcode.sh on a Mac and who has the source code for Application. [RmotXXXXXXXX.zip file]
2) Use RTWec "Add Application to list..." button and brows to the zip to "import" it into RTWec.
3) UnZip the zip and use iTunes (for Windows) "Add File to Library..." menu to navigate in zip folder to the instrumented iOS Device application [XXXXXXXX.ipa in “instrumented/iOS Device” folder]
4) Plug in iDevice to Windows using USB, select the App, click associated "Install" button, then "Sync" iTunes.
5) Now test as usual...
Thanks
MTWW in Worklight 6.1.0.0 and 6.1.0.1 (to be released, soon) does not support iOS 7.1.
Work is under way to provide support in a future release of Worklight.