Plugin error with WPML + Subscription when changed to different currency

[hyroescom]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Install WPML + WooCommerce Subscription + WooCommerce Multilangual
2. Add currency
3. Set custom price for product
4. Change to this custom currency

Expected behavior Fatal error.

Screenshots

#3 /home/runcloud/webapps/panelhyroes/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-blocks-support.php(176): WC_Stripe_Blocks_Support->get_payment_request_" while reading response header from upstream, client: 74.116.32.39, server: panel.hyroes.com, request: "GET /en/produkt/environet-service-hosting/ HTTP/2.0", upstream: "fastcgi://unix:/var/run/panelhyroes.sock:", host: "panel.hyroes.com"
#2 /home/runcloud/webapps/panelhyroes/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-blocks-support.php(269): WC_Stripe_Payment_Request->javascript_params()
#1 /home/runcloud/webapps/panelhyroes/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-payment-request.php(808): WC_Stripe_Payment_Request->get_product_data()
#0 /home/runcloud/webapps/panelhyroes/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-payment-request.php(416): WC_Stripe_Payment_Request->get_product_price()
Stack trace:
2024/04/03 11:27:42 [error] 3061254#3061254: *10227264 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: Unsupported operand types: string + string in /home/runcloud/webapps/panelhyroes/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-payment-request.php:365

Environment (please complete the following information):

• WordPress Version
• WooCommerce Version 8.7.0
• Stripe Plugin Version 8.1.0
• Browser [e.g. chrome, safari] and Version
• Any other plugins installed

Additional context Add any other context about the problem here.

[github-actions[bot]]

Hi, This issue has gone 150 days (5 months) without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest version, you can help the project by responding to confirm the problem and by providing any updated reproduction steps. Thanks for helping out.

[github-actions[bot]]

This issue has gone 180 days (6 months) without any activity.