New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supply: Publishing Draft Google Play Listing fails if App Content not filled out yet #20630
Comments
Is there a way one may set the required "privacy policy" and "data safety declaration" sections through supply command? |
Code error what? That there isn't a way to set data safety or there isn't even an API for it? |
@Madisenes: Where do you see:
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.
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. |
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 Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Where is that Google api documented, and maybe someone may be able to check that out and set a way to set that? |
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. |
New Issue Checklist
Issue Description
When publishing Google Play Listing information via supply during the draft stage (release_status=draft), we have not added information yet in the App Content section.
The Google Play APIs have started rejecting updates to Google Play Listing if these sections are not completed. I think this is really good to have these errors early if the app has already been published in the past and this is a new update. It will keep the app from being rejected (and then it is harder to update since the update has to be done manually).
Is there a way that these App Content checks can be skipped during draft or a parameter to control it?
Here are two examples:
Command executed
SUPPLY_METADATA_PATH=play-listing
SUPPLY_VERSION_CODE=4
SUPPLY_JSON_KEY=/secrets/google_play_store/webonary_sil/playstore_api.json
SUPPLY_TRACK=production
SUPPLY_SKIP_UPLOAD_APK=true
SUPPLY_RELEASE_STATUS=draft
SUPPLY_AAB=/artifacts/Teke_Dictionary-1.0.aab
SUPPLY_PACKAGE_NAME=org.sil.tyx
fastlane supply
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: