Type error upon calling payment-methods store-api (headless) as PaymentMethodRouteResponseSubscriber sets an object for an expected array

[AndreasA]

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

Versions
Shopware version: 6.5.8.12
Plugin version: 3.16.0

To Reproduce
Steps to reproduce the behavior:

1. Call store-api for payment methods (headless)

Expected behavior
No type error and correct response.

Code info
At https://github.com/Adyen/adyen-shopware6/blob/3.16.0/src/Subscriber/Response/PaymentMethodRouteResponseSubscriber.php#L163
you return now null or a PaymentMethod object. which is then set https://github.com/Adyen/adyen-shopware6/blob/3.16.0/src/Subscriber/Response/PaymentMethodRouteResponseSubscriber.php#L148C29-L148C51 to an array. this results in a type error.

potentialy solutions:

• set the object and verify store-api correctly serializes it.
• call ->toArray on the object
• json_encode(json_decode on the object.

[AndreasA]

any news regarding this?

[adyen-integrations-support]

Hello @AndreasA ,

Thank you very much for all the required information.
Could you please update the plugin to the latest 3.16.3 and check if the issue still persists?
Additionally, our team will investigate this issue and keep you updated.

Best Regards.

[floddy-newport]

Still an issue in 3.17

[AndreasA]

I did create a one line change PR that would fix this #532

Not sure why this still hasn't been merged, the PR exists for several months now and has basically no changes.

[adyen-integrations-support]

Hi,

Thank you for your patience.

We are currently investigating the root cause of the issue you reported. Our team is working to identify and resolve it.

We will keep you updated and notify you as soon as we have more information or a resolution to share.

Best regards

[adyen-integrations-support]

Hi,

Thank you for your continued patience as we work on resolving this issue. Our team is still actively investigating the root cause and working towards a solution.

We appreciate your understanding and will keep you updated with any progress or developments. If you have any additional information that might assist us, please feel free to share it.

Best regards

[AndreasA]

Additional information, see my PR: #532 that's everything that is needed to fix this (at least it was when I created the issue).