I've created a real photobooth which is a camera in a housing with an raspberry pi running a webserver and handling all the photo stuff. The frontend for this is an tablet with a browser pointing at the webserver running on the pi (on local network).
The functions are pretty simple: Take a picture (or a strip of four), view the gallery, download and mail the photos. Now I'd like to integrate a photo upload to Facebook.
Is this possible with an application that is not hosted public? The booth has internet access via 3G or available Wifi. But the pi's webserver is only available locally.
My first Idea was to have the postback send to a script running on my website that redirects me hardocded to the local adress. This is working, but is this allowed?
For publish permissions I need to submit the app for review. But how can Facebook review my app? It's not available public.
Thank you in advance.
Arne
Related
Lets assume that the intranet has SSL and the users are using Chrome in Android, will progressive web apps work? Will it have offline caching?
Lets assume also that the push notification service will be sitting in their network, will it also have notifications?
A Progressive Web app works where any website works, as long as it has a service worker, a manifest and SSL. When people are outside the company, they'd see the offline version.
Push notifications might work as well, but you need to be inside the company network to receive them.
Creating an AIR desktop application that has the ability to upload images to a Facebook user's account.
Even though this is a desktop application, in order to integrate with Facebook you need to embed a 'webview'. So I am confused as to how I should define this on Facebook? From Facebook's point of view, is this a web application or a desktop application?
https://developers.facebook.com/docs/facebook-login/review/requirements#platforms:
“Desktop apps should submit a Web platform and include detailed screenshots or a screencast of the integration.”
Choose a dummy address for the Website platform (such as http://localhost/), and mention the fact that this is not actually a website app, but a desktop app, very explicitly in your review instructions.
I am using a proxy for logging purposes and blocking malicious sites.
I recently installed a squid3 proxy setup with SquidGuard. I have my iOS devices connected to it and all it working well except for 2 apps. The iOS Facebook and Twitter app will not update content, and eventually times out. I actually want the content to update. This only happens when coming out through the proxy. If I turn wifi off and connect 4G it works. All other internet apps on the iOS device work except Twitter and Facebook. Any thoughts? I am using a very simple proxy squid.conf file and SquidGuard is blocking a bunch of spyware/ad domains, but not facebook.com or twitter.com or akami.com/akamihd.com. Thanks!
By the looks of it, the Facebook app for iOS does not support proxies at all. On my iPad, for instance, the app tries to connect directly to Facebook irrespective of proxy settings. One workaround is to redirect all of your device's traffic through a device that performs intercepting proxying
We plan to manufacture a device that we want it to communicate with Facebook. If the user presses a button on the device, we want something to appear on users wall as a post. It means that the device will post on behalf of the user on Facebook.
As we see from the Facebook developer page, the types of applications are a Facebook app, a web app or a mobile app. The thing we have just explained does not belong to any of these categories. For instance, it is not a web app because the device does only support http connection but does not have a built-in web browser. It is not an Andorid or iOs app because the operating system in this device is none of these.
What would you suggest for this kind of application?
Thanks in advance.
Definitely look into http://developers.facebook.com/docs/authentication/devices/
Your other decent option would be to run an HTTP server on your device that users could connect to from a computer or phone to authenticate.
Once authorized, a simple HTTP request is all that it will take to share anything.
Edit: Just noticed that Facebook is no longer accepting applications for new partners with the auth device pattern. This is definitely what you want. You could try contacting them anyways.
Possible Answer = make it web app but dont forget the facebook policies about the user privacy issues. Your device can send a signal to your server and server can make the post i think it is possible (hmmm but to acquire access token again your clients have to login your webapp again every 60 days, there must be a better solution)
I am also working on similar problem
I have a prototype device for jogging wrist band and I am trying to post a wall story about number of steps in current day and the tempo on behalf of a user by just clicking on a button on the machine when it is connected to wlan or android phone in a wireless fashion.
I'm in the process of developing an FB app, which needs to be able to run in the usual desktop FB site (with surrounding FB livery), on mobile device browsers (I'm using HTML5 and Bootstrap to adapt the layout according to device), and within native mobile Facebook apps on iOS and Android.
In particular this last scenario - I'm trying to develop on my MBP and I'm using a local domain name (set in hosts) that points to my web server box next to me. In order to make that work from the iOS device, I have Charles running as a proxy on my MBP and have updated the iPhone wifi proxy settings so that all iPhone http requests are channeled through Charles, and therefore the iPhone can also use the localised domain name.
When testing through the mobile FB website, if i navigate to the test app I've created the FB mobile website launches the canvas in a new safari tab, and it works fine.
However, within the iOS native FB app, when I navigate to the app I receive a
"Sorry, something went wrong"
message in place of where the canvas content should be (see image linked below).
iPhone screengrab
Since FB forces https canvas URLs now I'm using the built-in self-certified certificate of my web server so that https can be served up. In the safari browser I initially get an untrusted certificate warning, which I accept and then I have no problems using my html.
Has anyone else seen this problem and know how to get around it? I'm assuming the FB app is having problems with the untrusted certs, but since the native app is calling a locally served (via proxy) URL, I dont see why there should be a problem (could the FB app be set to not accept untrusted certs?).
I really need to test my code within the iOS app otherwise I wont be able to prove to the client that FB works with my code.
Cheers
Lee
(p.s. I tried using 3G instead of the local wifi proxy in case something there was causing the problem, but it still didnt work in the native iOS FB app)
Turns out the problem was due to the mobile URL I had specified in the app settings was set to use https. Presumably this is because the native app won't accept untrusted SSL certificates (which is also probably why it was fine in the browser, because one can accept untrusted certificates).
Changing the protocol to http fixed the issue. Strangely Facebook doesn't insist on the use of https for mobile app URLs, so using http was not a problem.