Play Store Listing: Update for Wear app

[AliSoftware]

Why?

The Play Store Listing was initially rejected when we asked to enable the Wear app because the full description didn't mention the Wear app.

How?

We updated the listing manually in Play Store Console and resubmitted it, but for those changes to stick:

• We have to change the source of truth, which is fastlane/metadata/android/en-US/full_description.txt, otherwise during the next production upload, fastlane would re-update the listing with the content of that file and remove the changes we manually made.
• We have to update the PlayStoreStrings.pot file accordingly (via bundle exec fastlane update_play_store_strings), so that the new full description starts getting translated in GlotPress for other locales

What's Next

Once this PR is merged into release/19.2, we need to backmerge release/19.2 into trunk so that the updated PlayStoreStrings.pot reaches trunk and gets picked up by the WPCOM job to be sent to Glotpress for translation.

Testing: only during Production build submission

During the next submission of the production release (cc @ThomazFB), we need to ensure that the en-US Play Store Listing shown in Play Store Console will still contain the added mention of the Wear app (i.e. that it hasn't been reverted by fastlane updating the metadata with an older copy).

Additionally, if translations for the new Play Store Listing copy have already been done in GlotPress, they should be downloaded during the call to finalize_release. We might thus want to check that the Play Store Listing for those locales in Play Store Console has been updated accordingly too once the CI have created the Play Store Release for Production Track after that call.

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 19.2. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce-Wear Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce-Wear Android
	Platform	⌚️ Wear OS
	Flavor	Jalapeno
	Build Type	Debug
	Commit	9d11644
	Direct Download	woocommerce-wear-prototype-build-pr11820-9d11644.apk

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Commit	9d11644
	Direct Download	woocommerce-prototype-build-pr11820-9d11644.apk

[AliSoftware]

@ThomazFB I took the liberty to change the wording from WearOS to Wear OS because that's how they spell it in the Guidelines and I feel like misnaming it WearOS might make the Google reviewers trigger-happy on rejecting it 😅

[iangmaia]

I got confused seeing this as I was pretty sure we removed it, but it seems it came back in a merge (fc13979). Thanks for noticing and removing it 🙇

[AliSoftware]

Yeah I was sure we already removed it as well so was confused why it was still there 😅 Nice catch finding the reason being a merge, that explains it 👍

[AliSoftware]

Update: since Google Play requires that we mention Wear OS in all our localized Play Store Listing too (and not just the English one), we'll have to update the fastlane/metadata/android/{locale}/full_description.txt of all the supported locales to include them in the submission.

Our plan is to:

• Update those localized .txt files in this PR, using Google Translate or ChatGPT to generate the translation of the added paragraph
• Call fastlane to upload the content of those .txt files to Google Play as the localized Play Store Listings, then submit them for review (ping me once you're at that stage)
• If the listings get rejected, make the necessary adjustments in the .txt files and iterate
• Once the new listing gets approved, ensure the .pot is still up-to-date with any potential change we'd have made to the English .txt to make Google happy, then merge this PR to release/19.2 then backmerge release/19.2 all the way to trunk, so that the PlayStoreListing.pot file gets picked up and uploaded to GlotPress
• Once the new original copy appears in GlotPress (which can take some time depending on when the cron job importing the .pot runs), optionally copy our updated translations from the .txt to GlotPress for each locale, so that they're in sync.
  • Otherwise there's a risk that either the content of the .txt files will be overwritten by the old translations from GlotPress, or that our automation will skip that locale because the translation would be marked status: fuzzy (and not status: current) in GlotPress and would not be exported… which would risk fastlane defaulting to the English translation for those locales (instead of keeping our manually-updated one)

[AliSoftware]

FYI, I just ran the following fastlane command from this PR's branch to upload the new content of all the fastlane/metadata/android/*/*.txt files to Google Play:

bundle exec fastlane run upload_to_play_store package_name:com.woocommerce.android \
  skip_upload_metadata:false \
  skip_upload_changelogs:true \
  skip_upload_images:true \
  skip_upload_screenshots:true \
  skip_upload_apk:true skip_upload_aab:true \
  json_key:$HOME/.configure/woocommerce-android/secrets/google-upload-credentials.json

I then confirmed that the new copies sent for submission were now the expected ones in Google Play Console (i.e. matching the .txt files, i.e. that the fastlane command worked as expected), so now we wait for Google to hopefully approve them.

[AliSoftware]

Next Steps once Google approves the current listing (🤞 )

• Merge this PR to release/19.3
• Backmerge release/19.3 to trunk, so that PlayStoreStrings.pot gets sent to GlotPress
• Once new English copy appears in GlotPress(†), copy the translations we created from the .txt files as translations for the new copy in GlotPress (so that .txt files content won't be overwritten by GlotPress content during finalize_release)
• Prepare a PR to modify fastlane/metadata/android/en-US/full_description.txt once again for 19.3, to add the mention of complications in 19.3's future Play Store Listing, but don't merge it until after 19.2 has been submitted
• After the submission of 19.2 and before the code freeze of 19.3, merge the PR adding mention of complications to the en-US/full_description.txt, so that it's included in the .pot and send to GlotPress for translation during 19.3's complete_code_freeze and that human translations will start translating the new copy.
• Optionally ping Team Global in #i18n Slack to ask them to relay to our translation contractors the need for those to be translated in all locales in time for 19.3's submission.

cc @ThomazFB

---

(†) Depending on the time at which this lands in trunk, we might miss the time at which the cron job runs and might wait a couple of hours until the next run happens; so it might take some time for the new original to appear in GlotPress