I’ve read through StackOverflow, and replies have pointed out that this is because the sign up is done via a native app.
Could anyone enlighten me on this issue & how I can implement the solution via Bubble?
If you struggle to understand what the problem was, like I did - this error means that the user has opened your site within a specific app. This means that it wasn’t opened via a regular browser, such as Chrome, Edge, Firefox, Safari, etc. An example of this is WeChat. It has its own in-app browser. This is done to ensure security & to minimise chances of cross-site scripting where a third party steals/intercepts the information filled during sign up/sign in. How you can tell is that any link you open from within the app is loaded without it launching a separate browser. You’ll see a “jump” if the said app doesn’t have one.
If you’re not technical like me - what you can do is to create a traditional sign up/sign in form as the main method of signing up/signing in, and have sign up/sign in with Google as an alternative method. The idea is to identify where the user is coming from by determining their browser name. If user is from WeChat, for instance, then hide Google sign up/sign in. This way, your user would still have a reliable method of engaging with your site (through the manual method) rather than seeing the error.
One of the many plugins that can help you identify the browser name is Browser Device Information · BEP Plugin | Bubble.
However, do keep in mind that this method isn’t the most ideal because you’d need an exhaustive list of apps that has a built-in browser.