how to install previous version on TestFlight - testflight

I want some people install latest version and others install a previous version, so I set the permissions accordingly in hope that user can be automatically directed to the version. However, testFlight always point to latest version and other users will get an error say "You don't have access"... Anyway from device to install a previous version?

Just follow the steps to install previous version.
1 - Go into testflight
2 - Tap on the app for which you want to get the previous version.
3 - After tapping you will see the detail of it and at the bottom you will see the 'Previous Versions' button.
4 - Tap on 'Previous versions.'
5 - A list will be displayed of all the previous version from where you can install any of the previous version.

I don't know about splitting versions between testers automatically, but you can download older versions of an app from TestFlight.
On the permissions page for a particular build (from the dashboard, select builds, then select the build of the app you're after—hit the more button next to the latest build to reveal the others) there's a section titled Share this Build that provides a direct download link. If it were me, I'd eschew TestFlight's automatic notifications system in this case and send notifications manually, including the appropriate direct link for each tester. If your delivery system allows it, set the email reply address to be the one found on the feedback page for the build and testers can still send feedback by replying to your (now custom) announcement email.

I can able to install the previous versions of builds in TestFlight. We can upgrade and downgrade to any old/new versions seamlessly
Steps to follow,
In TestFlight iOS app
Tap on the app for which you want to get the previous version.
After tapping you will see the detail of it and at the top, you will
be able to see the 'Previous Versions' button.
Tap on 'Previous versions.'
A list will be displayed of all the previous version from where you
can install any of the previous version.
check the screenshots for more clarify

It seems that today is no way to install older builds(

Just updating this as TestFlight has changed.
From TestFlight, where it shows your App, touch the app icon or tap anywhere in that row on the left side. That will reveal App Information page.
On the App Information page look for Previous Builds. If you tap that it will show all of your builds and you can pick one.
Happy coding. :-)

Related

App store connect operation error asset validation failed

Hi I got this error while uploading archive with xCode.
Does anybody had this error before ? Thanks
I exported IPA from Organizer and used Transporter app which finally helped me to see the issues.
Install the "Transporter" app from the MacOS app store.
From Xcode's organizer, select your archive and press "Distribute App"
Instead of "Upload", select "Export" and proceed as usual.
Drop the exported .ipa into the transporter and press "Deliver".
In case your current app version is already in approved but not released status, you cannot use the same version number. You must go higher version.
In my case, it was the version number. Once App is published on App Store, to push update use a higher version number e.g 1.0.1 (if in production we have App version 1.0.0).
Ways to fix this:
Check if the new version is greater than the previous version.
In the issue navigator, you just need to apply the changes recommended by Xcode. Start clicking the issue to see the recommendations, it will prompt automatically.
Download Transporter, to see the details of the error.
You need to export appName.ipa from Xcode
Upload the appName.ipa in the Transporter
I had the same problem. Even though validation continued to fail, I eventually just tried clicking on the "Distribute App" button in Organizer. That also failed, but gave me a much more helpful error message. Turned out that the issue had nothing to do with Assets. I added a redirect uri scheme that contained an invalid character. I fixed that, and the validation succeeded.
I was getting the same error but when i tried to upload the app, it gives me the detailed info, i was using the same version for the latest build which apple doesn't accept. I just changed the version number for that build and able to upload the app successfully.
There is something wrong in your assets. Either the app icons are not correct/missing OR you need to check your images.
I am also encountering this error with an Ionic project. Even though my build failed Xcode validation, I tried to distribute it to the App Store anyway, and received the following error, which provided more detail:
Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'xx.xxxxx.xxxxxxxx'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. With error code STATE_ERROR.VALIDATION_ERROR.90713 for id 97fb5968-9248-4336-a622-e015181dd333
In Xcode I examined the app/app/assets and under AppIcon the 1024x1024px icon was missing. I added a file, generated a new build, and subsequently was able to Archive, validate and deploy.
This error message occurs by different situactions, to address your problem you can distribute your app directly to get more detail error message.
I got same message because I overrite my ios folder with a older one,
issue fixed by replacing a ios folder with a new one.( you can run "flutter create newProject" to get it)
The XGA-sized icon for the App Store cannot have an Alpha channel (and only that one - all other assets are OK with Alpha channels... go figure). It's one of the many, many unnecessary quirks Xcode / AppStore Connect have that drive me nuts.
In my case, the app was approved for release with the same version number. So I have to cancel the release to validate and distribute the app with the same build number. Or you can change the build number.
You can cancel the release in AppStore connect. It's a blue button on the top of the page.
Found that the problem was with the assets like it's said in the error. Don't know if it's a new requirement by apple or if it's an old one but you cannot have an alpha channel in your assets. So I just edited all my assets and deleted the alpha channels and then it worked ! Hope it help ;)
I just changed the iOS build version 3.6.3(92) to 3.6.4(92) from runner and it works fine. So, try changing your build version properly.
In my case two mistakes, I did
The first one is the store version and Xcode build versions are not matching
The second one is something wrong with our assets. (Either the app icons are not created/missing or other images)
If you have already deployed (to the app store) the same version of the app you are attempting to validate for TestFlight, you will see this error message. The new TestFlight release must have a succeeding version number in comparison to the latest version of the app, if it is already on the app store.
Remove alpha channel only for the icon "App Store iOS 1024pt" (Assets.xcassets) and you will fix the issue "App Store Connect Operation Error - Asset validation failed"
In my case there were some errors with the icons in Runner/Assets.
I just deleted those images was shown in the image bellow and everything works fine.
If your app has "Approved" state, but it is not released yet - you can not use same version number.
You have two options:
increase version number (not just version code);
cancel release (nothing will be deleted, just your approval will be cancelled), validate and distribute app, submit for approval.
i have found a solution to this problem,
you need to double check that, you have check the iphone or Ipad checkbox on xcode , but you have to upload the Iphone icons or ipad icons, one of them is missing.
I got the same error message when I tried to validate my app, so I tried to distribute the app and I got a full error message, in my case was:
Invalid Provisioning Profile Signature. The provisioning profile included in the bundle 'netoloboapps.com.mensagensProntas' (Payload/Runner.app) cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. (Expired profile signing certificate.) For more information, visit the iOS Developer Portal. With error code STATE_ERROR.VALIDATION_ERROR.90165 for id b493faef-bcf5-4732-995d-f7c6609a0354
My problem was a expired signing certificated. So here's the tip, check out the complete error message and see the source of the problem.
I got the same error too. I contacted Apple and received the following reply:
Thank you for contacting Apple Developer Program Support.
We are sorry to hear that an error message is displayed in Xcode and that you are unable to distribute the app.
We have checked our available resources and found that none of them correspond to the error you have inquired about.
We have identified a guide that may be related to the error you are experiencing and are sending it to you below.
Validate an archive of your app
If you need more information, please consider visiting the Apple Developer Forums, where you can discuss development issues with Apple engineers and other developers.
Developer Forums
https://developer.apple.com/forums/
For feedback on Xcode or to report a bug, please use the Feedback Assistant.
Developer Feedback Assistant
https://developer.apple.com/jp/bug-reporting/
We apologize for not being able to help you with your inquiry, but we hope the above resources will be of assistance.
I found same issue, but i dont see error reporting anywhere. I build my app with Flutter and i try edit version in pubsbec.yaml. and i edit too version app in xcode. then my app success validate and distribute
In my case I was messing some AppIcon resolution images for iPad. Also I made sure that the version and the build are set correctly.
1- Go to the icons folder
/myapp/ios/App/App/Assets.xcassets/
2- Open the photo
3- Click File, then choose Export
4- Deselect from Alpha and replace the image
This should be applied to all icons
I got the error when the WatchApp uses the healthkit api but not adds description into info.plist.
I use the Transporter App to upload, it shows the error summery.
For Flutter Developer, Change the version number. From Example in pub.yaml, 1.0.0+4 to 1.0.1+5.
If this is a new project and you are uploading to the App Store for the first time, you must have app icons set in the Assets folder.
This is why it could say "Asset validation failed".
The only one solution helps me is transfer app to other AppStore account.
Before uploading the app to the app store first we need to validate the app to check whether the app has any errors or not.
Another advantage of validating app is it’ll provide detailed error.
I found 3 scenarios on which this error will occur:
=> if we are not updating the version name
=> Alpha channel in all the images of Assets.xcassets/ should be removed (you can download alpha channel remover for that)
=> if we have selected Ipad in general settings Portrait, landscape right , landscape left should be enable if we have given just portrait mode we will face the same error.
Happy coding :)

