Hello Ron, SDP team; I hope I’m not duplicating this post.
*I have a problem understanding how to migrate my apps on Google Play - as forewarned by Google. Has anyone tried it successfully?
I can’t seem to find those features as instructed in step 4 “remove inactive Wear OS app bundles and APKs from your default track” !?
If I were to contact their support team, I’m sure they will confuse me even further.*
Their instruction is:
If you currently have Wear OS apps that you want to continue distributing on Google Play, you must migrate Wear OS releases from the default track to “Wear OS Only” tracks.
You can migrate releases to “Wear OS Only” tracks from May to the end of August, 2023. During this period, you can continue to roll out Wear OS releases via the standard track. From September, Wear OS releases on default tracks will still serve users, but you won’t be able to update them.
To migrate your release:
- Open Play Console, go to the Publishing overview page, and search for the release you want to migrate to the “Wear OS Only” track.
- Note: You can also open the production or testing track page directly and select your release there.
If your release contains a Wear OS app bundle, you’ll see a notification at the top of the page about changes to Wear OS releases. Click Create a Wear OS track under the notification.
Choose one of the following options:
- Copy testers, countries, and app bundles from existing tracks: Testers, countries, and app bundles will be copied from your existing testing and production tracks. You’ll still be able to make changes. App bundles won’t be copied for tracks where you have a staged rollout in progress. To copy app bundles, finish your staged rollouts before continuing. If you’re an API user you’ll need to update your integration to use the new track ID.
- Don’t copy testers, countries, and app bundles: If you choose this option, you’ll need to add this information when preparing your Wear OS release.
- Click Create tracks.
After creating a “Wear OS Only” release track, remove inactive Wear OS app bundles and APKs from your default track, and publish a new release without the Wear OS app bundle. From this point, you can manage your Wear OS releases and users separately to your mobile or other form factor releases
After you create dedicated Wear OS release tracks, you’ll no longer be able to use the existing API to release Wear OS app bundles or APKs using your default track. You must update your integration to use the new Wear OS track IDs.
Source: Manage Wear OS Release