This is just another example of unintended consequences. Please see this discussion, for instance:
(You can view the entire email exchange for this issue, if you wish. Ticket number 64633322.)
Or what Shopify did when they forced app-bridge 4 on developers and full screen in embedded apps broke. And still hasn’t been fixed.
I have another half-dozen or more examples. I don’t wish to repeat the comments I made in the referenced discussion. But, it’s just typical behavior from your dev teams. Behavior I was assured would not happen again. And then, we’re left to scramble to find a work around.
The ability to log in as a customer is something I’ve built into every POS system I’ve worked on over the past 30 years. And it was working just fine with Multipass. We could emulate a customer down to their browser. Why aren’t they seeing the correct price? Is it a Safaria issue? A Firefox issue? Why can’t they apply a discount in the storefront but it works in the backend?
It’s called customer service. And now? Now we had to find a work around because once again, your developers are unable or unwilling to comprehend that changes are most likely going to break something because they haven’t actually researched what the real-world consequences might be or they simply don’t care.
Where was the forum discussion about the removal of Multipass and how it’s being used? There is none. This is not a trivial change. It’s a major change. And there was absolutely no input from your customers. The behavior I was assured would change from you dev teams has not. Nor, do I expect it to. Hence, our own workaround.