Repository navigation
Playtomic connector: login returns 403 APP_ATTESTATION_REQUIRED from a home connection #1498
Description
Description
Setting up the Playtomic connector from the store fails at Check and install, with "Playtomic did not accept these credentials." The underlying response is a 403 with status APP_ATTESTATION_REQUIRED.
This looks like a new problem rather than the datacenter block described in the guide:
- It's a JSON response, not an HTML page, and the request came from a home broadband connection with no proxy.
- PR Unlist the Playtomic connectors #1042 recorded a 401 JSON response from a home connection on 12 Oct 2026, and the guide updated on 19 Oct doesn't mention a device check. Playtomic may have added this since then, but I can't confirm that.
- I couldn't find an existing issue for this error.
Steps to Reproduce
- Run the self-hosted quickstart (
docker-compose.quickstart.yml) on a home connection. - Open
/connectors/storeand pick Playtomic. - Enter a Playtomic email and password, then click Check and install.
Expected Behavior
The connector logs in and installs, or reports a credentials error if the login details are wrong.
Actual Behavior
The login is refused with the 403 below, so the connector can't be installed. I made one attempt, with the full Playtomic connector. I haven't tried Playtomic (Lite), but its docs describe the same login, so I'd expect the same result.
Connector Type
Playtomic (catalog connector)
Deployment Method
Docker Compose
Version
helpcodeai/anythingmcp:latest, pulled on 3 Nov 2026 (I didn't check the exact version inside the image)
Relevant Logs
Request failed with status code 403:
{"localized_message":"We couldn't verify your device. Please update the app to the latest version or try again later.","status":"APP_ATTESTATION_REQUIRED"}
Environment
- Mac mini (M1), macOS 26.3
- OrbStack 2.2.5, running the amd64 image under Rosetta
Questions
- Can you reproduce this from a home connection?
- Does the connector still have a permitted way to log in, or should its docs and listing be updated to say it no longer works?
Activity
github-actions commentedon Nov 3, 2026
👋 Hi @andypieroux, thanks for opening your first issue on AnythingMCP!
A maintainer will triage this within ~48h. To help us help you faster:
⭐ If AnythingMCP has been useful to you, a star helps others find it.
helpcodeai commentedon Nov 4, 2026
Thanks for the clear report. I can reproduce it.
The Playtomic login endpoint now answers 403
APP_ATTESTATION_REQUIREDto every request, even with a made-up email and password, and from a normal office connection too. So it is not your credentials and not your network. Playtomic now asks for a proof that the request comes from their official mobile app. A server cannot give that proof, and we will not try to get around it.This affects both catalog connectors, Playtomic and Playtomic (Lite), because both sign in the same way. On our Cloud there has been no successful Playtomic call in the last two weeks either.
What happens next: I will update the connector page and the setup hints so they say clearly that the login is blocked by Playtomic for now, and I will take the connectors out of the store until there is a way to sign in that Playtomic allows. If Playtomic publishes a partner or club API, we will build on that instead. I will post here when it changes.
Sorry for the time you lost on this.
andypieroux commentedon Nov 4, 2026
Thanks for confirming so quickly, and for being clear about not working around it. That makes sense. I'll uninstall on my side for now. Happy for you to close this or keep it open as the tracker — I've subscribed, so I'll see any update if Playtomic publishes a partner or club API.
helpcodeai commentedon Nov 4, 2026
Thanks again, @andypieroux. We're closing this here. The Playtomic connectors are coming off the catalog in #1506, because the login now requires app attestation and we won't work around it. If Playtomic publishes an API that third-party apps can use, we'll add a connector for it and post an update.
Unlist Playtomic connectors: login blocked by app attestation (#1506)