Component registrations are async. This causes problems with the new Android background task update scheduler where we sometimes want to fire component updates before the components are registered (see issue 867354). We are currently pursuing a workaround where we add some delay before firing the component update to give all components time to register. That is not great. It would be better to solve this problem in a more principled way. For instance, we could add a callback that fires after all components have finished registering and only then run the update task.
Comment 1 by bugdroid1@chromium.org
, Aug 22