# Google Play deploy v1.2.2

**URL:** <https://discuss.bitrise.io/t/google-play-deploy-v1-2-2/1475>\
**Category:** Changelog\
**Tags:** step\
**Created:** [April 18, 2017, 8:32am UTC](https://discuss.bitrise.io/t/google-play-deploy-v1-2-2/1475 "2017-04-18T08:32:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tamaspapik](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/tamaspapik/32/251_2.png) [@tamaspapik](https://discuss.bitrise.io/u/tamaspapik)\
**Post date:** [April 18, 2017, 8:32am UTC](https://discuss.bitrise.io/t/google-play-deploy-v1-2-2/1475/1 "2017-04-18T08:32:39Z")

</div>

In the new version([1.2.2](https://github.com/bitrise-steplib/steps-google-play-deploy/releases/tag/1.2.2)) the issue of accepting different file sources is fixed. Now you can use `file://`, `http://`, `https://` or any local path in `service_account_json_key_path`.

At the same time this release fixes the issue:

> <https://github.com/bitrise-steplib/steps-google-play-deploy/issues/19>
>
> This change https://github.com/bitrise-steplib/steps-google-play-deploy/pull/10/…files#diff-91d8d269a1c9bd3631ddb04b80b01c4eL64 seems to break the key input. Previously local files in the format \`./path/to/file\` were accepted, but right now only \`file://./path/to/file\` is accepted.
> 
> If possible we should allow the \`./path/to/file\` specification too.