Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Play Services authorization prompt in v74 #281

Closed
dadosch opened this issue Apr 13, 2019 · 31 comments
Closed

Google Play Services authorization prompt in v74 #281

dadosch opened this issue Apr 13, 2019 · 31 comments
Labels
bug upstream bugs which are identified in upstream Chromium

Comments

@dadosch
Copy link

dadosch commented Apr 13, 2019

Bromite version

Version: 74.0.3729.80
Arch: arm64
Android version: 7.1.2

Is the bug reproducible with latest version?
Already using latest version available from F-Droid Repo.

Can the bug be reproduced with corresponding Chromium version?
Not tested, but Chromium doesn't claim to be privacy-enhanced.

Is the bug a crash?
no

Describe the bug
A notification appears after the latest update saying that Bromite needs Google Play Services. (see screenshot)

Expected behavior
Bromite should not depend on Google Play Services

Screenshots
Screenshot_20190413-162835

@csagan5
Copy link
Contributor

csagan5 commented Apr 14, 2019

This is likely due to new code in v74 using Play integrations; unfortunately the patches that I am using to evict this functionality are orphaned, so I would have now to do some work to find out why it's happening.

@csagan5 csagan5 added the bug label Apr 14, 2019
@csagan5 csagan5 changed the title Bromite wants to use Google Play Services Google Play Services authorization prompt in v74 Apr 14, 2019
@ouzowtf
Copy link

ouzowtf commented Apr 14, 2019

I haven't seen this notification yet. When does it show up?

@csagan5
Copy link
Contributor

csagan5 commented Apr 14, 2019

