Okay, I'm at my wits end - I can't figure this one out. If you go into Facebook in Safari on a desktop/laptop and in the search bar type the name of my app: "Hopple Hop", and then click on the app itself (not the app page), instead of launching the app, it triggers this error message in Safari:
"Safari can't open "fbrpc://nativethirdparty/f?appid="
Followed by hundreds of characters. Basically, it's a big long URL string, in the "fbrpc://" protocol, and it tries to launch directly into the browser as-is.
As you can imagine, this is not the intended functionality of searching for my app. The intended functionality is that they type "Hopple Hop", click on it, and the Facebook canvas game starts. If you go to
https://www.facebook.com/appcenter/hopplehop/
You can see it there. And if you click "Play Now", it launches properly from:
https://apps.facebook.com/hopplehop/
I know it's probably a configuration issue. There is also an iOS app to go with it.
I'm not sure what the end cause was, to be honest. It appears to be a very specific configuration issue with my phone / Facebook account and the way I've authorized the game. It doesn't seem to be an issue for anyone else. I don't unfortunately know the root cause.
But if anyone else sees this error, it's likely only you are seeing it.
Thanks,
Glen
Related
I've been using the Facebook Plugin for years, on dozens of websites, but all of a sudden, I can only see the page's facebook header, the actual feed appears only as a spinning icon. This is on my desktop and mobile device, feed is at the bottom of the page. https://saltydogfestival.com
screenshot_mobile
However, my co-worker in the desk across from me tried it on his desktop and laptop and the feed loads just fine.
I'm not a page admin for this particular feed.
I have this plugin for other facebook pages, for which I AM an Admin, and those don't show up for me, either. I've tried using Chrome and Edge.
I'm knocking my head against the wall with this.... or maybe it's something so simple that I'm not seeing it... Suggestions??? Please save what's left of my sanity!
I think this issue has affected many sites including mine. I used a third party plugin recently that's said to no affect page speed. It's called "Buttonizer - Smart Floating Action Button" you can add a FB messenger button also and add call to action and any they button as well. I have disabled the Facebook chat one for now. If you can update me if it's now work for you that would be great as I'm in the same boat. Email mtgusto#outlook.com
Edited - bug seems resolved
This is what worked for me:
Go to Facebook Developers - Page Plugin and configure the 'widget' with desired params.
As you change the parameters the preview should update & show. If it doesn't, try signing out.
Click "Get Code" beneath the preview. I used the JavaScript SDK method.
Copy & paste the first piece of code after the < body > tag.
Copy & paste the second piece of code where the box should appear.
Previous answer - leaving here for posterity / reference
It seems to be an issue with Facebook that occurs when the visitor is signed in to Facebook. Try viewing the page in a private window or reload after you have signed out of Facebook to see if it loads when you are not signed in.
There's more information on a Facebook Developers bug report, which was just marked as closed 8/26, although it still appears to be happening: https://developers.facebook.com/support/bugs/584988619248795/
This other community thread has a work-around - look for Dave's comment: https://developers.facebook.com/community/threads/1018223139108570/
Trying to get my head around OAuth 2.0. I am building a cross platform google drive app using PhoneGap Build and JQM.
I am able to format the request URL correctly and on both iOS and Android. It prompts the user for ID/PW using InAppBrowser (tried child browser too). Next user gets prompt with blue button on web page to "Allow Access" just like on other google web sites/apps. On Android all is well user taps allow access and callback finds the success code and I can grab the token. On iOS I get a "Load Error" message in the status bar of InAppBrowser but I can't trap the error to see what it is. It seems as if the redirect parameter breaks things before the startLoad or endLoad event can be called to trap success/failure in the response from Google.
Playing with oauth2-playground my URL looks correct and like I said it is working fine on Android.
Anyone have any ideas what differences I need to look at with regard to iOS? Been stumped here for a couple of days. Any and all help greatly appreciated.
I have tried redirecting back to http//localhost and http//localhost/afterOauth.html where afterOauth.html is a page in the app to give the redirect something to call the startLoad/endLoad event.
Update: I really think the problem has something to do with the redirect I give the original Google request. If I change "localhost" to urn:ietf:wg:oauth:2.0:oob which shows up in the google documentation both Android and iOS behave the same. They take me to a page saying "Please copy this code, switch to your application and paste it there" With the code=4/MyCode below it.
Also, I added a loaderror callback. It does not fire on Android but does on iOS giving error code -1004 and error message: could not connect to the server. However in the event.url of this loaderror it clearly shows the code=4/myCode. What is the missing link here for iOS and successful OAuth between Google?
I have made an iphone app. The app calls the webpage and displays the content. Server side coding is in php. The problem is I have several links in the webpage. When I click on the link in the webpage it opens the entire page and I am no longer able to go back to where I was.
I tried iframe but not all the website support it like google, facebook. What I am looking is someway to open the link in browser or launch the another app, like the app of facebook. I have quite thoroughly searched for the solution without much luck.
Any pointers would be greatly appreciated.
Thanks
To implement navigation for UIWebView you can do the following: create two buttons, one for going forward in history and one for going back. And here is the code for that buttons you must include:
//For going forward
if (yourWebView.canGoForward)
{
yourWebView.goForward();
}
//For going back
if (yourWebView.canGoBack)
{
yourWebView.goBack();
}
I am trying to set up a tab with a link to a contact form from my site on Facebook.
I developed the 'app' through the developers site and have set up the page tab.
I've saved the app and it saves it fine (displaying a message saying changes were saved but it might take some time to propagate across all servers.)
Well I waited an hour and I still can't add the tab to my page. I tried locating the app page directly using the namespace, but I get an error message saying:
"[My App] cannot be displayed because the app is misconfigured."
I don't know how it is misconfigured? There are no errors when saving, so I don't know what the issue is or how to go about fixing it. There are no problems with the app that I can see... how am I supposed to know what's wrong with it?
All it is is a page tab. I've put the link to the page tab in, I don't have a secure page (https) so I have left this box blank but I don't know what to do now.
Any ideas how I can find out in what way it is 'misconfigured'?
This error usually occurs when you try to view the App Center page for the app when the app doesn't have the 'App Details' tab settings populated.
So instead of:
https://www.facebook.com/appcenter/APP_NAMESPACE
Make sure you are loading:
https://apps.facebook.com/APP_NAMESPACE
That page will display hints (if you are admin or developer of the app) on what you are missing.
And, adding to the answer already given by #Donn Lee, which pointed to the right way, you must also ADD A PLATFORM in settings, in https://developers.facebook.com/apps/APP-ID/settings/
I've got a form in a web page with an action that is "mailto:email" (where email is a real email address). When I load this page in Mobile Safari in regular mode (ie, not launched from home screen with app-capable mode), this works fine - after I submit the form, the email app comes up. However, when I'm in app-capable mode and have launched from the home screen (so, no Safari chrome), and submit the form I get the error "URL can't be shown". However, a regular mailto: link (ie, not in a form) does work when in app-capable mode.
Has anyone else noticed this? Any workarounds? Are forms disallowed in app-capable mode?
Thanks,
Elisabeth
This accurately describes the issue. There is nothing wrong with the mailto link, the mailto link fails to load. Often the webapp crashes.
The funny thing is that tel: link for telephone numbers work fine.
window.location.replace does in-fact work. Thanks!
Here is the jQuery to fix this automatically...
$('a[href^=mailto]').click(function (event) {
event.preventDefault();
window.location.replace = $(this).attr('href');
return false;
});
I think I've figured this out. I noticed when in app-capable mode, any http link will take you out of the app and launch a separate mobile safari window, take you to the page and show the Safari chrome. Makes sense (typically one wouldn't link to anything from an "all in one" app-capable web app. I noticed this because I implemented a 4 page app with my own "tab bar" at the bottom and was linking amongst the .html files with plain http links in the a element. When I replace this with a javascript function to load the pages using document.location.replace this doesn't happen.
So, on the form - I think what must be happening is that because I'm using a scheme (in this case, mailto:) somehow the browser is needed in "regular mode" to interpret the scheme and do the right thing by launching the email app and this clearly doesn't work when submitting a form. I haven't yet found anything in the Apple documentation specifically about this, so if anyone knows the technical details, please do post!
UPDATE: I did find that I can access a server side script using a form in web-app mode, so I'm still curious about the mailto: issue, if anyone has an answer.
Thanks,
Elisabeth
I am having the exact same issue with mailto links not working in the web capable mode. I just got done submitting a bug report to Apple. Let's see what happens, meanwhile I found another dev. platform for web apps that works in web capable mode and mailto links work, but it is funny how it works in this even--it is not as fluid as it is in Safari. Because even in this new web dev tool that I found, it closes your app and launches mail client, which is lame. In Safari it just slides in a mail window that slides back out if you hit cancel or send--it doesn't actually close your app.
Here is a workaround that does not depend on JQuery:
aTmp = document.createElement("a");
aTmp.href="mailto:example#example.com?subject=Test&body=Hello.";
aTmp.click();
Update: To run this code from a bookmarklet you have to wait about 1000 ms before the bookmarks bezel is closed and the browser is ready to respond. I realized this by wrapping the code in a setTimeout function.