[Play Integrity API] Binding to the service in the play store failed . This is due to having an old play store version installed on the device #2050
Comments
|
1st, you need to provide much more details.
http://www.catb.org/~esr/faqs/smart-questions.html
2nd, please ask at MicroG support. This small app is just a stub.
|
|
If this is a Play Integrity API check problem it seems to be a fakestore issue, see error codes. |
|
From my investigation Play Integrity is binding specifically to com.android.vending package com.google.android.play.core.integrity;
import android.content.Intent;
/* loaded from: classes2.dex */
final class u {
public static final Intent a = new Intent("com.google.android.play.core.integrityservice.BIND_INTEGRITY_SERVICE").setPackage("com.android.vending");
} |
Originally posted by @ale5000-git in #1771 (comment) For me is not yet very clear, but implement the api on gmscore and link with fakestore, or implement on fekestore is probably indifferent. |
.setPackage("com.android.vending");Code from Play Integrity library. |
|
One of the functions that needs implementing https://developer.android.com/google/play/integrity/reference/com/google/android/play/core/integrity/IntegrityManager.html#requestIntegrityToken(com.google.android.play.core.integrity.IntegrityTokenRequest) HAR file for play integrity requests
|
|
I believe all play store does it's just says "yep, this app is licensed", and then forwards request to droidguard. |
|
@mar-v-in, I can try to implement this feature, I reversed it a lot already. |
Since this is an open-source project, yes, PRs are welcome |
|
@Uldiniad you will work on this? |
|
No, I just implemented the stub as a starting point. Feel free to take it on from here |
It seems to me to be a bit more complicated, since is a signed response. |
|
@redacted-text Hello, is there any new progress on this? |
ale5000-git
changed the title
|
@bbaster I have contacted him on telegram, it seems that play integrity continue to change internally day to day... He is waiting that google stabilize it. Then will be a pull request. |
|
I transferred this issue to GmsCore as the FakeStore source code is now maintained in the vending-app folder in GmsCore repository. |
|
For context and searchability, here are logs that appear in logcat if you try the hydra app with lineage-microg: |
|
I see that #2611 is closed, is this done or nah? |
|
I read some of #2599 (totally didn't copy paste chunks into chatgpt truss me) and it looks like it is going the same way the official implementation goes. My understanding:
Either way it means that yall are running arbitrary, proprietary code from Google's servers. Shouldn't the user get warned in any way? |
|
It seems to be done on the next release (0.3.6). |
|
@TailsFanLOL this feature is disabled by default. On the screen to enable it (which currently is the same screen we use for SafetyNet) it is explained that the proprietary droidguard is used. We might want to make this more explicit and adjust the wording for Play Integrity, but in the end, if users need it, it's for a proprietary app, so users already do run proprietary code on their device anyway. From what we've seen in the past, the droidguard proprietary code is not as much of a privacy issue, compared to regular tracking libraries you see in almost every proprietary app these days. There's been a bunch of research and analysis around droidguard, so you can probably find some good sources on that. |
|
@mar-v-in, aight. I found out how it works from a 2019 habr post, no idea if anything changed. |
|
This issue was only for "Binding to the service in the play store failed" that got implemented in v0.3.6 of microG so it is now fixed. |
Binding to the service in the play store failed . This is due to having an old play store version
Is this fake store issue or gms core issue
The text was updated successfully, but these errors were encountered: