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

Reland again brave/brave-core/pull/17431 #28978

Closed
AlexeyBarabash opened this issue Mar 9, 2023 · 2 comments · Fixed by brave/brave-core#17545
Closed

Reland again brave/brave-core/pull/17431 #28978

AlexeyBarabash opened this issue Mar 9, 2023 · 2 comments · Fixed by brave/brave-core#17545
Assignees
Labels
dev-concern OS/Android Fixes related to Android browser functionality QA/No release-notes/exclude

Comments

@AlexeyBarabash
Copy link
Contributor

PR brave/brave-core/pull/17431 was reverted twice:

Original issue: #28831
Original PR: brave/brave-core#17431

Test plan:

  1. Ensure Stable channel Release build is not broken:
    npm run build -- Release --target_arch=x86 --target_android_base=mono --target_os=android --target_android_output_format=apk;
  2. Ensure there is no crash on app start and possible to pass onboarding.
@kjozwiak
Copy link
Member

kjozwiak commented Apr 6, 2023

As per brave/brave-core#17545 (comment), the QA will basically run through the STR/Cases every time we install the app while running through 1.51.x verifications. So this will get verified several times by default. Labelling as QA/No.

@AlexeyBarabash
Copy link
Contributor Author

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-concern OS/Android Fixes related to Android browser functionality QA/No release-notes/exclude
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants