Closed Asiyil-K-Alaswad closed 2 months ago
I am also facing similar issue . Did you find any solution ?
I am also facing similar issue . Did you find any solution ?
No. it is still persistant.
I have the same issue Already added all urls to allow in the browser and it still persists
Hi @Sejal-svg @Asiyil-K-Alaswad. Can you please share a capture of how these settings looks like?
@mlagus which browser are you using?
@paulperez-dev which browser are you using?
Chrome Version 125.0.6422.142 (Official Build) (arm64)
@mlagus please click on 'Site settings', and share a capture of the configuration.
@paulperez-dev why? what u wanna see? The list is long in there
@mlagus the popup permissions specifically for the FF site.
@paulperez-dev the popups and redirects are allowed
In run mode i get this wierd icons generated. In test mode ther look correct with apple and google logo. Dont know if its connecting to the same problem
Hi @Sejal-svg @Asiyil-K-Alaswad. Can you please share a capture of how these settings looks like?
I rebooted computer, tried to access flutter flow. it was just black! I emptied cashe and reloaded and got this in console "Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox." I found this thread: https://stackoverflow.com/questions/78011724/warning-third-party-cookie-will-be-blocked-learn-more-in-the-issues-tab Could it be belonging to that problem?
I got this from google console: "
The error "Blocked opening ... in a new window because the request was made in a sandboxed frame whose 'allow-popups' permission is not set" indicates that your web application is trying to open a popup window (likely for authentication with Firebase) from within an iframe or a context that has sandbox restrictions. Browsers enforce these restrictions to prevent potentially malicious behavior from embedded content.
Here's a breakdown of the issue and how to fix it:
Understanding the Error
Sandboxed Frames: When you embed content in an iframe, you can apply the sandbox attribute with various restrictions. One of these restrictions is allow-popups, which controls whether the iframe is allowed to open new windows.
Security Measure: This is a security feature to prevent embedded content from opening unwanted popups, which could be used for phishing or other malicious purposes.
Solutions
Adjust Sandbox Attribute: If you control the iframe where your code is running, modify the sandbox attribute to include allow-popups:
<iframe src="your_app_url" sandbox="allow-scripts allow-same-origin allow-popups"></iframe>
Open Popup from Top-Level Window: If you can't modify the sandbox attribute, restructure your code to initiate the popup opening from the top-level window (the main browser window, not within an iframe). This might involve using postMessage communication between the iframe and the parent window.
Alternative Authentication Methods: Consider using authentication methods that don't rely on popups, such as:
Redirect-based flow: Firebase Authentication supports redirect-based flows where the user is redirected to a login page and then back to your application after authentication.
In-page authentication: Implement a login form directly within your application's page.
Code Analysis
Looking at your provided code snippet, the issue likely stems from the window.open call. If this code is executed within a sandboxed iframe without the allow-popups permission, the browser will block the popup.
Debugging Tips
Check Console: Open your browser's developer console to see if there are any additional error messages or warnings related to the popup blocking.
Inspect Sandbox Attribute: If your code is within an iframe, inspect the iframe element in the developer tools to see if the sandbox attribute is present and what restrictions are applied.
Important Considerations
User Experience: Popups can be disruptive to the user experience. Consider whether alternative authentication methods might provide a smoother flow.
Security: Always prioritize security when implementing authentication. Carefully evaluate the risks and benefits of different approaches.
If you can provide more context about how your application is structured (e.g., whether it's embedded in an iframe, how the authentication flow is initiated), I can give more specific guidance.
Data used to understand this message
Jump in here and upvote this problem https://community.flutterflow.io/ask-the-community/post/unable-to-authenticate-using-google-hYFpowS2i2LRDzx
@Asiyil-K-Alaswad Have you been able to fix it?
@Asiyil-K-Alaswad Have you been able to fix it?
No luck. The only other thing I haven't tried is running it on a safari browser to see if the problem is solely from chrome, but I don't have access to a Mac/IOS device.
Hi @Asiyil-K-Alaswad! Can you please share a capture of the domains added to Firebase Auth?
@paulperez-dev
@paulperez-dev i have the same settings as @Asiyil-K-Alaswad its all set according to instructions. Why does FF test mode work but not run mode?
Its work fine with testing it here, so it must be specific to flutter flow or firebase settings https://gal-demo.withgoogle.com/
I also have the same issue but in RUN mode. When I use desctop Flutterflow it works. A bit frustrating... BTW, it was working before and one day it stopped... I do not recall any changes I made to my system, browser or project.
This issue probably has to do with that the permissions in an <iframe>
has to be explicitly allowed in HTML using the attribute allow='...'
. The site settings alone are not enough. The same thing why the camera and microphone don't work in debug mode.
@Tyg-g Yeah it's definitely that. The issue is controlling an elements attribute in FlutterFlows UI is not really something the developer could do.
Having the same issue. Google auth pop up not showing up.
In test mode it says, this url is not added as authorized domains which it is. And in run mode it says unable to establish connection with pop up, browser may have blocked the pop up.
Any work around for this?
I want to use razorpay. For razorpay FF required firebase auth.
Well. the problem is that for the last 4 months i was using RUN mode about 200 times to test my app, and it was working. and one day it stopped. I did not change anything in login page at all... Although there was a new flutter update... So concluding, is there anything I can do solve it or shall we wait for FF people to fix it?
In test mode it says, this url is not added as authorized domains which it is. And in run mode it says unable to establish connection with pop up, browser may have blocked the pop up.
Any work around for this?
Test mode: you have to add the URL from the
Run mode: Click the [Wiew Full Screen] button.
I solved it.
In test mode, when you see error in snack bar like this
Open developer console on google chrome and there will be a URL printed within an error from firebase auth which you can add to authorized domains in firebase. Wait for a minute, it should work then.
@abhibalani do you mean the url from this error?
@mlagus
This message is what I am referring to.
Hope it helps.
@mlagus I am getting the same error on run mode.
But this working in local environment setup with FF desktop app for windows.
@abhibalani Yes as said before, i only have the problem in run mode
I have this message from support: Yes, Seems google auth recently changed something in their end that requires a header to be added to the launcher, i notified the team responsible for our bug triage to make it a priority and identify the issue, seems they assume it's happening in the test mode not run mode They will triage it and will prioritise the fix to roll out in next releases. So I guess I will be fixed.
I have this message from support: Yes, Seems google auth recently changed something in their end that requires a header to be added to the launcher, i notified the team responsible for our bug triage to make it a priority and identify the issue, seems they assume it's happening in the test mode not run mode They will triage it and will prioritise the fix to roll out in next releases. So I guess I will be fixed.
Thanks for the info. This issue was raised 2 weeks ago.
I am not very sure now if it was right choosing FF for frontend development.
I haven't received any response on my ticket and my email that I sent 3-4 days ago.
I am finally taking a manual API route to integrate razorpay in my app.
Any update? This is happening in run mode for me - test mode and publish mode works fine.
I had the same problem. Enabled the Windows (alpha) checkbox in platforms tab settings. Works for me.
Hi @Asiyil-K-Alaswad, can you please try disabling this option?
If this does not work, can you please reach out to support@flutterflow.io? They can better assist you with ensuring your project is configured correctly!
@paulperez-dev I did disable that option and i still have the same error (run mode) Ive already reached out to support
@Asiyil-K-Alaswad and all! Ive talked to FF support and they will have a fix for this in production next week! This week its in beta! Yay!
did the fix come yet? I am seeing this when attempting to login with my PWA published on custom domain and using the google authentication...
Can we access your project?
Current Behavior
Expected Behavior
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
ITEelsn1z4pNj7xZ1ZP6Y/lFgQMxQUB+bZ0vlO1FGE0YNb2uBJoteMnuaXddUt+kelZHMFSJhmUGpsLuhobDJ8E6OTStY6V607tTFj3weD2iVbaRELuKY3FRHdpMBUy0yruFnxQnGOpYWHdn73GLcq3qNleeY8aSfxBlZ7vfcPo=
Visual documentation
Environment
Additional Information
additional triage I have done :