-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What to test parameter doesn't seem to work #77
Comments
@lukewis: I can see the "What to test" field populated with the data I pass in to the task when uploading to "TestFlight". Do you have multiple languages that your app ships in? Please share relevant portion of the logs from your build, particularly the fastlane commands being run if you still have this issue. Thanks, |
Hi @madhurig, after reviewing some of my logs, I'm wondering if the reason I never saw this field populated is because I had checked the "don't wait for processing to complete" option. Is waiting for processing to complete required for this feature to work? |
I tried this again today and made sure I UN-checked the "skip waiting for processing" option and things worked as expected. It might be nice to add a blurb in the "info tips" for both What to Test and Skip waiting for processing to indicate that those options are mutually exclusive. |
@lukewis: Thank you, we will update the documentation. |
This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
This seems related to #47, but I can't seem to get the "What to test" feature to work correctly. No matter what string I specify, the "What to test" field in Testflight remains blank. Are there any "special considerations" for using this feature that I should be aware of?
The text was updated successfully, but these errors were encountered: