Develop

.github/workflows/release.yml

@@ -40,13 +40,13 @@ jobs:
       - uses: actions/setup-node@v7.0.0
         with:
           node-version: "22"
-      - name: Validate shared Microsoft Store and Google Play descriptions
+      - name: Validate shared Microsoft Store and Google Play listings and images
         run: |
           node --test scripts/tests/store_listings.test.mjs scripts/tests/google_play_listings.test.mjs
           node scripts/store_listings.mjs > store-listings-preview.json
       - uses: actions/upload-artifact@v7.0.1
         with:
-          name: store-listings-en-vi
+          name: store-listings
           path: store-listings-preview.json
 
   # Generate release notes from commits
@@ -455,7 +455,7 @@ jobs:
           name: windows-msix
           path: ${{ env.PROJECT_DIR }}/build/windows/msix/*.msix
 
-      - name: Create Partner Center submission archive
+      - name: Locate MSIX for Partner Center submission
         shell: pwsh
         run: |
           $version = "${{ needs.generate-release-notes.outputs.version_name }}"
@@ -465,20 +465,11 @@ jobs:
             throw "MSIX package not found in ${{ env.PROJECT_DIR }}/build/windows/msix"
           }
 
-          $stageDir = Join-Path $env:RUNNER_TEMP "msix-store-submit"
-          New-Item -ItemType Directory -Force -Path $stageDir | Out-Null
+          # partner_center_msix.mjs builds the submission ZIP (package + listing images).
+          "PARTNER_CENTER_PACKAGE_PATH=$($source.FullName)" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
+          "PARTNER_CENTER_PACKAGE_FILE_NAME=CBFileHub-$version-$msixVersion.msix" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
 
-          $packageFileName = "CBFileHub-$version-$msixVersion.msix"
-          $storePackagePath = Join-Path $stageDir $packageFileName
-          Copy-Item -LiteralPath $source.FullName -Destination $storePackagePath -Force
-
-          $archivePath = Join-Path $env:RUNNER_TEMP "CBFileHub-$version-$msixVersion-store.zip"
-          Compress-Archive -LiteralPath $storePackagePath -DestinationPath $archivePath -Force
-
-          "PARTNER_CENTER_PACKAGE_ARCHIVE=$archivePath" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
-          "PARTNER_CENTER_PACKAGE_FILE_NAME=$packageFileName" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
-
-      - name: Submit MSIX to Microsoft Store for automatic publishing
+      - name: Submit MSIX, listings and images to Microsoft Store for automatic publishing
         shell: bash
         env:
           PARTNER_CENTER_TENANT_ID: ${{ secrets.PARTNER_CENTER_TENANT_ID }}
@@ -490,6 +481,7 @@ jobs:
           PARTNER_CENTER_COMMIT_SUBMISSION: "true"
           PARTNER_CENTER_TARGET_PUBLISH_MODE: "Immediate"
         run: |
+          # Waits for Partner Center to finish processing the commit and fails on CommitFailed.
           SUBMISSION_ID="$(node scripts/partner_center_msix.mjs submit)"
           echo "Partner Center submission committed for automatic publishing after certification: $SUBMISSION_ID"
 

README.md

@@ -447,7 +447,7 @@ Generate promotional artwork from the captured screenshots:
 python scripts\make_promo_images.py
 ```
 
-The generated artwork is written to `screenshots/promo/desktop/`, `screenshots/promo/mobile/`, `screenshots/promo/tablet7/`, and the matching Vietnamese folders under `screenshots/promo/vi/`.
+The generated artwork is written to `screenshots/promo/desktop/`, `screenshots/promo/mobile/`, `screenshots/promo/tablet7/`, the matching Vietnamese folders under `screenshots/promo/vi/`, Turkish and Chinese desktop promos under `screenshots/promo/tr/` and `screenshots/promo/zh/`, and the text-free Microsoft Store hero art in `screenshots/promo/store/`. Use `--desktop-only --languages tr,zh` to regenerate only some languages.
 
 Render the English/Vietnamese Torrent dialog images with sample data from `cb_file_manager/`:
 
@@ -459,7 +459,7 @@ This opt-in widget capture writes `screenshots/features/torrents/en/` and `vi/`.
 
 ### Microsoft Store and Google Play descriptions
 
-Both stores use the same concise English/Vietnamese descriptions in [`store/listings/`](store/listings/). Edit each language's `.txt` once; its bullet points also generate Microsoft Store features. The sibling `.json` holds the short description and Google Play language code. CI checks character limits and uploads a `store-listings-en-vi` preview. MSIX submissions apply the text in Partner Center; AAB submissions include it in the same Google Play edit as the app bundle. See the [content guide](store/README.md).
+Both stores use the same concise descriptions in [`store/listings/`](store/listings/), one per app language (English, Vietnamese, Turkish, Simplified Chinese). Edit each language's `.txt` once; its bullet points also generate Microsoft Store features. The sibling `.json` holds the short description, Google Play language code and the Microsoft Store screenshots/hero art. CI checks text limits and image sizes and uploads a `store-listings` preview. MSIX submissions apply the text and images in Partner Center; AAB submissions include the text in the same Google Play edit as the app bundle. See the [content guide](store/README.md).
 
 ## Testing
 

README.vi.md

@@ -141,4 +141,4 @@ flutter test --no-pub tool/capture_torrent_screenshots_test.dart --dart-define=C
 
 Ảnh được ghi vào `screenshots/features/torrents/en/` và `vi/`; luồng này dựng widget, không mở ứng dụng desktop hay đọc thư viện torrent của người dùng.
 
-Microsoft Store và Google Play dùng chung mô tả ngắn gọn tiếng Anh/Việt tại [`store/listings/`](store/listings/). Chỉ cần sửa file `.txt` của từng ngôn ngữ; các dòng gạch đầu dòng cũng tạo danh sách tính năng cho Microsoft Store. File `.json` bên cạnh chứa mô tả ngắn và mã ngôn ngữ Google Play. CI kiểm tra giới hạn ký tự, tạo artifact `store-listings-en-vi`, rồi cập nhật nội dung khi submit MSIX/AAB. Xem [hướng dẫn nội dung](store/README.md).
+Microsoft Store và Google Play dùng chung mô tả ngắn gọn tại [`store/listings/`](store/listings/), mỗi ngôn ngữ của app một bộ (Anh, Việt, Thổ Nhĩ Kỳ, Trung giản thể). Chỉ cần sửa file `.txt` của từng ngôn ngữ; các dòng gạch đầu dòng cũng tạo danh sách tính năng cho Microsoft Store. File `.json` bên cạnh chứa mô tả ngắn, mã ngôn ngữ Google Play và danh sách ảnh chụp/hero art cho Microsoft Store. CI kiểm tra giới hạn ký tự và kích thước ảnh, tạo artifact `store-listings`, rồi cập nhật nội dung (và ảnh với MSIX) khi submit MSIX/AAB. Xem [hướng dẫn nội dung](store/README.md).

cb_file_manager/pubspec.yaml

@@ -214,3 +214,5 @@ msix_config:
   capabilities: internetClient, privateNetworkClientServer
   file_extension: .torrent
   protocol_activation: magnet
+  # UI languages; must match the Store listings in store/listings/.
+  languages: en-us, vi-vn, tr-tr, zh-cn

docs/guides/02-microsoft-store-submission-guide.md

@@ -55,12 +55,13 @@ Push a release tag or run the release workflow manually.
 
 The pipeline will:
 
-1. Validate the checked-in English/Vietnamese listing text and run mocked submission tests
-2. Upload `store-listings-en-vi`, a shared JSON preview of the exact text for Microsoft Store and Google Play
-3. Restore the `.pfx` from `MSIX_CERT_BASE64`, build and sign the Windows MSIX
-4. Upload the `.msix` as the `windows-msix` artifact and prepare its submission archive
-5. Update the Store draft's `en-us` and `vi-vn` descriptions/features and upload the package
-6. Commit for certification with `targetPublishMode: Immediate`; Microsoft Store publishes automatically after approval
+1. Validate the checked-in listing text and images (`en-us`, `vi-vn`, `tr-tr`, `zh-cn`) and run mocked submission tests
+2. Upload `store-listings`, a shared JSON preview of the exact text and images for Microsoft Store and Google Play
+3. Restore the `.pfx` from `MSIX_CERT_BASE64`, build and sign the Windows MSIX (its manifest declares the same four languages)
+4. Upload the `.msix` as the `windows-msix` artifact
+5. Update every listing's description, features, screenshots and hero art, then upload one ZIP with the package and any changed images
+6. Commit for certification with `targetPublishMode: Immediate` and wait until Partner Center has processed the commit; the job fails on `CommitFailed` and prints Partner Center's errors/warnings
+7. Microsoft Store publishes automatically after certification (this can take up to a few business days; the public listing keeps the old text and images until then)
 
 The release workflow always sets `PARTNER_CENTER_COMMIT_SUBMISSION=true` and
 `PARTNER_CENTER_TARGET_PUBLISH_MODE=Immediate`. Repository variables with those
@@ -102,36 +103,55 @@ For a local MSIX build submitted manually in Partner Center:
 4. Complete store listing fields
 5. Submit for certification
 
-## 6. Maintain English and Vietnamese Descriptions
+## 6. Maintain Listing Text and Images
 
-Microsoft Store and Google Play share these version-controlled descriptions:
+Microsoft Store and Google Play share these version-controlled listings, one per
+app UI language:
 
-| Language | Full description and feature bullets | Short description / locale metadata |
+| Language | Full description and feature bullets | Short description / locale / images |
 |---|---|---|
 | English (`en-us`) | [`store/listings/en-us.txt`](../../store/listings/en-us.txt) | [`en-us.json`](../../store/listings/en-us.json) |
 | Vietnamese (`vi-vn`) | [`store/listings/vi-vn.txt`](../../store/listings/vi-vn.txt) | [`vi-vn.json`](../../store/listings/vi-vn.json) |
+| Turkish (`tr-tr`) | [`store/listings/tr-tr.txt`](../../store/listings/tr-tr.txt) | [`tr-tr.json`](../../store/listings/tr-tr.json) |
+| Simplified Chinese (`zh-cn`) | [`store/listings/zh-cn.txt`](../../store/listings/zh-cn.txt) | [`zh-cn.json`](../../store/listings/zh-cn.json) |
 
-Keep both languages concise and aligned. Lines beginning with `- ` generate
+Keep all languages concise and aligned. Lines beginning with `- ` generate
 Microsoft Store's features automatically, so feature text is maintained once.
-The `.json` files hold `descriptionFile`, `shortDescription` and
-`googlePlayLanguage`; product capabilities and platform limits live in the `.txt`.
+The `.json` files hold `descriptionFile`, `shortDescription`,
+`googlePlayLanguage` and `microsoftStoreImages`; product capabilities and
+platform limits live in the `.txt`. The same locales are declared in the MSIX
+manifest (`msix_config.languages`), so Partner Center lists them as supported
+package languages; a test keeps both lists identical.
 
 `scripts/store_listings.mjs` validates required locales, shared description length
-(1–4,000 characters), short descriptions (1–80 characters), and feature bullets
-(1–20 entries, at most 200 characters each). The shared limit fits
-[Google Play](https://support.google.com/googleplay/android-developer/answer/9859152?hl=en)
-and Microsoft Store. `scripts/partner_center_msix.mjs submit` validates the text before
-authenticating or modifying a draft, then merges only `description` and `features`
-into `listings[locale].baseListing`. The data shape follows the
+(1–4,000 characters), short descriptions (1–80 characters), feature bullets
+(1–20 entries, at most 200 characters each) and images (PNG type, dimensions per
+image type, count, 50 MB, 200-character captions). `scripts/partner_center_msix.mjs submit`
+validates everything before authenticating or modifying a draft, then merges
+`description`, `features` and the managed `images` into
+`listings[locale].baseListing`. The data shape follows the
 [Microsoft Store submission API](https://learn.microsoft.com/en-us/windows/uwp/monetize/manage-app-submissions).
 
-Existing titles, images, policy/support URLs, terms, release notes, platform
-overrides and unrelated languages remain intact. If Vietnamese is new, its
-listing is seeded from the existing English Store metadata before applying the
-Vietnamese text. An initial Store listing with a registered title must already
+Images are managed per image type: for each type listed in a locale's
+`microsoftStoreImages` (by default `Screenshot` and `PromotionalArt16x9`), the
+existing images of that type are marked `PendingDelete` and the checked-in ones
+are added as `PendingUpload`, in order. Uploaded file names contain a content
+hash, so when Partner Center still reports the same files nothing is re-uploaded.
+Image types not listed (for example a manually uploaded `Icon` or Xbox art) stay
+untouched. Set `PARTNER_CENTER_UPDATE_IMAGES=false` to update only text.
+
+Existing titles, policy/support URLs, terms, release notes, platform overrides
+and unrelated languages remain intact. A new language listing is seeded from the
+existing English Store metadata (without English images) before applying its
+text and images. An initial Store listing with a registered title must already
 exist. `PARTNER_CENTER_LISTINGS_DIR` can select another content directory; release
 CI explicitly uses `store/listings`.
 
+After the commit, the script polls the submission status
+(`PARTNER_CENTER_COMMIT_POLL_SECONDS`, default 30;
+`PARTNER_CENTER_COMMIT_TIMEOUT_SECONDS`, default 1800). `CommitFailed` fails the
+job with Partner Center's error list; a timeout only emits a warning.
+
 Preview and test locally from the repository root without Store credentials or
 network requests:
 
@@ -141,8 +161,8 @@ node --test scripts/tests/store_listings.test.mjs scripts/tests/google_play_list
 ```
 
 PR/push CI validates the content. Release jobs wait for the same checks and
-upload a `store-listings-en-vi` preview containing payloads for both stores.
-Google Play's AAB job prepares an uncommitted edit with both descriptions and
+upload a `store-listings` preview containing payloads for both stores.
+Google Play's AAB job prepares an uncommitted edit with every description and
 passes its ID to `upload-google-play`; that action uploads the AAB and commits
 the descriptions with the release. Failed updates/uploads discard the edit.
 Internal app sharing skips listing updates because it has no store release edit.
@@ -167,4 +187,4 @@ flutter test --no-pub tool/capture_torrent_screenshots_test.dart --dart-define=C
 
 This is an opt-in widget renderer. It does not launch the Windows app, scan user
 data, contact trackers or download payloads. README screenshots are independent
-of existing Store image assets, which this description update preserves.
+of the Store images, which come from `screenshots/promo/` (see section 6).