-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecurityError: Blocked Frame with origin ... from accessing a cross-origin frame #18
Comments
To elaborate further: I am using firebase authentication for my client's square customers. It appears the conflict is as such: My app fires up authentication --> firebase produces iframe --> square injects iframe. The cross-origin issue is coming from the Square iFrame. I have added all applicable square URLs to the list of accepted firebase domains. The most odd thing of all is that once the page is refreshed, the client side exception goes away and the form renders perfectly. Unfortunately, it's obviously unacceptable for customers to have to reload the page due to a client-side error. Any advice on how to get around this issue? |
How you are rendering the form? It's appearing that is a problem when you are rendering |
As I didn't receive any response, I'm going to proceed to close the issue |
@danestves I can confirm that this issue is happening to me as well when running my project locally. The error occurs in development and production. It does not crash but it does cause obnoxious error messages when developing locally. I'm not sure if this is a Square issue or a problem with this library. But leaving this message here since there hasn't been any report of the issue on https://github.com/square/web-sdk
EDIT 02/17: I can confirm this is not only happening on localhost. |
It's appearing that is a problem from the Square side, will investigate about this |
What version of React are you using?
17.0.2
What version of Node.js are you using?
16.4.1
What browser are you using?
Safari
What operating system are you using?
iOS
How are you deploying your application?
Vercel / Next Start
Describe the Bug
Only on iOS does this error occur, but it is absolutely breaking my application. Upon sending the user to the payment form, on iOS (safari & duck-duck-go only, NOT chrome, oddly enough) the user receives the following client-side exception/error:
SecurityError: Blocked a frame with origin "http://localhost:3000" from accessing a cross-origin frame.
The text was updated successfully, but these errors were encountered: