`docs/tesla-support-ticket.md`

37 lines
# Tesla Developer Support — "No policy rules" / app bound to foreign API record

**Account:** steveabramsdesigns@gmail.com
**Product:** Charge & Explore (chargeandexplore.com) — third-party Fleet API app (read-only: openid, offline_access, vehicle_device_data, vehicle_location)

## Problem
User OAuth (`/oauth2/v3/authorize`) fails at the consent step with:
> "Something went wrong. Try again later" — **"No policy rules"**

Reproduced repeatedly in a real browser. Reference IDs:
- 7b149f64-c52c-42c4-b34d-7b558cb726cb
- c658ed90-...
- caf17ec0-258f-4eba-b6bc-8105b2c75b27

## Root cause (from GET /oauth2/v3/clientinfo)
Both of our apps have `default_api_id = 8513`, but API record 8513 is **owned by a different developer's app** and has **no policy**:

| our app | app.id | client_id | default_api_id |
|---|---|---|---|
| Steven Abrams | 72246 | 9e4d27da-c154-4630-85fe-1b216f8901b0 | 8513 |
| 8226          | 72462 | 370f23c4-4fba-403b-b11c-c42e6a09902e | 8513 |

Record 8513:
- `owner_app_id`: 71851  (name: "Millie Vehicle Assistant" — NOT ours)
- `policy_id`: null  ← this is the "No policy rules" failure
- `identifier`: "https://fleet-api.prd.na.vn.cloud.tesla.com https://fleet-api.prd.eu.vn.cloud.tesla.com" (space-joined NA+EU)

Partner registration is complete (GET partner_accounts/public_key verifies on NA; our public key matches).
The dashboard does not expose a way to change region/audience, so we cannot obtain a unique, self-owned API record.

## Request
Please either:
1. Assign our apps (72246 and/or 72462) their **own** API audience record with a valid consent policy, **not** the foreign shared record 8513; or
2. Enable us to select a **single region (North America only)** so our app gets a dedicated NA audience record with its own policy.

Our redirect URIs / origins are already correctly configured (e.g. https://chargeandexplore.com/auth/tesla/callback).