Open caisd1998 opened 5 years ago
Hey, @caisd1998,
Thanks for flagging this issue. We have the team responsible tracking this issue, and we'll post an update here once we have fixed it!
I am seeing this issue as well on 3.3.2, except clearing cookies and local cache doesn't correct the issue if the user has closed/reopened the app after checkout. (I'm not sure why that makes a difference). However, launching the same checkout url a second time in a webview corrects the problem.
@BevTheDev I change to use UIWebview instead of WKWebview, the reason is, the way I use to clear cookie in WKWebview doesn't seem to be working all the time.
Did you found the solution?
This issue is still open, any progress so far?
@jmignac looks like this is still happening in 2022. Any planned fix or workaround?
I worked around this by loading the logout page before opening the order.
Mobile-Buy-SDK (3.3.2)
I use checkout weburl, user associate, WKWebview and http header X-Shopify-Customer-Access-Token, it's working great, until I find that if I create another user access token and use it to create a new checkout (use a new WKWebview and new X-Shopify-Customer-Access-Token header), the web checkout still shows old user's information (login status, shopping address list etc. ) Looks like it's because of cookie and the new X-Shopify-Customer-Access-Token doesn't override old one if cookie exists. My dirty fix is to delete all cookies (maybe just what related to myshopify.com domain) before I start a WKWebview for web checkout.
This relates to an old issue: https://github.com/Shopify/mobile-buy-sdk-ios/issues/841