Location trusted prompt for Scopes shown immediately after the wizard

The trusted prompt for location access for Scopes is shown immediately after the wizard and not after first search or pull-to-refresh initiated by the user as intended. For some reason it happens only if wizard is involved in the boot sequence, and not if trusted prompt for location is just forced by removing .scopesLocationPrompt and trust store db.

Looking at the unity8-dash.log file from the first boot after wiping the device, it seems that there is a forced refresh of scopes registry metadata early during the dash startup:

[2016-04-23:07:04:42.593] Refreshing scope metadata
[2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope with id 'com.canonical.scopes.weatherchannel'"
[2016-04-23:07:04:42.983] Dispatching search: "com.canonical.scopes.dashboard_dashboard" "" ""
[2016-04-23:07:04:42.987] Enabling location updates

This calls invalidateResults() and has the same effect as pull-to-refresh.

This is most likely caused by the network becoming available & remote scopes getting fetched for the first time, signaling new scopes get available to the shell.

To reproduce, reflash with --wipe or perform factory reset.