App Store Connect refused uploads of apps embedding WebmasterIDStoreKit 1.3.0 with ITMS-91056: a comment inside the module's privacy manifest contained "--", which XML forbids. iOS 1.3.1 and webmasterid_flutter 0.4.1 correct the comment and nothing else.
iOS SDK 1.3.1 (Swift Package Manager) and webmasterid_flutter 0.4.1 (pub.dev). Android SDK 0.3.0 is unchanged.
The privacy declarations are identical to 1.3.0's: Purchase History and User ID, linked to the user, not used for tracking, purpose analytics; no tracking; no required-reason API.
No runtime, API, consent or delivery change. Apps that embed only WebmasterID were not affected.
The native SDKs now deliver events on their own, the same way on iOS and Android: about 5 seconds after the first queued event, when the app goes to the background, and after the next launch for anything left. An iOS app no longer needs to call flush() to be measured.
iOS SDK 1.3.0 (Swift Package Manager), Android SDK 0.3.0 (webmasterid.com/sdk/maven) and webmasterid_flutter 0.4.0 (pub.dev). Same public channels, no private repository.
One armed delivery about 5 seconds after the first queued event; later events join it and never postpone it. The app goes to the background: delivered at once, best effort.
After the next launch, anything an earlier launch left is delivered once the consent decision is in force — no flush(), no call from your app.
WebmasterID now measures iOS and Android apps: public SDKs, consent-first events and five Apps reports beside your website reports, in the same workspace.
iOS SDK 1.2.0 from Swift Package Manager, Android SDK 0.2.0 from the Maven repository at webmasterid.com/sdk/maven, and webmasterid_flutter 0.3.0 from pub.dev. No private repository or access token.
Apps reports in the dashboard: Overview, Events, Conversions, Retention (beta) and Attribution, next to the Web reports.
Consent first: nothing is queued or sent until the app passes the user's decision, and the server refuses advertising identifiers.
The rollup release: a real MCP HTTP server, workspace-scoped multi-tenancy, Stripe-backed billing, full onboarding, and the new operator identity surfaces.
Real MCP HTTP server at /api/agent/mcp with workspace-scoped Bearer auth and ten read-only tools.
Workspace switcher + operator profile in the dashboard sidebar; copyable user IDs on /settings/account.
Stripe billing with three plans (Pro / Agency / Business), signature-verified webhooks, and a customer portal.
Endpoint-visibility row, three-step quick-start wizard, server-status panel, recent-activity widget, and an in-page verify-connection tester on /settings/mcp.
Endpoint-visibility row at the top of /settings/mcp with a one-tap copy button on the full MCP URL.
Three-step Quick Start wizard: generate API key → add to Claude → verify. Step 1 ticks green when the workspace already has an active key.
Server-status panel — operational / degraded / unconfigured pill, recent success-rate %, last-checked timestamp. Honest 'n/a' when there are no events; no fabricated uptime.
Production MCP HTTP endpoint at /api/agent/mcp with ten read-only tools, Bearer auth via the api_keys table, plan gating, audit logging, payload caps, and a per-key rate limit.
POST /api/agent/mcp — JSON-RPC 2.0 over HTTP. Methods: initialize, tools/list, tools/call.
Ten read-only tools: sites, summary, recent events, bot intelligence, AI referrals, top pages, recommendations, repo mappings, execution sessions, plan status.
Workspace-scoped Bearer auth against the api_keys table; revoked keys rejected and audited.
Welcome email auto-fire, the api_keys infrastructure, /settings/mcp documentation, /getting-started richer post-first-event page, and three Claude/MCP SEO landing pages.
Welcome email auto-fires from /api/auth/signup. Delivery failure never blocks signup; production never falls back to logging plaintext tokens.
Migration 0017 adds the api_keys table — sha256 hash at rest, six-char prefix, plaintext shown once, workspace-scoped + RBAC-gated.
Closed-allow-list dashboard route registry, maturity-aware sidebar rendering, and route-health diagnostics. The substrate the rest of M53 / M54 / M55 builds on.
M52-core route registry — single source of truth for every dashboard route's maturity, RBAC permission, and sidebar visibility.
Sidebar items render based on maturity (stable / beta / coming-soon hidden / broken / experimental hidden) so the chrome reflects what the operator can actually use.
Route-health diagnostics surface broken / experimental routes in the dashboard's diagnostics view rather than 404-ing operators.