Supply should detect the current release status and set it to draft when the app has never been released

[lacostej]

New Issue Checklist

• [x] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x]I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

If you've never published your app, and are publishing to your draft internal track, if you haven't explicitly set the release_status to draft the upload will fail with

[!] Google Api Error: Invalid request - Only releases with status draft may be created on draft app.

Supply options default to "COMPLETED" and this is used when updating the track.

Because of this, one is forced to add release_status: 'draft' as argument to upload_to_play_store, and then remove that argument when the app is finally published.

It would be better if fastlane was fetching the current status from the Play store instead of using the default COMPLETED status. That way we wouldn't have to modify the commands before publishing the app, and after publishing it.

[nathanfallet]

I have the same problem. Actually, what is the difference between having the "draft" status or "completed" status when releasing to "internal"? (we're not distributing the app to production)