facebook app is misconfigured for mobile access - facebook

Got this error when trying to use a my Facebook app on an iPad with Safari.
"mobile version of app is unavailble because it is misconfigured for mobile access"
The app works fine when used in a Safari browser on a desktop. Anyone a suggestion for a solution?
Only see this option in the settings of the app "Mobile Web URL" which has the same value as my "site URL".

I found if using authorization, I had to use m.facebook.com/authurl rather than www.facebook.com

If you're using SSL and visit https://apps.facebook.com or https://m.facebook.com on a mobile device, and your mobile URL is http:// (not https://) then you receive this error. I imagine the same happens through the Facebook iPhone app if secure browsing is enabled.
Adding the trailing slash at the end of my URL also seemed to help, but it may have been the above SSL issue confusing me.

Related

Capacitor Browser issue with Redirect

The Capacitor Browser is having issues with web redirects - with different behaviors in iOS and Android. I think this is a very buggy plugin, but maybe I'm missing something...
My Ionic app uses the Capacitor Browser plugin to present a Federation Login page. There is an "authentication URL" returned upon successful SSO login - or if the user is already logged in then there is an immediate "authentication URL" redirect.
Here's what I am seeing...
iOS: for a first time login, the web redirect works and deep links back into my app -- no problem here. However, if SSO is active, then there is an immediate redirect which the Browser ignores. I can see the URL change, and it works if I open it in a separate mobile web browser.
Android: for a first time login, the web redirect is ignored and the user is left stuck in the browser. Again, if I copy the URL to a separate web browser then it deep links back into the app.
Has anyone done this successfully or have any workarounds? I've tried the "Cordova" and "Awesome" InAppBrowser versions of this plugin, and they don't redirect at all (although they have a bit more control over closing the browser, etc.).
I encountered a problem like this on Android lately,
The in app redirection was down on Android 12, users where locked on a white screen where we normally get the token in the url and redirect in app.
In my case it was related to this :
https://developer.android.com/training/app-links/verify-site-associations?authuser=2
The chrome browser was trying to check this file to verify the hash of the app to perform the redirection but it was unavailable due to internal network configuration, so it was locked.
This check seems to append on Android 12 only, and needed a re-install of the app on users devices (cache on in app browser ?).
Hope this can help.
(Ionic 6 Capacitor)

Mobile users unable to access Facebook app

My application works with descktop browser but it shows "The page you requested was not found." error by mobile browser. (the screenshot was made by chrome simulator but it shows same by real mobile(android) too)
I already set mobile site url to "Mobile Site URL" field from Setting tab
and turned on "Website - Mobile" checkbox on App Details tab.
I spent all my day trying to find solution without success. Hope someone can help me.
Unfortunately this problem can't be solved :(
https://developers.facebook.com/bugs/1051463851558493/
Hey all,
We recently identified a handful of apps misusing our mobile App
Center to redirect people to unauthorized sites. As a precaution, we
have temporarily turned off the ability for developers to direct to a
destination URL for any app in the "Mobile Site URL" field on the dev
site.
We will be in touch shortly to discuss specific next steps with your
team.
Best,
The Facebook Team

Self-signed SSL certificate when developing app on Facebook

I'm new to developing apps on Facebook, I encountered some problems.
As it turned out facebook requires my Canvas URL to use SSL.
I use Open Server which uses it's own SSL cert. I have set Secure Canvas URL as following "https://localhost/"
https://localhost/ opens in any browser fine, But when I try to open facebook app it says that it doesn't trust the certificate because it's self-signed with the following error
"sec_error_untrusted_issuer"
(I am using Mozilla).
And it doesn't provide me with option to trust this certificate.
So what can I do?
I just want to make a "Hello World" app on facebook. And I don't want to buy any certificates.
I'm dealing with this question as well.. (I find IE11 won't show the app either).
It does seem that a facebook app/tab page will show in Chrome with a self-signed cert - so you could try doing your development / testing in chrome as a workaruond.
In firefox this workaround seems to work as well for local development purposes: right-click in the frame for the facebook app, select 'This Frame' -> 'Show only this frame'. It will open just the facebook app, and give a warning.. click 'I understand the risks', the confirm/add the exception. When you then return to the facebook page with the app frame, your app should be displayed

"Either this application has not configured its Mobile Web URL or the URL could not be verified as owned by the application" error

