Product Display Page: Error: Call to a member function getId() on bool in vendor/magento/module-catalog/Block/Product/ListProduct.php:464

[nbennett25]

Preconditions (*)

1. Magento 2.4.2-p2

Steps to reproduce (*)

1. Go to Product Display page with product assigned to at least one category

Expected result (*)

1. Product display page is rendered

Actual result (*)

1. Error is thrown (developer mode)

Stack trace:
Error: Call to a member function getId() on bool in /var/www/html/vendor/magento/module-catalog/Block/Product/ListProduct.php:464

This appears to be related to the change in the Magento\Catalog\Block\Product\ListProduct class, converting to the use of the current method:

462             if ($categories->count()) {
463                 // show products from this category
464                 $this->setCategoryId(current($categories->getIterator())->getId());
465             }

Converting this to use the built in current() method in the ArrayIterator class works as expected:

462             if ($categories->count()) {
463                 // show products from this category
464                 $this->setCategoryId($categories->getIterator()->current()->getId());
465             }

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ x] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @nbennett25. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[nbennett25]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @nbennett25. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @nbennett25, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[hostep]

It appears there is already a fix for this problem: #32389 and it looks like this fix is included in Magento 2.4.3

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Verified the issue on Magento 2.4-develop branch and the issue is not reproducible:
Steps performed:
Magento Operation mode is set to developer - bin/magento deploy:mode:set developer
Front-end - Catalog Search Results page - Click on Product - Product Details page is displayed as expected
Assigned Product to multiple categories from Admin and saved
Reindex and clear cache
Front-end - Product Details page is displayed as expected. No issue
Admin - Product page is also displayed as expected - No issue
@nbennett25 , kindly recheck the issue on Magento 2.4-develop branch and provide missing steps if any if the issue is still reproducible.
Thank you.

[nbennett25]

thx @engcom-November - a deeper dive into the stack trace on our end indicates that this issue stems from the Smartwave_FilteredProducts module. Thanks for investigating!