Unable to make a booking in chrome incognito session

[gzim-joinfella]

Found a bug? Please fill out the sections below. 👍

Issue Summary

We are integrating cal.com an an embed in our web app portal where we allow our customers to make appointments.
Something we noticed is that when our customers are in incognito session in chrome, they are not able to make the appointments at all.

The root cause is that in incognito, chrome settings are set to block 3rd party cookies by default.

Steps to Reproduce

1. Open chrome incognito
2. Navigate to our custom React.js web portal
3. Try to use cal.com through the embed

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Technical details

• Chrome, incognito
• 3rd party cookies not allowed

[milospuac]

Hi there. Thanks for reaching out.

Our team will investigate this. Are you using our V2?

[hariombalhara]

This is an issue due to Rainbow kit integration. RainbowKit.tsx seems to use wagmi which uses localstorage which isn't accessible in incognito mode. It should be fixed there cc @PeerRich

Because Rainbow isn't needed if EventType doesn't have it enabled, it shouldn't cause booking pages to break in other cases
This recently merged #4409 PR fixed that and thus the error no longer comes in Event Types not using RainbowKit

[gzim-joinfella]

@hariombalhara any ideas if there's something we can do about this as a quick workaround? We had this issue reported to us three times by different customers.

It is frustrating because they just paid for the product but can't progress on making the appointment with the coach.

thanks for looking into this 🙏

[hariombalhara]

@gzim-joinfella If you take the latest pull of main, it should be fixed unless you have Rainbow kit integration in your Event Types.

[gzim-joinfella]

@hariombalhara I am using the hosted cal.com version at http://app.cal.com/ via an iframe

[hariombalhara]

That should go live soon. cc @zomars

[PeerRich]

i believe this has been fixed a long time ago. can you try again with the most recent version?