"You must pass at least entity" exception when users with no permission click "download pdf"

This not using VBO. Just core views. With VBO module there is a submodule that does action permissions but that's something else. It perhaps possible to hide the button but I'm not sure where.

Hiding the button is also not enough as you could still access the route somehow and the exception get thrown where it should be access denied.

I doubt they support that that's why they have action_permissions. It's similar to any other action such as edit, delete ..etc. they all are displayed despite lacking the permissions for the operations. If an action is performed by a user with no permission, for example, delete, a denial message is displayed without an error. I think entity_print should do the same.

So entity_print implements access correctly and the user gets the message "No access to execute..." after the exception is thrown when the user refresh the page "admin/content". But for some reason the exception is thrown (either before or after), prevent normal flow. I will change the patch to not catch the exception.

Here is what I found is going on between entity_print and views: (code commented)

       // The access is evaluated and entity_print correctly handles it therefore it passes this condition::
        if (!$action->getPlugin()->access($entity, $this->view->getUser())) { 
          // And correctly an access denial message error is displayed:
          $this->drupalSetMessage($this->t('No access to execute %action on the @entity_type_label %entity_label.', [
            '%action' => $action->label(),
            '@entity_type_label' => $entity->getEntityType()->getLabel(),
            '%entity_label' => $entity->label()
          ]), 'error');
          continue; 
        }

        $count++;
        // At this point entities remain empty.
        $entities[$bulk_form_key] = $entity;
      }
       // And eventually passed to deliverPrintable where an exception in thrown.
      $action->execute($entities); 

So unless views is doing something wrong, we need to check if entities are empties; which means access was denied.
updated the patch.

although( entity_print-2969357-9.patch) patch passed my basic testing on my local environment , but on a live env with https, nginx, load balancer, it's causing blank screen. I am assuming because the returned response is malformed. Not sure what's the most appropriate response.

Another attempt since it seems the that

return (new StreamedResponse(function () use ($entity, $print_engine, $config) {
      // The Print is sent straight to the browser.
      $this->printBuilder->deliverPrintable([$entity], $print_engine, $config->get('force_download'), $config->get('default_css'));
    }))->send();

Fails when deliverPrintable returns false on an environment with https, nginx and loadbalancer. here is some pics of the response header/preview:

1. https://i.imgur.com/CFNoLOb.png
2. https://i.imgur.com/fdeOzpi.png

Nothing that stood out as far as I looked but will dig more when i have time. But I am almost certain it has to do with StreamedResponse .
Perhaps streamedResponse should not be instantiated if there are no entities?