You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Trakt “Own app” connection requires a Client Secret, which Trakt no longer issues for new apps #1497
The Trakt "Own app (Client ID)" connection form has a Client Secret field that appears to be mandatory, but Trakt no longer issues a client secret for newly created apps. The app page on developer.trakt.tv shows "Not issued. This app signs users in with PKCE", so there is nothing to enter and no way to complete the connection with a new app.
Expected: own-app mode should work with only a Client ID (using PKCE if needed), since Trakt now treats client_secret as optional and deprecated on its /oauth endpoints.
How can we reproduce it?
Create a new Trakt app at developer.trakt.tv/apps with redirect URI urn:ietf:wg:oauth:2.0:oob, as the connection modal instructs.
Open the app page. Client Secret shows "Not issued".
In CrossWatch, go to Settings → Connections → Add provider → Trakt → Own app (Client ID).
Enter the Client ID. The Client Secret field has nothing to fill. Clicking "Connect Trakt" has no effect.
Sync Output debug log
No response
Analyzer output
No response
Additional context
Trakt's change: trakt/trakt-api#974 (client_secret is now optional/deprecated on /oauth, PKCE recommended).
Confirmation
I removed tokens, API keys, passwords, usernames, and other sensitive information.
Activity
cenodude commentedon Oct 15, 2026
its in the dev build:
ghcr.io/cenodude/crosswatch-dev:dev-dbor wait for the upcoming release.Own-app connections now use the PIN flow too.
Enter your Client ID, click Connect and approve access on Trakt.
No client secret is needed.
keldian commentedon Oct 15, 2026
Thanks that works.