Error: Call to undefined method Drupal\views\Render\ViewsRenderPipelineMarkup::render()

I'm getting the same error after upgrading from Drupal 8 to 9. I had a quick look at the code and tried to find a solution but no luck so far. Line 82 in BreadcrumbList.php looks like this:

$text = is_object($text) ? $text->render() : $text;

An easy solution would be to extend this to check if $text is ViewsRenderPipelineMarkup and then don't call render(), but that kind of solution could easily grow large and ugly. Any ideas on how to approach this?

I created a patch to solve the issue quickly, but a better solution would be nice.

I created a patch. The #3 not success on my case.

Patch in #5 solved the issue in my case

Patch in #5 also solved the issue for me :)

Disregard this patch, it's the same for 8.x-1.8 version.

Patch in #5 also solved the issue for me.

Working for me with the patch in #5.

As a reminder, when a patch is added to an issue please set the status to "needs review". Thank you.

Patch #5 solved my issue.

Patch #5 work for me too. Thanks.

Even though the attached patch does solve the issue described, I see two problems:
- It introduces a dependency to the views module
- The instance check is too specific: the same issue may arise for different classes.

I propose a simpler approach: The Link objects returned by the breadcrumb builder can return three types: string, array or MarkupInterface. Objects implementing the MarkupInterface must have a __toString(), meaning objects will be converted to string when needed.
Finally, this patch adds support to render array being returned by Link::getText(), by rendering it.

Hi, I checked this issue probably has a much easier solution:
1. The breadcrumb "->getLinks()" method returns list of "\Drupal\Core\Link" objects.
2. The link "->getText()" method already returns a "string", "array", or "\Drupal\Component\Render\MarkupInterface" object.
3. The "getItems()" method output should be a renderable array, so we don't need to render values ourselves.

I'm attaching patches for both branches.
Could you please review and test if it works for you too?

Thank you
Vit

@kyberman the third assumption is wrong, getItems() do not return a render array, but a basic associative array. I've tried to pass a simple render array in the name key, and it was printed as a json representation of this array:

"itemListElement": [
    {
        "@type": "ListItem",
        "position": 1,
        "name": {
            "#markup": "Link title"
        },
        "item": "https://example.com"
    }
]

Patch in #5 solved the issue for me (Drupal 8.9.7). After applying patch in #15, it also solved the issue (Drupal 9.3).

Patch #15 fixes our issues after upgrading the module on Drupal 9.3:
- If pathauto module is also enabled, and taxonomy term hierarchy is used in a node path alias (so BreadcrumbList at least 3 items), then the site produces WSOD with the error described in this issue summary for this kind of URL: /term-parent/term-child/node-article
- Also, 404 and 403 error pages produce WSOD with a URL like this: /xxxxx/xxxxx/xxxx, same error happens.
The patch fixes both use cases.

I'm raising the priority to Critical because this problem completely breaks certain pages on the website currently.

#15 looks like the most flexible solution. I've made a few small additions just because this is introducing an opportunity to remove some \Drupal::service calls. New patch and interdiff attached and I'll be merging this in to 8.x-2.x (perhaps notably, not 8.x-1.x, see #3264566: Seeking co-maintainers if you're interested in helping support older branches).