Welcome to RVX-Spotify Discussions!

[simoabid]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[4qx]

Howdy. The original patch notes state "Audio and visual ads will now appear." I am trying to understand what the point of this patch is if that's the case

[simoabid]

Try the new release v260308, it has some improvements and full ad blocking implemented!

[JibsouX]

Hello i analyse your work, there is some really good ideas but still login out detection.
There are my personal advices after your commit e9e358e

- Problem 1: Deleted Files Loaded in Memory (deleted)

Method flaw: In Linux/Android, when a .so file is loaded using System.load and then deleted, it remains visible in /proc/self/maps with the (deleted) tag. Example: /data/data/.../cache/liba8jf83k.so (deleted). This is the biggest red flag possible. Anti-cheat systems specifically look for executables located in data folders (rather than in the APK's system folder) that are marked as (deleted). This is the classic signature of malicious dynamic injection.

Improvement: Do not delete the temporary .so file while the application is running. Generate a filename that blends in perfectly with the environment, such as libcrashlytics-ndk.so or libspotify_audio_engine.so. Keep it on the disk. On the next launch, delete the old "fake" files before creating a new one, rather than hot-deleting them.

- Problem 2: Using Standard Java Collections Instead of Protobuf

Method flaw: The UnlockPremiumPatch.java class now returns standard Java LinkedHashMap or ArrayList objects. If the original Spotify code strictly expects to receive a specific Protobuf implementation (e.g., ProtobufList or Internal.ProtobufMap), the application will suffer an unexpected ClassCastException slightly further down in its execution, causing a crash.

Improvement: Instead of creating a new ArrayList<>(), it would be better to use the official Protobuf Builders (if they haven't been stripped by Proguard/R8) to instantiate collections that are "compatible" with the hooked method's signature.

If not possible : Alternatively, use a Java Dynamic Proxy to intercept calls to the original collection and make it lie "on the fly" (by overriding the .get() or .iterator() methods) without ever modifying its original type.

- Problem 3: Unhandled Null Signatures (Fingerprints)

Method flaw: The commit successfully wrapped AutoValue_PlayerOptionOverrides$Builder in a runCatching block, which is excellent. However, in UnlockPremium(), the calls to hookMethod on the DexKit fingerprints (e.g., ::homeStructureGetSectionsFingerprint.hookMethod) assume that the fingerprint was found. If the method returns null after a major Spotify update, calling .hookMethod on it will throw a NullPointerException and halt the initialization of the other hooks.

Improvement: Calls like ::X.hookMethod must be checked. DexKit should return an optional abstraction, or they must all be placed in individual try/catch blocks or utilize the existing fallback function to prevent a domino effect during a Spotify API update.

[JibsouX]

Something like that : https://github.com/JibsouX/RVX-Spotify-test/commit/9cece6870342c205e8aa2974f69ee16295f9a799

[JibsouX]

Little update :
Add protect cache I/O, error handling and silent logging
Wrap risky operations in runCatching to avoid crashing host apps: protect cache I/O in BaseHook.saveCache and wrap the reflection-based entrypoint in MainHook.inContext. Replace user-visible Toasts with Logger.printDebug and log reflection failures to XposedBridge to keep failures silent and avoid app crashes or detectable UI popups.
https://github.com/JibsouX/RVX-Spotify-test/commit/7152559aaa05a9c76a05fd3a871ad149dfa81824

[JibsouX]

mhhh..

Why it doesn't change anything about the result

The base idea behind RVX was that if Spotify serializes the original protobufs to send them back to the server, with the originals left intact → the server sees the real free values → no mismatch.

But the server doesn't detect anything through the serialization of local protobufs — it performs a live check on the backend side, comparing the state declared by the client against the actual state of the account in its database. It doesn't matter whether you mutate in place or clone: the client behaves like a premium account → the server compares it against the real data → logout.

In short: the difference is architectural but has no impact on detection.

So it's a dead way for this method. but i have already an other...

[Ruslanik77]

The main menu does not work on any account, If you go to my media library, everything works there.

[simoabid]

Try the new release v260308, it has some improvements and full ad blocking!

[Obnyr]

Similar bug here, although installed from the download of 260308. v260308 still indicates 260225 as a version number when installing also, maybe there was an error at release ?

[ts-ts]

This is a bug report for RVX-Spotify-v260308.
When I tap the switch to video button on the playback screen for each song, it doesn't play.

[simoabid]

Do you mean this video that plays with the song? it's working fine for me! if this is not what you meant, then maybe the bock list that blocks ads is blocking audio as well?

[ts-ts]

No. It's a music video that plays when you tap the yellow-framed button. Depending on the song, this button may not be displayed.

[simoabid]

Weird! I never saw it before. maybe it is not available in my region, so is it a region specific feature? anyway it is not a big deal in our case ! we're dealing with other things like server side log outs, ad blocking etc..

[ts-ts]

For example, you can watch the music video directly from the playback screen of "Bad Day."

　https://open.spotify.com/intl-ja/track/0mUyMawtxj1CJ76kn9gIZK

I'm using the app in Japan, and some songs feature playable music videos.
Music videos may not be available in some regions.

　https://support.spotify.com/artists/article/music-videos/

[JibsouX]

Blocking dealer will not work on app relaunch spotify has binded apresolve to dealer https://apresolve.spotify.com/?time=1773777228&type=accesspoint&type=spclient&type=dealer-g2, no apresolve no login, has dealer = logout

When you close and reopen the app: the app must refresh its session via login5.spotify.com/v3/login. But on the server side, the stored session and credentials have already been invalidated (the server has “marked” the account for logout even though the logout request wasn't received). login5 therefore returns an error → the app logs you out.

[JibsouX]

Your new token reinjection from cache is a clever way but this partially circumvented the problem by only reloading an old token that was previously valid and blocking synchronisation.
However, tokens all have an expiry date encoded in them, so if they aren't renewed/sync at some point, you will be logout anyway...

[2020loryx]

I get logged out again 😔

[JibsouX]

The only way to assign a premium license exclusively to the Player without the server knowing (to avoid detection) is to spoof the ProductState just before it is sent via JNI (Java Native Interface) to the C++ core, without including it in the network headers sent to the spclient server.

In your current code (UnlockPremiumPatch), when you modify an attribute via OverrideAttribute, you modify it globally within the application’s Java singleton. As a result, any network request from the application will carry this information (and get caught by the server).

[4qx]

Audio ads are back, plsease update the release! Thank you very lots