[BUG] Active Apple Max 20x subscription still recognized as Pro

I upgraded from the Free plan to Max 20x, the payment was made but it didn't take effect, and clicking the upgrade button on my computer says I already have a subscription. 🤬

Additional affected case: Apple Pro → Max 5x upgrade remains Pro across iPad, claude.ai, and Claude Code

I am experiencing a closely matching issue with Max 5x, observed on October 2–3, 2026. I am adding the details here to help investigate the shared subscription-recognition failure.

Upgrade path and account checks

1. My existing Claude Pro subscription was purchased through Apple and worked on this Claude account for about one week.
2. I upgraded through iPad Settings → Apple Account → Subscriptions → Claude, rather than the upgrade button inside the Claude app.
3. Apple's subscription page now shows one active Claude Max 5x – Monthly subscription. There are not separate active Pro and Max entries.
4. The iPad's Media & Purchases Apple account matches the account used for the purchase.
5. The Claude account email matches across the iPad app, claude.ai, and Claude Code. I did not switch Claude accounts for the upgrade.

Actual behavior

• The official Claude iPad app still shows Pro.
• claude.ai still shows Pro, with the subscription identified as purchased via the iOS app.
• Claude Code still recognizes the same account as Pro after a successful fresh claude.ai authentication.
• Repeated taps on Restore Purchases in the iPad app produce no visible response: no success message, no error, and no plan change.
• A fresh authenticated account-profile check also reports Pro rather than Max. This observation suggests the mismatch is not limited to a stale label in the local CLI; it does not establish where the Apple transaction-recognition flow failed.

Troubleshooting already completed

• Updated the Claude iPad app to the version offered by the App Store and retried restoration.
• Restarted and reinstalled the iPad app, signed into the same Claude account, and retried restoration.
• Refreshed the web account and completed a fresh official Claude Code login.
• Checked for an API key or alternative API-provider override on the Mac; none was found.

All three official products still show Pro. I do not have a second iOS device available for a cross-device restore test. I have not captured StoreKit transaction logs, so I cannot tell whether restore fails in the app, receipt delivery, or backend entitlement mapping.

Expected behavior

An active Apple Max 5x upgrade should be recognized for the same Claude account across the iPad app, claude.ai, and Claude Code. Restore Purchases should provide an observable result or an actionable error when recognition fails.

Environment

• Claude Code: 2.1.282 (Claude Code), verified with claude --version on October 3. I am reporting the actual installed version, not claiming it is the latest release.
• Mac: macOS 26.5.2.
• Web: Chrome, claude.ai.
• Mobile: official Claude app on iPad; initial app version 1.260921.19, subsequently updated and reinstalled. The exact post-reinstall app build and iPadOS version have not been recorded.
• Authentication: official claude.ai account login; Apple-billed subscription.

Requested investigation

Could the team investigate the Apple Pro → Max upgrade-recognition path, particularly upgrades initiated in iPad system subscription settings, and the silent Restore Purchases behavior? If this needs a different engineering team, please route the report or identify the appropriate technical reporting channel.

I already have a private Get Help conversation with Anthropic Support. Account identifiers, Apple order information, and purchase evidence will remain in that private support channel.

It's really terrible. I encountered this problem today too! I don't know how to solve it!

I'm hitting the same issue. I upgraded from Pro to Max through the Apple App Store, Apple shows Max as active and the Pro portion was refunded, but my Claude account still shows Pro (and Free on the backend, according to support). Restore Purchases, force-closing the app, and signing out/in did not help. I opened a support ticket 3 days ago and it's still in the human queue. Is there any known fix or timeline?