We have a post on a FB wall. It points to http://tinyurl.com/{something}.
When the link is clicked in a non-mobile web browser, it works fine: TinyURL redirects the user to our web site using the appropriate URI including a special querystring.
When the link is clicked in a mobile web browser on my Android, it fails with the error in the title of this question.
When the link is clicked in the FB native app for iPad and in Safari on the iPad, it works fine.
I have tried adding our URL to the Mobile Web setting in the Basic Settings tab of the FB App configuration. That results in all links pointing directly to the root of our web site with a funky set of parameters in a querystring -- in other words, it doesn't follow the TinyURL in that particular case. The funky parameters include "refid", "ref", and "ft".
So primarily my question is: Why, when I specify the URL in the Mobile Web setting as described in the previous paragraph, does it redirect to our main URL instead of the TinyURL link originally called for?
I think this is something Facebook broke very recently (perhaps even today?). When a user clicks on any links to our app from inside the Facebook native iOS app, they get this error "Either this application has not configured its Mobile Web URL or the URL could not be verified as owned by the application. Unable to redirect." We had never set a Mobile Web URL previously, and everything had been fine since we launched the app over a year ago. We sent all mobile clicks to the same URL's as desktop browsers and handled the mobile rendering server-side. We have not changed our application domain inside the App Settings or anything like that.
In the App Settings, can set a Mobile Web URL to our homepage and the link works (and the error message goes away) but that's not the desired behavior at all - it would mean that all links end up at the same Mobile Web URL regardless of what the link was!
Was this change made on purpose by Facebook and if so why? There's been no mention of this whatsoever on the Developer Blog.
Update 3/21 8:10am PST:
I've since found this to be a widespread problem, not just for a few apps. Just by clicking around I've seen this error on posts to weather.com, youtube, msn.com and a dozen others. It happens on both clicks from the Timeline as well as the News Feed (although strangely sometimes the same post works on one, but not the other!), and from the m.facebook.com mobile web app as well as the native iOS app.
I commented on http://developers.facebook.com/bugs/302635863137683 but no word from Facebook yet. I can't believe more people aren't talking about this right now, this is a major bug.
In your app, go to Settings -> Add platform -> Website
Add both, Website URL and Moblie Website (Yes, you need these both), then your app will be able to be opened from facebook native app.
You will also need the FB Canvas.
Same here, I recently noted that all links of items shared with our Adroid or iPhone app are broken. This only happens with the mobile version of Facebook the Desktop web version is still working. What is actually wrong on the mobile version is that the original shared url is replaced with a m.facebook url that ends with "?ref=unknown&refid=0&ft=fbid.332036910178718%3Ainterface.m_touch%3Ac.m" When user click on it Facebook is redirecting the user to the App's "Mobile Web URL" + "?ref=unknown&refid=0&ft=fbid.332036910178718%3Ainterface.m_touch%3Ac.m" instead of the original shared url.
My opinion is that this is an issue of Facebook that is redirecting the url to the wrong location, "Mobile Web URL" instead of the original post url.
Ok not working. What is going on, 1st directed to something about itunes url. I am on an Android not an Iphone. Sad state when an disabled person is unable to gain access the same as others. This is bad for all users.

Mobile version of the app is unavailable because it is misconfigured for mobile access

I don't see any requirements aside from the registration one here:
https://developers.facebook.com/docs/guides/mobile/web/#register
I've set the Mobile Web URL to the secure canvas url, but am receiving the error Mobile version of the app WishGenies is unavailable because it is misconfigured for mobile access
The only other thing I see presumably has to do w/ the Auth Dialog page, but that just renders a blank screen for me.
Any suggestions?
Ok, so I finally figured out a little about this problem...
Somehow, when the request sends a referrer you get this error ( like a link through a http site ) linking from a https site, or getting the referrer out results in a correct redirect to the mobile site ...
Removing "app-domains" from your basic Facebook Settings will fix this problem.
Facebook bug: http://developers.facebook.com/bugs/124226157757972
The URL for the mobile version of your app must be distinct from the URL for your desktop app. It's a weird constraint, but that's probably what's keeping your app from working.
I had to set Mobile URL to blank under Basic App Settings. And also I had to add rel="noreferrer" on my website. I believe this makes the Mobile URL referrer match the actual referrer because they are both an empty string.
It would probably also work if you had a mobile site URL other than your desktop site and the referrer matched when you direct users to Facebook.