beta_ipa activates wrong version/build

[YuukiHogo]

Instead of activating newest build in currently testing version (at least same as uploading) it enables testing of top of list build/version. I.e. I have two version branches - 2.1 which is beta version and 2.0 version which is stable but needs testing of features before release. Uploading 2.0.5 version package activates disabled 2.1 testing.

In other words deliver must search for version same as uploaded and activate same build as uploaded package. If its hard to do, better to activate testing of top build of currently active for testing version.

[KrauseFx]

I know this feature is not 100% completed, since I haven't used the Testflight Beta Testing service from Apple yet.

The implementation can be seen here: itunes_connect.rb:285

The method put_build_into_beta_testing! takes care of selecting the build.

[fatuhoku]

Ah, I was going to write an issue about why the --beta option is not listed in --help. Is it because this is an incomplete feature?

[KrauseFx]

Since I'm currently working on this: to distribute a beta build for internal users, you don't have to do anything on the iTunes Connect frontend, right? It's enabled by default.

[YuukiHogo]

You need to enable testing for specific version. I think it will be best to
enable testing for uploaded version if there is no test-enabled version and
leave it as is otherwise.
28 янв. 2015 г. 21:08 пользователь "Felix Krause" notifications@github.com
написал:

Since I'm currently working on this: to distribute a beta build for
internal users, you don't have to do anything on the iTunes Connect
frontend, right? It's enabled by default.

—
Reply to this email directly or view it on GitHub
#31 (comment).

[KrauseFx]

Check out the latest version: http://www.krausefx.com/blog/deliver-the-missing-api-for-apples-new-testflight

This should solve this issue 👍

[fastlanebot]

This issue was migrated to fastlane/fastlane#2459. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