Google-play-deploy step just started failing

#1

We cut weekly builds. Today we ran our workflow and it failed in the google-play-deploy step with this error:

- ApkPath: 
unknown app path extension in path: /bitrise/deploy/Pagerduty-5.50(6194).apk\n, supported extensions: .apk, .aab
no app provided

So we looked at the workflow and saw that the “App file path” is set to $BITRISE_APK_PATH\n$BITRISE_AAB_PATH. It looks like this step just updated to 1.6.0. If we revert to 1.5.1 it works.

The confusing part is that “App file path” is a field that is new to 1.6.0. Version 1.5.1 has “APK or App Bundle file path” and the value we had was just $BITRISE_APK_PATH. So it seems like the auto-upgrade from 1.5.1 to 1.6.0 determined what the value of this new field should be and got it wrong. The step says multiple values can be used, separated by \n or |, but the step doesn’t seem to accept that after we tried both.

This is the second time this year a change to a Bitrise step has broken one of our workflows.

0 Likes

Deploy to Google Play v1.6.0
#2

Hi @rwalberg!

Thank you for your report! We are really sorry about the inconvenience this may have caused you. Would it be possibly for you to include the URL related to the build where you’ve found that this is occurring?

0 Likes

#3

Hi again!

Just wanted to let you know that the issue should be fixed as per this merge: https://github.com/bitrise-io/bitrise-steplib/pull/1989

Sorry for the issue again, and thanks for your help!

1 Like

#4

Thanks for the fix!

The build was https://app.bitrise.io/build/4a4ba1e7f76b4033 in case you still need to see it.

1 Like