# EeveeSpotifyReincarnated: a Spotify tweak that has outlived three of its own lineages

> An iOS tweak that intercepts Spotify's user data requests and rewrites the subscription fields in flight. It has been forked twice since Spotify's DMCA takedown, and the build is a GitHub Actions workflow you run yourself.

**SideloadLabs/EeveeSpotifyReincarnated** — Enhancing your Spotify experience on iOS

- Repository: https://github.com/SideloadLabs/EeveeSpotifyReincarnated
- Website: https://github.com/SideloadLabs/Eevee-Alt-Source/raw/refs/heads/main/apps.json
- Stars: 918 · Forks: 2,359
- Language: Swift
- License: GPL-3.0
- Published: 2026-10-07 · Updated: 2026-10-07 · Language: en
- Canonical page: https://hysenlabs.com/projects/sideloadlabs-eeveespotifyreincarnated

## What the tweak actually does to Spotify

The README describes the mechanism in a single paragraph, and it is worth taking literally. EeveeSpotify intercepts Spotify's requests to load user data, deserializes the response, and modifies the parameters in real time. There is no patched binary and no server involved. The subscription state the app reads is rewritten on the way in, which is why the same build works across a range of Spotify versions as long as the shape of that response does not change.

The README calls this method incredibly stable across supported Spotify versions, and pairs it with a second change: the tweak sets `trackRowsEnabled` to `true`, so track rows and liked tracks appear on artist pages the way they do for a paying account.

The subscription-related features that do not work are listed separately and explained by the same mechanism. Very High audio quality, native playlist downloading, hosting a Spotify Jam remotely, AI DJ and AI Playlist, and Spotify Connect are all described as server-side and stated to never work. Connect gets an extra sentence explaining why: when Connect is active the phone acts as a remote control and streams directly to the target device, so the client-side rewrite has nothing left to influence. Understanding this list is the fastest way to know what a build will and will not do before you start one.

The last update line in the README reads `8/19/26` with Spotify version `9.1.74`, and the repository description frames the project as enhancing the Spotify experience on iOS.

## Three lineages, one repository: why the fork history is the story

The README's history section is unusually specific, and it explains more about the project than any feature list could.

In January 2024, Spotilife, then the only tweak of its kind, stopped working on new Spotify versions. The developer who had reverse-engineered Spotilife, whoeevee, decompiled it, worked out how Spotify fetches user data, and built EeveeSpotify. In August 2025 the original EeveeSpotify repository was disabled after a DMCA takedown filed by Spotify. The README records that the original repository was disabled and that this one will not contain IPA packages in the repository itself.

Then the maintenance line broke twice more. In December 2025 whoeevee, described as the maintainer at the time, announced discontinuing the tweak because of the burden of following Spotify's changing architectures. Skye forked the original into EeveeSpotifyRevivedPublic to keep it working on newer versions. In March 2026 users of v9.1.28 hit constant logout problems and reported them, but no newer release came. A user named jaydenjcpy forked the revived project, fixed the logout issue, and that fork became EeveeSpotifyReincarnated, now maintained by jaydenjcpy, faroukbmiled and Mod4.

Two things follow from that history. The fork cadence is the release process, so a version number tracks Spotify rather than accumulating features. And the DMCA history has a visible consequence for the reader: no prebuilt package is published, so the build step is mandatory rather than optional. The GitHub field for forks reads 2,359 against 918 stars, which fits a project whose main distribution path is forking the repository to run a build workflow.

## Building an IPA with GitHub Actions, using a decrypted IPA you supply

The build instructions are a numbered list, and the first step is forking the repository and enabling read and write permissions for Actions on the fork. From there you sync the fork, open the Actions tab, pick the Create IPA Packages workflow, and run it.

The workflow asks for a decrypted `.ipa` file. The README is explicit that this cannot be provided for legal reasons, and it tells you to host the file on a file provider such as filebin.net, filemail.com or Dropbox and paste a URL into the field. Two failure modes are called out in the notes. The URL has to be a direct download link rather than a link to a webpage, or the process fails, and after the run completes you download the IPA from the releases section of your own fork, not the upstream repository. The instructions also point at the releases page of the EeveeSpotify repository to copy the link of the `.deb` file matching your architecture, while warning to use the original repository rather than the fork for that lookup.

