Testflight beta testers won't get build mails? - ios

I used to send builds from testflight using Apple's beta testflight. From 1 week my testers won't get emails regarding new build. They have checked in testflight app also but they can't find the builds. Can somebody help me?
Note: I have submitted the app to apple for testflight. It was accepted.

Automatically we got all build mails. There may be issue in apple server or something else.

Related

IOS Build not vivible in Testflight Builds

I have got builds in Activity log, and can upload them to the Apple Store, but I'd like to beta test first, with a few of my friends.
When I go to testflight, there are no builds vissible in my Version 1.1, while they are visible in Activity.
Hopefully anyone an explain why I can't see my builds in TestFlight.
Thanks in advance

How to release testflight beta version to external users?

Having submitted a beta version of my IOS App trough Itunes Connect and Testflight to INTERNAL users, and selected it for testing to EXTERNAL users, it displays "waiting beta app verification" (from Internal users) and I don't know how to release the app for EXTERNAL User. (see pict enclosed).
It did worked on past version but I don't know how ... times, upload from Internal users, approval from them (but don't know how).
Need to re-test then submit my app quickly, any help welcome !
NOTE : Apple displays help on old itune connect versions, and don't see where this can be done. See here
Apple says:
Upload a build for the app. See Uploading a Build for an App.
Add App Description and What to Test to the build. This step is optional for releasing your builds to internal testers, but required
when submitting your app to Beta App Review for external testing. See
Add Metadata for your Prerelease App.
Distribute the app to internal testers.
Submit the app for Beta App Review, and distribute it to External users.
You need to have every build reviewed from apple for distribution to external testers.
I'm not sure how it worked earlier, but for now
All builds distributed to external testers must pass through an Apple review. While these reviews do not fall into the same queue as those submitted for App Store release, they can take time.
In other words, you have to use button "submit for beta app review" ;)
You can find guides here: Ray Wenderlich or kyleclegg.com

TestFlight error "Your request couldn't be completed"?

I'm testing an iOS App using TestFlight.
I have already successfully tested 8 Build pre-release but now it is not working anymore.
I have upload the built and it has been approved by Apple, invitations to external testers has been sent and properly received, but when they open TestFlight and try to download the App the download stops just before the end and an alertView says:
Your request couldn't be completed
NOTES:
I have tried the download on different devices but none has worked.
TestFlight is incrementing installation count also if none download has been completed.
I have upload the built today in the morning.
Found solution.
Latest XCode version changed the default build code signing identity to Developer, when it should be Distribution to work with TestFlight.
While it throw any error while uploading, it's the one causing the problem.
Just change it and it will work again

Adding testers using iTunesConnect TestFlight

I have been developing apps for iOS using Adobe Air SDK and have been using testflightapp.com for adding testers. But now that testflightapp.com has been moved, I am having issues adding testers through iTunesConnect test flight.
I upload the app to iTunesConnect using Application loader app.
But even after uploading the app, I am not able to invite testers. Also the provisioning profile is a newly created so it should be with beta entitlement.
In the build details the Internal Testing and External Testing is in processing state for more than 3 days.
iTunesConnect does not show any errors/warning for this build. What should I do to invite testers?
Have you followed these instructions for setting up your app descriptor xml correctly?
http://www.flashdeveloper.co/post/99200413877/enabling-testflight-testing-in-itunes-connect-for
Use following link to do that-
https://developer.apple.com/library/prerelease/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html
Here is a link that explains everything in simple words.It was really helpful to me.
Hope this helps

Testflight build on Appstore

I want to upload my Testflight build to apple Appstore so that i can get the crash logs from users and fix them before releasing the next builds.
But i am not sure if i can get the logs from app on Testflight from Appstore build.
On Testflight it is mentioned that we can use the Testflight to get the crash logs from Appstore build as well. But i want to make sure that i will get as much crash logs as i can on Testflight.
I tried the same thing on my own by uploading a build on Testflight and than installing the build on my iPad which i uploaded on the testflight.
But i never recieves any logs on testflight for my build.
But if i Install the same build from Testflight than only i get the logs on testflight.
so i am bit confused if Testflight logs actually works on the Appstore build as well.
If anyone has done this earlier please guide..
I can confirm that this indeed works. I've used this just yesterday with my App during it's launch.
Steps I followed:
Creative an archive of the project.
Submit to the App Store using this Archive.
Create an Ad-hoc build (.ipa file) using the exact same Archive.
Upload the Ad-hoc build to Testflight. It should automatically detect the DYSM for this.
Once you're live on the App Store, and if the app crashes, you'll see it's symbolicated crash report on Testflight (under that particular build of the app).
So make sure you use the same archive, same build number, etc. and you'll be good to go.
I would highly recommend you to use Bugsense https://www.bugsense.com/ to get the crash logs. Its free version is good enough for most app. If you are willing to pay, with a few simple steps, it can help you to symbolize the crash logs (that are hard to understand) to become readable.

Resources