Uncaught TypeError: Argument 1 passed to Magento\Catalog\Block\Product\ImageFactory::getRatio() must be of the type integer

[rr10]

0

i have this error in product page after upgrade to magento 2.3.4 from 2.2.6 php 7.2

magento 2.3.4
php 7.2
centos
apache
template porto 2.3.2

[20-Apr-2020 15:39:48 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to Magento\Catalog\Block\Product\ImageFactory::getRatio() must be of the type integer, null given, called in /home/rlk001/public_html/vendor/magento/module-catalog/Block/Product/ImageFactory.php on line 172 and defined in /home/rlk001/public_html/vendor/magento/module-catalog/Block/Product/ImageFactory.php:105 Stack trace:
0 /home/rlk001/public_html/vendor/magento/module-catalog/Block/Product/ImageFactory.php(172): Magento\Catalog\Block\Product\ImageFactory->getRatio(NULL, NULL)
1 /home/rlk001/public_html/generated/code/Magento/Catalog/Block/Product/ImageFactory/Interceptor.php(24): Magento\Catalog\Block\Product\ImageFactory->create(Object(Magento\Catalog\Model\Product\Interceptor), 'product_page_im...', Array)
2 /home/rlk001/public_html/vendor/magento/module-catalog/Block/Product/ImageBuilder.php(135): Magento\Catalog\Block\Product\ImageFactory\Interceptor->create(Object(Magento\Catalog\Model\Product\Interceptor), 'product_page_im...', Array)
3 /home/rlk001/public_ht in /home/rlk001/public_html/vendor/magento/module-catalog/Block/Product/ImageFactory.php on line 105enter code here

thanks

i have found a similar issue
https://magento.stackexchange.com/questions/264084/uncaught-typeerror-argument-1-passed-to-magento-catalog-block-product-imagefact

[m2-assistant]

Hi @rr10. 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.

@rr10 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[mrtuvn]

@rr10 This issue fixed in this PR #26974

[m2-assistant]

Hi @engcom-Alfa. 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-Alfa]

Hi @rr10 .

Looks like this issue has already been fixed in PR #26974.

So, we have to close it.
Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch. Thank you for collaboration.