Talk:Mobile

From Facebook Developer Wiki

Jump to: navigation, search

Contents

[edit] Extended Permissions

There is currently no way to let a user grant your application extended permissions with mobile browser-friendly pages.

There is a bug submitted in the Bug Tracker (http://bugs.developers.facebook.com/show_bug.cgi?id=1877) but it has not been queued. Need to be able to grant extended permissions with something like http://m.facebook.com/authorize.php?api_key=YOUR_API_KEY&v=1.0&ext_perm=PERMISSION_NAME.

This problem has been addressed in the Facebook Connect for iPhone apps only. It still requires fixing for dotmobi/WAP sites.

Ronan [User:625328551]

[edit] SMS limits

Am I interpreting this correctly? "Applications will be limited to a global limit that equals the sum of 1 MT (Mobile Terminated, or a message sent to a mobile phone) per user that has opted to receive SMS from the app each day." If my app has 1000 users who have opted to receive SMS from it, my app can send 1000 SMS per day and could choose for all of them to go to the same user? I know this would be further limited by the user limit. Martin Lockett

It's technically true. This is to give you some flexibility with how you message your users. There's a corollary here with how the email extended permission works -- since a user explicitly has to give permission to your application before you can send the user a text message, we leave it to your best judgment to whom to send messages, and how often (once a user gives your application the email extended permission, you can send the user as much email as you want). Hope this helps. -- Pete (563683308 15:14, 17 March 2009 (PDT))

[edit] T-mobile

Ok, it's been almost a year and still no integration with T-Mobile USA... what gives? There is *nothing* technical preventing you from enabling FB Mobile for the 4th largest US carrier, so why isn't it being done?

--500347728 17:59, 24 October 2007 (PDT) - MMS, anyone? - Global SMS/MMS aggregators are not hard to come by, Facebook should be able to cover most carriers worldwide without much effort.

[edit] Error 270

I have a test application that I'm using to try to experiment with the SMS API, but every time I try to send one to myself I get a code 270 error ("Permissions disallow sms to user"). I have the box checked in the app config to enable the SMS API, and I have gone to the extended-permissions page to allow the app to send SMS messages to the account I am testing with, but I still always get this error. There are some other people who are experiencing the same issue as well.

Adam: You should verify you got the names of the variables right as the documentation for sms.canSend was initially wrong (it used "user_id" instead of "uid"). If you didn't send a "uid" field at all, you got back a 270 as sending "invalid user" was considered "permission denied" ;P. Now, the documentation for sms.send was correct, so maybe this isn't your problem, but it was mine (I happened to only paid half attention as I typed in the names for sms.send and used "user_id" there as well). -- Jay Freeman (saurik)

Here are some references on this issue:

[edit] Mobile Uploads

I've not yet seen a way for developers to utilize the mobile uploads functionality within their applications. For instance, I'm building a scavenger hunt application that allows a user to create a scavenger hunt and for his/her friends to send picture messages via their phone for each item they find on the hunt. It's become difficult as I've come to realize the need for me to handle the photos myself rather than use facebook's systems. This means needing to use a separate email address like [hunt_id]@one_of_my_domains.com to catch the photos rather than using something easy to remember like facebooks mobile@facebook.com or scavengerhunt@facebook.com

Have I just missed this functionality? If not, I feel it would be an awesome addition to the facebook API :)

[edit] Facebook Mobile Severely Limited

There are several things that severely limit the usefulness of Facebook Mobile:

1. When canvas pages are wrapped in the fb:mobile tags, feed story forms are IGNORED. Thus it is impossible to publish anything using a mobile web browser.

2. The Feed.publishUserAction function, which COULD be used nicely with SMS functionality to publish stories, is worthless because it ignores the target ID's. So nothing can be published to a friend's feed. It also forces only one-line stories to be published to the user's wall, thus essentially removing any rich content like images, music, etc.

3. When a user adds a mobile-enabled application to their profile, it doesn't show on the mobile version of their profile. If two or more mobile-enabled applications are added, it will list them and provide a link to "all boxes". However, no one is going to think to add a second mobile app when the first one doesn't work at all (no link on mobile version of profile).

[edit] Facebook Links on Canvas Pages

When wrapping the entire content with <fb:mobile> in order to create a canvas visually consistent with m.facebook.com, although visually consistent with m.facebook.com, all facebook links (such as: inbox, home, etc.) are relative and will therefore link to http://apps.facebook.com/inbox.php and http://apps.facebook.com/home.php instead of http://m.facebook.com/inbox.php and http://m.facebook.com/home.php respectively.

Retrieved from "http://wiki.developers.facebook.com/index.php/Talk:Mobile"
reference