adyen-shopware6 icon indicating copy to clipboard operation
adyen-shopware6 copied to clipboard

[PW-7946] - Removed option to store payment state using store api (headless) - subscribed event has been removed.

Open AndreasA opened this issue 3 years ago • 5 comments

Describe the bug Before the merge of PW-7218 the context switch event was used to store adyen payment state data upon selecting the payment method.

Since the merge of PW-7218 this seems to have been removed.

I guess the intention was to move that logic from the PaymentSubscriber to the ContextSubscriber.

Versions Shopware version: 6.4.18.0 Plugin version: develop / 5f58d08a345da9566dec6d047329030bb55158cc

To Reproduce See description.

AndreasA avatar Jan 17 '23 11:01 AndreasA

Hello @AndreasA,

Thank you for raising this issue. We created an internal investigation ticket to revisit the logic in that part of the plugin.

Best Regards, Can

candemiralp avatar Jan 23 '23 13:01 candemiralp

Hello @AndreasA,

I would like to inform you about that we are still investigating how we can re-support that functionality. Indeed, it is a breaking change for the headless integrations, which shouldn't be the case in a feature version upgrade. I will inform you again after finding a non-breaking implementation for this issue.

During this time period, could you please share your use-case? As a follow-up question, are you sending the fresh stateData obtained from the component/drop-in to the Shopware 6 backend?

Best Regards, Can

candemiralp avatar Feb 09 '23 11:02 candemiralp

@candemiralp Currently the plugin is set to the last version before this change, I just noticed that with the next update there will be an issue. The stateData would usually be set upon payment method change on a separate PWA that only uses the store-api and has not direct Shopware 6 frontend (headless).

AndreasA avatar Feb 09 '23 17:02 AndreasA

Hi @candemiralp has this been fixed with the recent 6.5 support being added to the plugin or is it still open?

if it is still open, when will it be fixed?

AndreasA avatar Jul 12 '23 04:07 AndreasA

@candemiralp Do I understand this correctly and the payment state data from e.g. card component is now sent as a parameter upon calling the handle-payment method? If so, I guess I could just remember the data in memory or session storage and include it upon calling the handle-payment method now instead?

AndreasA avatar Jul 20 '23 10:07 AndreasA