From b7ff762301eb1aabd11d7acb52c26e768e6e5691 Mon Sep 17 00:00:00 2001
From: whoeevee <94960726+whoeevee@users.noreply.github.com>
Date: Thu, 31 Jul 2025 01:05:37 +0300
Subject: [PATCH] Create something-went-wrong.md

---
 something-went-wrong.md | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 something-went-wrong.md

diff --git a/something-went-wrong.md b/something-went-wrong.md
new file mode 100644
index 0000000..cf80386
--- /dev/null
+++ b/something-went-wrong.md
@@ -0,0 +1,8 @@
+In recent Spotify versions, the new reCAPTCHA SDK was integrated. It uses Apple's App Attest as part of its detection engine, generating keys within the Secure Enclave. The attestationObject includes the app's bundle and team IDs, which can be validated by Spotify's backend. When you sideload an app by any method, the teamID inevitably changes, resulting in App Attest failure.
+
+However, this check is not strictly required at the moment. If Spotify chooses to enforce reCAPTCHA with App Attest in the future, you will no longer be able to log in with sideloaded EeveeSpotify. There are some potential workarounds, such as spoofing a previous version without reCAPTCHA integration, or creating a server that runs on a jailbroken device to generate signatures and attestation objects for App Attest. Regardless, I won't implement any login fixes in EeveeSpotify. If someone is interested in developing a solution, they are welcome to submit a pull request.
+
+Currently, there are two workarounds if you see the “Something went wrong” message during login:
+
+- Go to accounts.spotify.com, navigate to Account Overview > Edit Login Methods, and connect your Apple or Google Account. Logging in with Apple or Google has consistently worked so far.
+- Install a previous version of EeveeSpotify and log in. You can update to the latest version and remain logged in after.