# Google-play-deploy step just started failing

**URL:** <https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079>\
**Category:** Tooling Issues\
**Created:** [May 23, 2019, 1:32am UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079 "2019-05-23T01:32:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rwalberg](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/rwalberg/32/751_2.png) [@rwalberg](https://discuss.bitrise.io/u/rwalberg)\
**Post date:** [May 23, 2019, 1:32am UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079/1 "2019-05-23T01:32:03Z")

</div>

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

```auto
- 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.

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [May 23, 2019, 11:00am UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079/2 "2019-05-23T11:00:17Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [May 23, 2019, 11:48am UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079/3 "2019-05-23T11:48:39Z")

</div>

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](https://github.com/bitrise-io/bitrise-steplib/pull/1989)

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

---

<div class="post-metadata">

**Author:** ![rwalberg](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/rwalberg/32/751_2.png) [@rwalberg](https://discuss.bitrise.io/u/rwalberg)\
**Post date:** [May 23, 2019, 12:20pm UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079/4 "2019-05-23T12:20:55Z")

</div>

Thanks for the fix!

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [June 22, 2019, 12:20pm UTC](https://discuss.bitrise.io/t/google-play-deploy-step-just-started-failing/9079/5 "2019-06-22T12:20:59Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.