I'm having issues openning link to my website that I share on facebook.
By default, any link users open from facebook mobile app are opened in the facebook embedded browser.
This browser causing issues to my app so I'm trying to redirect the users to their default mobile browser, but I don't know how.
I've tried many solutions, but none have worked, the closes one was trying to do:
window.location.href="mywebsiteurl", but this prompted message on facebook app that I'm trying to leaving the app, but after accepting would leave the page just idle.
Related
I have created a react web app to authenticate with social media like google and facebook and twitter using firebase, I ran the app on a fortinet firewall to popup when anyone connect to wifi.
When I open the website from any browser I don't have any problem like chrome or safari but when connect to Wi-Fi it opens a popup web page automatically on mobile default web browser.
Then I try to make authentication with google and I had this error 403 disallowed useragent as you see the screenshot.
I need your advice if I can add any code or setting to my react web app to solve this error.
google auth error
react web app
I tried to know browser type if it is mobile web view or not but did not work or at least as far as I knew google does not support it as it declars, it appears that it does not comply with google's security policies
I have a Nextjs web app with Firebase Auth. I only allow my users to login with Google.
All my traffic is coming from social media apps which have an embedded browser. So on launch day I learned that signing in only works directly from a browser like chrome or safari but not within a webview within an application. This is a nightmare.
I tried switching from signInWithPopUp() to signInWithRedirect(), but still same issue.
error 403: disallowed_useragent
This app doesn't comply with Googles webview policy.
Has anyone encountered this problem?
What I'm doing is a login with social networks, this works very well but I have a doubt. I leave pictures of what I do and what I'm getting to be a little more understanding. I am using js library OpenFB.js. With twitter even I can not do much but what matters to me most is that if you can do this.
This is what happens is my application :
This is what I would like to happen, to open the application installed.
If you are already logged into Facebook, you will not see the screen on the first image otherwise the screen will appear. Based on the images that you have posted, in order to see the screen on the second image, you have to be logged in. The second screen is the new login flow of Facebook where you can look at the permissions the app is requesting for and if you tap on the edit link, you can refuse certain permissions that your app is asking.
Note that once you grant these permissions, you may no longer see this screen until you remove the app from your Facebook settings.
I'm in the process of migrating a Google App Engine / Java based app over to the new Google Apps Marketplace.
The old app enabled users to install the app without actually being on the marketplace page by leveraging a redirect URL extracted from a user click on the "Add It Now" button from the old marketplace page. This URL triggers an account login button that is then followed up by the app install. The URL was of the form:
https://accounts.google.com/AccountChooser?continue=https://www.google.com/enterprise/marketplace/interstitialRedirect?domain&productListingId=&index=0&followup=https://www.google.com/enterprise/marketplace/interstitialRedirect?domain&productListingId=&index=0&service=marketplace&passive=true&ul=1
I've tried using the redirect URL generated from clicking on "Integrate with Google" from the new marketplace page but it goes through the authorization page then leads me to a blank page (though the app is successfully installed). The blank page issue is likely related to the following issue - Chrome Web Store app install redirects to a blank page
The new URL is of the form:
https://admin.google.com/OauthTosCombined?appId=&redirectUri=https://apis.google.com/additnow/signin.html?applicationid%3D%26callback%3Dtrue%26parenturl%3Dhttps://chrome.google.com%26appfinder%3Dfalse
Has anyone been able to successfully enable this scenario? Thanks in advance!
One supported means of allowing an admin to install your Marketplace from a web site is the Integrate with Google button which may be worth considering ( https://developers.google.com/apps-marketplace/button?hl=ca ).
Does the install button from the Chrome Web Store standalone page not work correctly, or is it only when attempting to utilize the URL from the button on the page elsewhere? If the former is not working correctly, then it does sound like the linked to issue. Including the URL to the standalone Chrome Web Store page and an example of your app manifest would be helpful in identifying whether this is a bug.
I am developing a mobile web application, some times it is showing that "the mobile version of the app is unavailable because it is misconfigured for mobile access". Why this is happening? I noticed that it is happening when user is logout form Fb and try to come back to the app it showing login form after login it showing the error.
Please help
I had this problem and what was seemed to be the issue was that if you just got redirected from Facebook to your app, and then instantly redirected back to apps.facebook.com/my-app/sub-uri then Facebook raises an error.
This is what I was doing and what I ended up doing:
I tried to authorize my app, authorization through redirect to Facebook and after authorizing the app redirected to my apps.facebook.com/my-namespace/next-step.
Visiting with a mobile device and redirecting back to Facebook, after Facebook just had redirected your user to the app, caused an error.
I then added a piece of mobile sniffing code and if the user was mobile it redirected internally to /next-step instead of going to apps.facebook.com.
Initial request flow for mobile:
my.domain.tld/authorize
-> graph.facebook.com/oauth/authorize
<- my.domain.tld/authorized
-> apps.facebok.com/my-app/next-step
error
Which I then changed to this if the user was mobile:
my.domain.tld/authorize
-> graph.facebook.com/oauth/authorize
<- my.domain.tld/authorized
-> my.domain.tld/next-step
All working fine
Check your's Native iOS or Android Apps Bundle ID in Facebook developer page