This could be a regression (reference: https://forum.xda-developers.com/showpost.php?p=76242418&postcount=652)

@ouzowtf you need to terminate the app or reboot to see it.

@csagan5
Copy link
Contributor

csagan5 commented Apr 15, 2019

Fixed in 74.0.3729.86.

@dadosch please report back if it is not fixed.

@csagan5 csagan5 closed this as completed Apr 15, 2019
@dadosch
Copy link
Author

dadosch commented Apr 18, 2019

I can confirm that it isn't fixed in 74.0.3729.86.

@csagan5
Copy link
Contributor

csagan5 commented Apr 21, 2019

Ok, thanks for reporting; something must have changed in the code or in the manifest that makes this prompt happen again. No idea about what though.

@csagan5 csagan5 reopened this Apr 21, 2019
@hadig
Copy link

hadig commented Apr 25, 2019

You can disable this notification in bromite's notification settings

@csagan5
Copy link
Contributor

csagan5 commented Apr 28, 2019

Is this problem still present with 74.0.3729.122?

@AlternativeZero
Copy link

@csagan5 I still seem to have login issues on 74.0.3729.122, I brought it up in the microg issues cause I thought it was an issue on their end but read on xda it's an issue with v74.

I have a logcat there if it's any use.

@ghost
Copy link

ghost commented May 5, 2019

Is this problem still present with 74.0.3729.122?

Yes.

@csagan5

@AlternativeZero
Copy link

Just tested 74.0.3729.141 and login still isn't working.

@csagan5
Copy link
Contributor

csagan5 commented May 7, 2019

@AlternativeZero that should be discussed in a separate issue. This issue here is "Google Play Services authorization prompt in v74"

@csagan5
Copy link
Contributor

csagan5 commented May 18, 2019

I cannot reproduce this issue; can somebody please verify with 74.0.3729.162?

@ghost
Copy link

ghost commented May 18, 2019

I cannot reproduce this issue; can somebody please verify with 74.0.3729.162?

The issue still exists in the latest version, 74.0.3729.162.

@csagan5
Copy link
Contributor

csagan5 commented May 18, 2019

@BugReporter2 you are experiencing this issue with the Bromite browser, not the SystemWebView, correct?

What are the steps to trigger it?

@ghost
Copy link

ghost commented May 19, 2019

@BugReporter2 you are experiencing this issue with the Bromite browser, not the SystemWebView, correct?

Yes, with the Bromite browser.

What are the steps to trigger it?

Just normal browsing. There is no special step to trigger it. Start browsing websites, so that prompt will come in a certain amount of time. Sometimes the prompt comes almost immediately when you open Bromite and start browsing and sometimes it can take several minutes.

@whour
Copy link

whour commented May 22, 2019

75.0.3770.50 still have problems.
Just browse m.youtube.com, click a video,you will see the problem.

@allenluce
Copy link

This is likely due to new code in v74 using Play integrations; unfortunately the patches that I am using to evict this functionality are orphaned, so I would have now to do some work to find out why it's happening.

Hi @csagan5, can you supply a reference to those patches?

@csagan5
Copy link
Contributor

csagan5 commented May 24, 2019

@allenluce the patches have been included for about a year now, they come from this abandoned project: https://gitlab.com/thermatk/Unobtainium

You can find them under https://github.com/bromite/bromite/tree/master/build/patches as kill-Auth.patch and kill-GCM.patch; the Chromium build from Arch Linux has similar patches.

This new authorization request is due to some new code from upstream and it's not easy to find out where it is; I also cannot reproduce it.

@thestinger
Copy link

Try visiting https://www.tomshardware.com/.

@csagan5
Copy link
Contributor

csagan5 commented Jun 18, 2019

@thestinger I am still unable to reproduce this with real devices. Can this be reproduced with the Android Virtual Device or it is related to running a specific ROM?

@thestinger
Copy link

It occurs for me on AOSP on any of the officially supported devices. I think there's a good chance you could reproduce it in the emulator.

@thestinger
Copy link

Also, worth noting that this does also occur in Brave too: brave/browser-android-tabs#1639, so the idea of getting a fix from there isn't viable.

@expobar
Copy link

expobar commented Jun 20, 2019

Another page which quickly triggers this issue is https://1.1.1.1/help

@csagan5
Copy link
Contributor

csagan5 commented Jun 24, 2019

@thestinger I think it does not appear on my physical devices because it might have been granted in the past already.

Thanks for the explanation and reference, it makes sense. So it's an upstream bug and there appears to be little incentive from upstream to fix it in a timely manner.

@csagan5 csagan5 added the upstream bugs which are identified in upstream Chromium label Jun 24, 2019
@csagan5
Copy link
Contributor

csagan5 commented Jun 24, 2019

Has anybody found/created the upstream issue in Chromium issue tracker? I suggest addressing it upstream, they might find more easily where this comes from.

This would be addressed radically if no play services were used in Bromite, but it's not currently being worked on.

Closing it as the fix will come from upstream (if ever).

@csagan5 csagan5 closed this as completed Jun 24, 2019
@thestinger
Copy link

I don't think there's an issue open yet. I wanted to identify the reason for the issue before filing it. They're likely to fix it very quickly if they're pointed towards the right place, but otherwise I expect they will treat it as a very low priority unless they can quickly identify the problem. Since https://1.1.1.1/help can trigger it without needing much code, someone should work on narrowing down the specific issue and then it should be fairly easy to find the right place to fix this.

@csagan5
Copy link
Contributor

csagan5 commented Jul 11, 2019

Will be fixed in next release 75.0.3770.139 thanks to @thestinger's patches.

@csagan5 csagan5 reopened this Jul 11, 2019
@csagan5
Copy link
Contributor

csagan5 commented Jul 13, 2019

Can someone please test whether this problem is resolved with latest version 75.0.3770.139 or not?

@expobar
Copy link

expobar commented Jul 13, 2019

Fixed on my side. I can't seem to trigger it on sites that usually triggers this. Thanks guys.

@csagan5 csagan5 closed this as completed Jul 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug upstream bugs which are identified in upstream Chromium
Projects
None yet
Development

No branches or pull requests

9 participants