v147 · PWA · Origin Migration

PWA Origin Migration Checklist

Enter your current and target origins to generate a live checklist for the current migration handshake: destination migrate_from, old-origin allow_migration, optional migrate_to, and redirect-safe install_url.

Origin pair

Current origin

Target origin

Behavior

Old origin association file authorizes the destination with allow_migration: true Old app URLs redirect before Chrome can refresh the old manifest Include a non-redirecting install_url for the old app

Generated migration files

migration requirements

# Target origin manifest:
{
  "id": "https://files.example.com/app/",
  "start_url": "https://files.example.com/app/index.html",
  "migrate_from": [{
    "id": "https://drive.example.com/",
    "behavior": "suggest",
    "install_url": "https://drive.example.com/install.html?noredirect=true"
  }]
}

# Old origin /.well-known/web-app-origin-association:
{
  "https://files.example.com/app/": {
    "allow_migration": true
  }
}

# Optional old origin manifest:
{
  "id": "https://drive.example.com/",
  "migrate_to": {
    "id": "https://files.example.com/app/",
    "install_url": "https://files.example.com/install.html?from=legacy"
  }
}

# Requirements:
# 1. Both origins must share the same eTLD+1 (example.com)
# 2. Both origins must be HTTPS
# 3. The destination manifest must declare migrate_from
# 4. The old origin association file must allow the destination app id
# 5. Redirecting old routes need an install_url Chrome can fetch

references

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