fastlane: [pilot] fails with only internal testers
New Issue Checklist
- Updated fastlane to the latest version
- I have read the Contribution Guidelines
Issue Description
pilot fails claiming there are no testers but there are - they are internal ones though.
$ pilot list
[00:39:51]: Login to iTunes Connect (xxxxx)
[00:39:58]: Login successful
+---------+----------+-----------------------------+
| Internal Testers |
+---------+----------+-----------------------------+
| First | Last | Email |
+---------+----------+-----------------------------+
| A | AA | a@foo.com |
| B | BB | b@foo.com |
+---------+----------+-----------------------------+
+-------+------+-------+
| External Testers |
+-------+------+-------+
| First | Last | Email |
+-------+------+-------+
+-------+------+-------+
Complete output when running fastlane, including the stack trace and command used
[00:33:13]: Successfully uploaded the new binary to iTunes Connect
[00:33:13]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
[00:33:13]: Waiting for iTunes Connect to process the new build
[00:33:45]: Waiting for iTunes Connect to finish processing the new build (1.0.0 - 25)
[00:34:16]: Waiting for iTunes Connect to finish processing the new build (1.0.0 - 25)
[00:34:48]: Waiting for iTunes Connect to finish processing the new build (1.0.0 - 25)
[00:35:20]: Waiting for iTunes Connect to finish processing the new build (1.0.0 - 25)
[00:35:53]: Waiting for iTunes Connect to finish processing the new build (1.0.0 - 25)
[00:36:23]: Successfully finished processing the build
[00:36:23]: You can now tweet:
[00:36:23]: iTunes Connect #iosprocessingtime 3 minutes
[00:36:24]: Successfully set the changelog for build
[00:36:24]: Distributing new build to testers
[00:36:25]: Variable Dump:
[00:36:25]: {... <snip> ...}
[00:36:25]: This train could not be activated because there is no testable build in the train. You cannot start testing without any tester. Please add tester(s) first and try again.```
Configuration Files
Fastfile:
pilot(changelog: notes)
Environment
fastlane version (run fastlane -v): fastlane 1.91.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? no
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? chruby
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 42 (22 by maintainers)
@mark-anders glad it works for you - but see https://github.com/fastlane/fastlane/issues/5066#issuecomment-225151732
A few more data points:
TL;DR - I think it has to do with
use_legacy_build_api: truerather than a lack of external testers.I just began using fastlane yesterday and ran into the same thing and spent hours doing builds to no avail. Like the others, I was using
gym(use_legacy_build_api: true)based on getting some error message early on that told me to do so.While the fastlane error I received was :
This train could not be activated because there is no testable build in the train.and going to iTunes Connect showed the build as “Missing Beta Entitlement”.As a test, I tried to build and submit using XCode and first received an email that said:
After turning bit code off in the project and turning off “send bitcode” during the upload process, I was able to get the build to be available and I then had to go through the web api to get it sent out to the internal testers.
I tried one more fastlane build and the same thing happened as before.
After reading this thread in its entirety, it occurred to me to set
use_legacy_build_api: false.Amazingly, it worked.
I’m still not sure what I changed that allowed me to build without the flag set to true, but everything worked and the build was sent out to testers with no manual steps.
Hope that helps!