@daemux/store-automator 0.10.21 → 0.10.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -5,14 +5,14 @@
|
|
|
5
5
|
},
|
|
6
6
|
"metadata": {
|
|
7
7
|
"description": "App Store & Google Play automation for Flutter apps",
|
|
8
|
-
"version": "0.10.
|
|
8
|
+
"version": "0.10.22"
|
|
9
9
|
},
|
|
10
10
|
"plugins": [
|
|
11
11
|
{
|
|
12
12
|
"name": "store-automator",
|
|
13
13
|
"source": "./plugins/store-automator",
|
|
14
14
|
"description": "3 agents for app store publishing: reviewer, meta-creator, media-designer",
|
|
15
|
-
"version": "0.10.
|
|
15
|
+
"version": "0.10.22",
|
|
16
16
|
"keywords": [
|
|
17
17
|
"flutter",
|
|
18
18
|
"app-store",
|
package/package.json
CHANGED
|
@@ -63,25 +63,39 @@ if [ $FASTLANE_EXIT -ne 0 ]; then
|
|
|
63
63
|
echo "::warning title=Google Play Draft App::First manual release required. See job summary for instructions."
|
|
64
64
|
if [ -n "${GITHUB_STEP_SUMMARY:-}" ]; then
|
|
65
65
|
cat >> "$GITHUB_STEP_SUMMARY" << 'SUMMARY'
|
|
66
|
-
## :warning: Google Play Draft App —
|
|
66
|
+
## :warning: Google Play Draft App — Closed Testing Required (Internal Testing Is NOT Enough)
|
|
67
67
|
|
|
68
|
-
Metadata and screenshots were uploaded by CI but **could not be saved** because the app
|
|
68
|
+
Metadata and screenshots were uploaded by CI but **could not be saved** because the app is still in **draft status**. This is a [Google Play API limitation](https://developers.google.com/android-publisher/edits) — all API edits are rejected until the app exits draft status.
|
|
69
|
+
|
|
70
|
+
**"Draft" is an app-level status**, not a release-level one. Internal testing bypasses Google review entirely, so it **cannot** transition your app out of draft. You must submit to **closed testing** (or higher) to trigger Google's review and remove draft status.
|
|
69
71
|
|
|
70
72
|
### One-time setup steps:
|
|
71
73
|
|
|
72
74
|
1. Go to [Google Play Console](https://play.google.com/console) → Select your app
|
|
73
|
-
2. **Dashboard** → Complete all required setup tasks
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
75
|
+
2. **Dashboard** → Complete **all** required setup tasks in the checklist:
|
|
76
|
+
- **Store listing** — app name, descriptions, screenshots, app icon, feature graphic
|
|
77
|
+
- *Copy-paste the values from the **Store Listing** table below, then re-run CI after setup to auto-upload future changes.*
|
|
78
|
+
- **App Content** declarations — **all** of the following:
|
|
79
|
+
- Privacy policy
|
|
80
|
+
- Data safety
|
|
81
|
+
- Content rating questionnaire
|
|
82
|
+
- Target audience and content
|
|
83
|
+
- Ads declaration
|
|
84
|
+
- App access (instructions if login required)
|
|
85
|
+
- Government apps declaration
|
|
86
|
+
- Financial features declaration (if applicable)
|
|
87
|
+
- Health apps (if applicable)
|
|
88
|
+
- **Pricing and distribution** — countries and free/paid
|
|
89
|
+
3. **Submit to Closed Testing** (not internal testing):
|
|
90
|
+
- Go to **Testing → Closed testing** → Create a track if needed → **Create new release**
|
|
91
|
+
- The AAB was already uploaded by CI — select it, add release notes
|
|
92
|
+
- Click **Review release** → **Start rollout to closed testing**
|
|
93
|
+
- This submits the app to **Google review**
|
|
94
|
+
4. **Wait for Google review approval** — typically 1-7 days for new apps
|
|
95
|
+
- :information_source: *New personal developer accounts (created after Nov 2023): Google requires **20+ testers** for **14+ continuous days** of closed testing before you can request production access.*
|
|
96
|
+
|
|
97
|
+
### After Google approves the review:
|
|
98
|
+
The app permanently exits draft status and all API operations (metadata, builds, screenshots) work automatically. Re-trigger the CI workflow after approval.
|
|
85
99
|
SUMMARY
|
|
86
100
|
|
|
87
101
|
# --- Append store listing table (read from metadata files) ---
|