Call ..ArgumentPluginBase->getContextDefinition() on null causes WSOD

I was also seeing this error when running the migration via the browser. The migration stalls at 56% with these lines:

Source ID tracker: VIEW: tracker DISPLAY: default - The 'uid_touch' argument Plugin is missing and will be listed as broken.
Source ID tracker: VIEW: tracker DISPLAY: default - The field timestamp does not exist and has been removed from the fields configuration.
…

If I open a page from the web site, I get this error:

The website encountered an unexpected error. Please try again later.

Error: Call to a member function getContextDefinition() on null in Drupal\views\Plugin\views\argument\ArgumentPluginBase->getContextDefinition() (line 1410 of core/modules/views/src/Plugin/views/argument/ArgumentPluginBase.php).

If I hit F5 to refresh, the migration continues and completes.

I don't need the Tracker view, and can disable the Tracker view in Drupal 7, but cannot delete it ... I looked in the export source for the View, and saw this:

[...]
/* Contextual filter: Content: User posted or commented */
$handler->display->display_options['arguments']['uid_touch']['id'] = 'uid_touch';
$handler->display->display_options['arguments']['uid_touch']['table'] = 'node';
$handler->display->display_options['arguments']['uid_touch']['field'] = 'uid_touch';
$handler->display->display_options['arguments']['uid_touch']['exception']['title_enable'] = TRUE;
$handler->display->display_options['arguments']['uid_touch']['title_enable'] = TRUE;
$handler->display->display_options['arguments']['uid_touch']['title'] = 'Recent posts for %1';
$handler->display->display_options['arguments']['uid_touch']['default_argument_type'] = 'fixed';
$handler->display->display_options['arguments']['uid_touch']['summary']['format'] = 'default_summary';
$handler->display->display_options['arguments']['uid_touch']['specify_validation'] = TRUE;
[...]

After deleting the Contextual filters "User posted or commented" and saving the View, the Migration no longer hangs at 56%. I am not sure there's anything to do about it, but maybe this can help someone else?

And by the way, Views are getting imported and work well, so thanks for working on the module!

We also faced this issue while trying to migrate views from D7 to D10 site. The below patch helped me in moving forward with the migration.