TestFlight: Testers are not getting notified of new builds

Since Apple moved to their new and improved TestFlight website, none of my internal or external users are receiving push notifications or emails when I make a new build available for testing.
These are testers who previously were getting push and emails with each new build.
If the tester goes to the TestFlight app on their device, they do see the new build is available for update there.
I see a couple threads about this in the Apple Developer forums but nobody seems to know how to work around this problem:
https://forums.developer.apple.com/thread/76020
https://forums.developer.apple.com/thread/76131
Anyone here found a workaround for this problem?
when submitting a build for beta approval, uncheck 'automatically notify' in lower left corner. then after beta is approved for external testing, click 'notify testers' in upper right corner. if i recall next time i do this, i'll include screenshots.
this solution is from #boozedog, it fixed the issue for me, and i am submitting #boozedog's comments as an answer. the text of his comment:
"
The Automatically Notify checkbox appears in the bottom left of the dialog box when you submit the build to beta approval on the iTunes Connect website. Make sure you clear that checkbox. And then, after the beta approval is complete, go back in to that build in iTunes Connect website and you should see an action button in the top right corner "Notify Testers."
"

Application's new version uploaded on iTune with internal testing enabled not appearing on Testflight app

I have released one version on my Application on iTune and is in process to release second one. Now I have uploaded the the .ipa file of the application and switching on for internal testing. But the application is not appearing on Testflight app of internal tester. I am uploading the .ipa file through Xcode 6.1 and also trying with Xcode 6.3.
When you upload the app on iTunes, then you can not add new IPA in existing version of app.
Make sure that for your app you have turned the switch ON for TestFlight Beta Testing.
Once done with that go to Internal Testers tab and check the internal testers from the list and invite them. Thats it! Hope it helps :]
Cheers!
If you've uploaded a build for the next/new version, you should see it at the top of the list of builds under the "Prerelease" menu for your app.
Assuming you're Build is in the list, check the "Internal" column for that build. If it says "Invite Testers", then that build is not yet active. What you probably need to do then is click the build number and make sure all the fields are filled out - especially "What to Test" - and then click the Save button. When you go back to the Builds list, it should now say "Active (30 Days Left)" under Internal. And should show up for testers in the TestFlight app.
I've noticed that sometimes I need to go through this process for a new build (even on a version I've already been testing) and sometimes I don't. I haven't found the pattern but it's tripped me up several times.

