Supply: Publishing Draft Google Play Listing fails if App Content not filled out yet about fastlane

[Luke-SF]

Is there a way one may set the required "privacy policy" and "data safety declaration" sections through supply command?

[Luke-SF]

code error

Code error what? That there isn't a way to set data safety or there isn't even an API for it?

[chrisvire]

@Madisenes: Where do you see:

this error message tells you how to fix the problem: by making an HTTPS call, instead of HTTP.

The error message is indicating that "privacy policy" and "data safety declaration" sections have to be filled out prior to publishing. This is a change in behavior. We have always been able to publish a DRAFT before filling out the "App content" section.

@Luke-SF:

Is there a way one may set the required "privacy policy" and "data safety declaration" sections through supply command?

I do not believe that the Google Play Store APIs provide this. It would be great if we could automate the updating of the "App content" section.

We have worked around this by changing our procedures to fill out the "App content" section when we are creating the App Store entry.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[Luke-SF]

@Luke-SF:

Is there a way one may set the required "privacy policy" and "data safety declaration" sections through supply command?

I do not believe that the Google Play Store APIs provide this. It would be great if we could automate the updating of the "App content" section.

We have worked around this by changing our procedures to fill out the "App content" section when we are creating the App Store entry.

Where is that Google api documented, and maybe someone may be able to check that out and set a way to set that?

[dmsherazi]

To resolve this, the Data Safety Declaration needs to be manually completed within the Play Console. Once that's done, this should prevent the issue from appearing in Fastlane.