The build inputs are worth understanding because they explain what the workflow does. The `Makefile` shows a Theos build targeting `iphone:clang:latest:14.0`, arm64 only, installing into a process named Spotify, with the tweak name `EeveeSpotify`.

```make
TARGET := iphone:clang:latest:14.0
INSTALL_TARGET_PROCESSES = Spotify
ARCHS = arm64
```

The same file derives the repository slug and branch at build time from the git remote, defaulting to `jaydenjcpy/EeveeSpotifyReincarnated` and `Master`, and writes them into a generated Swift enum. That is the mechanism by which a fork produces an IPA that reports its own source, which is what lets the maintainers tell where a build came from.

```make
TWEAK_NAME = EeveeSpotify
EeveeSpotify_EXTRA_FRAMEWORKS = EeveeSwiftProtobuf
EeveeSpotify_SWIFTFLAGS = -ISources/EeveeSpotifyC/include -Osize
```

## Patched, non-patched, and the signing methods that will not work

Every release note in this repository carries the same three-line block distinguishing build variants, and it is the most practically important text in the project.

A build is non-patched when installed through SideStore, AltStore, sideloadly, LiveContainer, or a free leaked enterprise certificate. A build is patched when installed on a jailbroken device, on TrollStore, or with a paid certificate. And ESign is called out by name as causing a crash. The distinction is not cosmetic: the sideload path relies on out-of-process injection, while the jailbreak path links against libroot, so the two variants are built differently.

The `Makefile` shows that split directly. When `THEOS_PACKAGE_SCHEME` is `roothide`, the build defines `ROOTHIDE` and links `-lroothide` with a runtime path into `@loader_path/.jbroot/Library/Frameworks`; every other build links `-lroot`, which is the rootless scheme. The comments in the file explain why: RootHide's compatibility implementation resolves jailbreak paths through libroothide at runtime.

```make
ifeq ($(THEOS_PACKAGE_SCHEME),roothide)
EeveeSpotify_SWIFTFLAGS += -D ROOTHIDE
EeveeSpotify_LDFLAGS += -lroothide
else
EeveeSpotify_LDFLAGS += -lroot
endif
```

Keychain redirection, group containers and CloudKit are handled by a separate module, `modules/zxPluginsInject`, injected at load-command level by `ipapatch` in `build-ipa-local.sh` and in the GitHub workflow, with no compiler flags. That note is the reason the sideload variant can behave like the jailbroken one without the Makefile branching for it.

For installation the README recommends SideStore or a certificate-based signer such as Ksign for sideloaded IPAs, and points at OpenSpotifySafariExtension for opening Spotify links from a sideloaded app.

## Five lyrics providers, two different lists, and a note about search results

Custom lyrics are the feature with the most moving parts. A section near the top of the README lists five providers as fully available from Spotify 9.1.56 onward: Spicy Lyrics, Musixmatch, PetitLyrics, LRCLIB and Genius, with a note that all providers work. A later section describes the same feature as replacing Spotify's monthly limited lyrics with one of four providers, and lists Genius, LRCLIB, Musixmatch and PetitLyrics without Spicy Lyrics.

Both passages are in the current README. The five-provider list sits above the build instructions, the four-provider list sits below the restrictions, and the release history explains the difference: v6.6.6, dated 2026-06-28, added SpicyLyrics as a new feature alongside a new icons drop and support for Spotify 9.1.60. So the upper list is the current one and the lower paragraph predates that release.

The providers differ in ways that matter for choosing one. Genius is described as the best quality with the most songs and the fastest updates, and explicitly never time-synced. LRCLIB is the most open and offers time-synced lyrics but lacks many songs. Musixmatch is the service Spotify itself uses, gives time-synced lyrics for many songs, and requires a user token you obtain from the Musixmatch app or by extracting one. PetitLyrics offers plenty of time-synced Japanese and some international lyrics.

The README is also candid about failure: if the tweak cannot find or process a song you get a message saying the lyrics could not be loaded, and Genius results can be the wrong song because of how the tweak searches. Both are flagged as not-for-issues.

## What the tree contains beyond the tweak itself

The repository is larger than a single Xcode project would be, and the extra files explain how a project that must track a moving target stays organized.

