Overview

GPD ID Resolver maps human-friendly names to IDs used by other gpd commands. It covers package names, track IDs, version codes, tester groups, and monetization IDs (products, subscriptions, base plans, and offers). Use when commands require IDs or exact values.

How This Skill Works

Supply a known name or slug and let the resolver guide you to the corresponding ID by querying the relevant gpd commands (e.g., tracks, status, testers, monetization, permissions). Always pass the app package with --package to guarantee deterministic results, and use --all on list commands to avoid missing items.

When to Use It

• When you know the app and need the exact package name for deterministic results.
• When you need track IDs or version codes for a given track.
• When you need tester group IDs for a specific track.
• When you need monetization IDs (products, subscriptions, base plans, offers).
• When you need permission or app-grant IDs (permissions users, app grants).

Quick Start

1. Step 1: Identify the app package name (e.g., com.example.app) and pass --package.
2. Step 2: Run relevant list/get commands to resolve IDs you need (tracks, status, testers, products, subscriptions, permissions).
3. Step 3: Use the retrieved IDs in subsequent gpd commands.

Best Practices

• Always pass --package for deterministic results.
• Use --all on list commands to avoid missing items.
• Use get commands (e.g., get sku123, sub123) to fetch exact IDs.
• Validate region codes and price micros when migrating prices in base plans/offers.
• Append --pretty for debugging, then switch to default JSON for production.

Example Use Cases

• gpd publish tracks --package com.example.app
• gpd publish status --package com.example.app --track production
• gpd monetization products list --package com.example.app
• gpd monetization subscriptions get sub123 --package com.example.app
• gpd permissions users list --developer-id DEV_ID

Frequently Asked Questions