-
Notifications
You must be signed in to change notification settings - Fork 949
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
moves autofill service (and activities) to its own process #5720
base: develop
Are you sure you want to change the base?
moves autofill service (and activities) to its own process #5720
Conversation
2ecd9a6
to
1f53db5
Compare
@@ -100,7 +100,9 @@ class RealAutofillService : AutofillService() { | |||
|
|||
callback.onSuccess(response) | |||
}.onFailure { | |||
pixel.fire(AutofillPixelNames.AUTOFILL_SERVICE_CRASH, mapOf("message" to it.extractExceptionCause())) | |||
if (it !is kotlinx.coroutines.CancellationException) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While testing I've noticed some crash pixels related when the coroutine is cancelled (before completion). That doesn't represent a crash, so skipping if that's the case.
@@ -110,6 +111,14 @@ open class DuckDuckGoApplication : HasDaggerInjector, MultiProcessApplication() | |||
} | |||
} | |||
} | |||
|
|||
runInSecondaryProcessNamed(AUTOFILL_SERVICE_PROCESS_NAME) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once you have rebased with develop, you wouldn’t need any changes in this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just pushed the actual changes, so this should be solved.
1f53db5
to
9bba237
Compare
Task/Issue URL: https://app.asana.com/0/1200156640058969/1209537052601451
Description
Moves Autofill Service (and activities) to its own process
Steps to test this PR
Feature 1
then smoke test the service
UI changes