-
Notifications
You must be signed in to change notification settings - Fork 2.6k
crash due to Brave being selecting as autofill provider #41254
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
Comments
@haroonidrees can you please reproduce few more times and share more crash ids? Thanks |
Hi,
Clearing cache did not fix the issue, however clearing storage /
reinstalling the brave app resolved the problem. I was getting the error
even when after killing the brave app, which was strange.
I'm not sure if it's related but recently I installed the bitwarden app few
days before the issue appeared. Although the integration between bitwarden
and brave is poor, but I tried various settings so that brave would pick up
bitwarden auto fill, like draw-over etc. I couldn't get autofill to work
but this may have been a contributing factor.
…On Fri, Sep 27, 2024, 9:35 AM iefremov ***@***.***> wrote:
@haroonidrees <https://github.com/haroonidrees> can you please reproduce
few more times and share more crash ids? Thanks
—
Reply to this email directly, view it on GitHub
<#41254 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKKMTBCSZ4I2I4BB2NLU2U3ZYWCNDAVCNFSM6AAAAABO3UT6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZZGY3DKNJWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
thanks @haroonidrees |
Sorry, this started happening again. I've sent 10 reports using 'Send Now'
in brave://crashes.
…On Sat, Sep 28, 2024, 5:23 AM iefremov ***@***.***> wrote:
thanks @haroonidrees <https://github.com/haroonidrees>
—
Reply to this email directly, view it on GitHub
<#41254 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKKMTBFSYEYZVSUDKXU2RTTZY2NVNAVCNFSM6AAAAABO3UT6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGYZDGNBZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@haroonidrees could you please paste a few of crash ids in that issue? It would be much easier for us to filter them out from out crash reporting system in that case. |
fcdc0e00-bd5b-aa0c-0000-000000000000 02dd0e00-bd5b-aa0c-0000-000000000000 05dd0e00-bd5b-aa0c-0000-000000000000 3ade0e00-bd5b-aa0c-0000-000000000000 dcea0e00-bd5b-aa0c-0000-000000000000 |
|
@haroonidrees do you have Brave set as an autofill service on your Android OS settings? Could you please remove it from there as a temp workaround for now? |
Requires 1.70.124 or higher for verification 👍🏻 |
Verification PASSED on
Using the STR/Cases outlined via brave/brave-core#25759 (comment) & brave/brave-core#25759 (comment), ensured that
|
IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.
Brave Version: 1.70.117 Chromium: 129.0.6668.59
Operating System: Android 11
URL (if applicable) where crash occurred:
Can you reproduce this crash?
What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)
DO NOT CHANGE BELOW THIS LINE
Crash ID: crash/cf810100-bd5b-aa0c-0000-000000000000
The text was updated successfully, but these errors were encountered: