Unable to migrate sites on 3.160: There are no valid install profiles on the target platform to migrate to

I think this is caused by commit: 43fa468915a8f77b463da330dd93b924c183cad4

While it's true that the documentation on hosting_package_isntance_load returns an array, it seems to be returning an object in my tests on 3.160.

I think by default count() on an object will return 1 meaning that the previous conditions worked (sort of), whereas the new ones fail when an object is received but not an array. Also note: in hosting_migrate.drush.inc

if (is_array($profile_instance) && count($profile_instance)) {                                     
   $task->options['profile'] = $profile_instance->short_name;
}
else {
  .....

The code for assigning the profile assumed the profile_instance is an object, not an array.

The underlying bug is perhaps that hosting_package_load_instance does not return an array as the new conditions expect, but there will maybe be a couple of further changes since the existing code generally seems to assume it's an object instead.

Btw, I added some debug lines around hosting_migrate.drush.inc to get a clearer picture of the data being return:

Calling hook drush_hosting_migrate_pre_hosting_task	

Getting target profile name for profile node: 61	

target_platform: 46847 ; profile_short_name: standard	

Got profile_instance: stdClass Object ( [iid] => 39419 [version] => 8.6.1 [version_code] => 80600000500 [schema_version] => 0 [status] => 0 [rid] => 46847 [package_id] => 61 [package_type] => profile [nid] => 61 [description] => Install with commonly used features pre-configured. [short_name] => standard [old_short_name] => default [title] => Standard [type] => platform [languages] => Array ( [en] => English ) ) 

Applied and migrations work as expected now.

Thanks!