OneStore Changelog

1.4.0 comes from real releases shipped end to end through the MCP, without opening App Store Connect or the Play Console. Every blocker we hit became a check or a fix in OneStore, and RevenueCat revenue now sits next to the store stats.

• RevenueCat in OneStore: connect your account once for the whole workspace, and each app is linked to its project by bundle ID or package name. MRR, ARR, revenue, active subscribers, trials, new customers, churn, trial conversion, conversion to paying, refund rate and revenue by store and country sync every 6 hours and show up in Analytics next to the store numbers, never added to them. Your AI reads them too through get_app_metrics.
• App Store videos from the MCP: the product page header video (21:9) and the search results video (3:2). OneStore checks the file before sending it (dimensions, frame rate, duration, codec), places it on the right language of the version and follows Apple's processing.
• Submit an Apple version in one action: the submit writes What's New itself, translates missing languages, pushes screenshots and reuses the declarations (encryption, age rating) Apple already holds. Anything it can't infer is asked once, up front, and everything missing comes back as one list instead of one failure at a time.
• A complete first App Store release: copyright, App Review contact, iPad screenshots, first subscriptions submitted with the version, pending Apple agreements flagged, and Apple's real reasons when it refuses. Two new MCP actions create the bundle ID and the subscriptions (group, products, prices per country, free trial).
• A fuller Apple check: required text missing in a language (fixed in one click when OneStore has the listing), videos still processing with the time to wait, and a version pulled from review gets renumbered and resubmitted without the console.
• New languages: publishing a listing in a language the App Store didn't have yet now sends the description, keywords and links. A publish result is broken down per store and per language, with each store's exact error.
• Google Play: the review state is read straight from Google, so a published version no longer stays "in review" in OneStore. A Play refusal names the missing permission and links to the console, and a false permission error caused by an old versionCode is gone.
• Alerts and links: check_store_alerts gathers Google's review state, stability anomalies, open Apple submissions and agreements to sign. check_app_links checks that your shared links really open the app on iOS and Android.
• A more reliable MCP: two operations on the same app wait their turn instead of failing, the queue restarts as soon as the blocking operation ends, sync_app runs a real refresh, and an action is no longer marked successful while Apple is still processing the build.

In the dashboard: a RevenueCat section in Settings, the last 5 MCP actions in an app's settings with the full history and its filters on its own page, icons instead of emojis, and release notes compared with the last published version to flag text copied unchanged.

1.3.0 opens OneStore to AI assistants and makes monitoring calmer: your AI ships from a chat, you get the essentials once a week, and data from both stores comes in over its full history.

• OneStore MCP server: Claude, ChatGPT, Cursor and Codex run listings, screenshots, builds, releases, reviews and stats with 43 tools. Each connection has its own permissions, and sensitive actions wait for your approval in OneStore. Everything is explained on /mcp.
• Weekly recap email: one row per app with its icon, installs, reviews and the versions that went live that week.
• Onboarding in two paths, quick or connected, and an app can be created as a draft before any store is connected.
• Per-user notifications, translated into French and English, and reliable alert emails (one clear alert when Apple denies access to reviews, instead of raw errors every day).
• Analytics: Apple (sales and analytics) and Google ingestion rewritten over each app's full history. A metric that isn't available is shown as such instead of zero.
• Google releases: a staged rollout can be raised or halted even while it is in review, and release notes go out with each store's own language codes.
• Reliability: autosave no longer overwrites the server, a push no longer wipes the live text, unchanged screenshots are no longer re-sent on every sync, and sessions, Stripe webhooks and cross-workspace access were hardened.

The landing page was simplified too: one window with three tabs, a grid of animated features, and two pixel-art scenes with Clawd on the landing and on /mcp.

1.2.0 goes after what blocks a release: Apple submissions rejected without a clear reason, release notes missing in one language, and back-and-forth between the two consoles.

• "Publish to stores" button: OneStore fills and translates the release notes, uploads the version, then submits it, in one click.
• Apple pre-check before submission (screenshots, encryption, age rating, release notes in every language) with one-click fixes, and Apple's actual rejection reasons shown as they are.
• Open Apple version reused: if an editable version already exists in App Store Connect, OneStore renumbers it instead of failing.
• Releases page reorganised: one card per version, with both stores and their builds inside.
• An existing app can get its second store, and the status page shows Apple and Google API availability, without false credential alerts during their outages.
• Free "Translate my listing" tool (/translate-listing), interface and emails available in French and English.

Version 1.1.0 focuses on AI-assisted workflows and post-launch measurement. This release ships three capabilities for developers who already have their apps on both stores and want better tools for ongoing content management and performance tracking.

• Unified review inbox with AI-drafted replies in the reviewer's language, posted back to the right store.
• Version comparison in analytics: select any two versions and measure their impact on installs, revenue, and retention. The J+0 axis aligns both versions to their respective release dates, making performance deltas directly comparable regardless of when each version shipped.
• Free App Store & Google Play listing audit (/audit): get an ASO completeness score for any listing in under 5 seconds with no account required. AI-powered recommendations flag gaps in metadata length, screenshot coverage, and localization across all supported locales.

This is OneStore's first release to add AI to the editorial layer. Upcoming releases will extend AI assistance to metadata creation and multi-locale localization.

OneStore launched publicly on 31 May 2026 with the full sync loop: a unified ASO editor, binary delivery, team collaboration, and the infrastructure needed to manage both stores from a single workspace.

• Accounts, workspaces, and Stripe billing, with guided onboarding that connects App Store Connect (via .p8 API key) and Google Play Console (via service account JSON) without requiring any command-line access.
• Push/pull sync for metadata, screenshots, release notes, and review replies across the App Store and Google Play, write once, publish to both stores in a single action.
• Binary upload and delivery: .aab and .ipa files are processed by a dedicated Railway worker, bypassing Vercel's serverless execution limits for large file handling.
• Team roles (OWNER / ADMIN / MEMBER) with a per-action audit log, cross-store analytics dashboard, and in-app feedback.
• Legal pages (Terms, Privacy, DPA, Security), GDPR-compliant analytics consent, and a live service status board.

v1.0 establishes the core sync loop. All workspace connections made at launch remain compatible with every subsequent release.

The 0.9.3 release introduced the public-facing marketing surface ahead of the full launch, including the first tools for developers evaluating whether OneStore fits their workflow.

• Landing page with a live side-by-side preview of App Store and Google Play listings, showing real per-field character limits, localization slots, and screenshot dimensions for each store.
• OneStore vs native APIs comparison and ROI calculator, quantifying the time difference between managing App Store Connect and Google Play Console directly versus using OneStore's unified editor.
• Security disclosure page and live service status board.

The first release established the core editor: a unified interface for iOS and Android storefront metadata, with credential setup that requires no terminal, no CLI, and no developer account configuration beyond what the stores already provide.

• Unified iOS + Android storefront editor, one form covering titles, subtitles, descriptions, keywords, and release notes for both the App Store and Google Play, with per-field character-count validation against each store's limits.
• Guided App Store Connect setup using .p8 API keys: the wizard validates the key, issuer ID, and key ID against the ASC API in real time, no terminal required.