Re-submitting app after it's been accepted

I've submitted an app that got accepted in it's 1.0 state, but I haven't published it because we had to wait for the next version.
Now I have the 1.01 version that I would like to submit, with a build number of 5 (the previous one on the store was 3), which I did using the following :
Archive
Distrubution to the app store
Submit to the app store
Submit to the appstore Complete, with a big green V.
5 hours after I still don't see my build or version on my itunes connect page, it still shows the old page as it always did.
Did I do something wrong? Must I publish before updating? I really wish we wouldn't' have to. Have I lost a day of review queue?
Thanks for your help
EDIT: Here is what I had at the end of my Xcode archive routine :
Yet nothing shows on the itunesconnect side, several hours afterwards.
Here is my build section in the version tab, which shows the version I uploaded two months ago. :
Did you prepare a new version to send to apple review team? I mean in the itunes connect webpage.
EDIT: You have to reject your old binary that is "ready to publish" or if you want publish it ("ready for sale"). Then you have to re-upload your new binary, creating a new version tab. You can follow this steps to upload your new binary:
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html

The Automatic Device Provisioning options have gone since upgrading to Xcode 4.3.1?

I'm making a release for the first time since upgrading to Xcode 4.3.1.
While having a look to see if my profiles were up to date I also noticed that automatically updating device provisioning is no longer displayed (i.e. where it should appear in this screen shot doesn't appear for me How to add a new device to a team provisioning profile) but it used to there before I upgraded.
Is this something that has been removed with 4.3.1? If not, why is it no longer appearing for me?
xCode 4.3 now has the Refresh link on the far right, and there is no longer a checkbox for "Automatic Device Provisioning," at least that I can find.
Just clicking the Refresh link on the right is all that's needed to update the app's provisioning profile from developer.apple.com.
I'm not seeing it either. I'm having lots of troubles with code signing and ad hoc distribution, so I'm trying to follow Apple's (recently updated!) step by step instructions. However, they don't appear to match the options I have in XCode. It appears that "automatic device provisioning" has been silently removed as an option, or my Organizer install is corrupted.

Resources