`Sources/` holds the Swift implementation and `EeveeSwiftProtobuf` is listed as an extra framework, so the tweak links a bundled protobuf runtime. There is a `swiftprotobuf/` directory at the root and a `Package.swift`, which is how the framework gets built alongside the tweak rather than being assumed present. `Tests/` and `Tools/` sit next to them, and `layout/` is where tweak UI layout definitions live, the convention for Theos-based iOS tweaks.

Then there is the maintenance scaffolding, which is the part that distinguishes this from a personal tweak. `classes_910.txt` and `class_comparison.md` are artifacts for tracking Spotify's Objective-C class surface across versions. `version-update-locations.txt` lists where version strings live in the source, which is what stops a release bump from missing a spot. `build-ipa-local.sh` and `setup-build-ipa.sh` let you reproduce the Actions build locally, and `test-spotify-api.sh` is a script for probing the endpoint the tweak intercepts. `common_issues.md` and `something-went-wrong.md` are linked from the README as the place to look before opening an issue, and `TRANSLATING.md` and `contributors.json` handle localization and credits.

GitHub reports the license as GPL-3.0 and the default branch as `Master`, matching the branch name the Makefile defaults to. The last push was on 2026-09-17. One oddity is the repository's homepage field, which points to an `apps.json` file in a different repository, `SideloadLabs/Eevee-Alt-Source`, rather than to documentation for this project. There is no documentation site; the README, the common-issues file and the Telegram channel linked from the release notes are the whole support surface.

## Conclusion

What is interesting in this repository is not the feature list but the maintenance model. A tweak that patches a proprietary app has no stable interface to build against, so the project survives by having a new maintainer fork it the moment Spotify ships a version that breaks it, and by making the fork cheap to set up. The GitHub Actions build, the version-tracked Spotify targets in the release notes, and the pinned list of features that can never work all point the same way. The honest limits are stated plainly: the repository ships no IPA, the build needs a decrypted IPA you supply, and five subscription features are decided server-side. Read the restrictions list before spending an evening on a build, because nothing in the client can move those five.

## FAQ

### Does Eevee Spotify still work?

The README records the last update as `8/19/26` against Spotify version `9.1.74`, and the v6.6.8 release notes name support for Spotify 9.1.72 and 9.1.74. Because the tweak rewrites the subscription fields as Spotify's user data is deserialized, it keeps working until Spotify changes the shape of that response, which is what the project's fork history shows happening several times.

### Why is EveeSpotify not working?

The most common causes named in the project are signing and build variant rather than logic. The release notes state that ESign causes a crash, and that patched builds are for jailbroken devices, TrollStore or a paid certificate while SideStore, AltStore, sideloadly and LiveContainer take the non-patched build. If the app installs but behaves as a free account, check the restrictions list, since Connect, Jam, playlist downloading and AI features are decided server-side.

### Is Eevee Spotify safe to use?

The repository publishes no application package: the README states that after the DMCA takedown the project will not contain IPA packages in the repository, so a build requires supplying your own decrypted IPA and running the GitHub Actions workflow on your own fork. That means what you install is assembled from source you can read, on infrastructure you control, rather than downloaded from a third-party mirror.

### How do I install Spotify Eevee on my device?

Fork the repository, enable read and write permissions for Actions on the fork, then run the Create IPA Packages workflow with a direct download link to a decrypted IPA you host yourself. Download the result from your fork's releases section. The README recommends SideStore or a certificate-based signer such as Ksign for sideloaded IPAs, and warns that ESign crashes.

## Sources

- [License: GPL-3.0](https://github.com/SideloadLabs/EeveeSpotifyReincarnated/blob/Master/LICENSE)
- [Project website](https://github.com/SideloadLabs/Eevee-Alt-Source/raw/refs/heads/main/apps.json)
- [README](https://github.com/SideloadLabs/EeveeSpotifyReincarnated/blob/Master/README.md)
- [Releases](https://github.com/SideloadLabs/EeveeSpotifyReincarnated/releases)
- [SideloadLabs/EeveeSpotifyReincarnated on GitHub](https://github.com/SideloadLabs/EeveeSpotifyReincarnated)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/sideloadlabs-eeveespotifyreincarnated