Closed GoogleCodeExporter closed 8 years ago
Ouch. Chances are that's happening to all shared URLs, too. I'll take a look
this week.
Original comment by sombradesoledad
on 15 Jun 2010 at 8:54
Would it be possible to use the FB app instead of the m.facebook.com utility
for the share function? This appears to work with Twitter correctly.
Original comment by jpenn...@gmail.com
on 29 Sep 2010 at 7:08
Original comment by jpenn...@gmail.com
on 29 Sep 2010 at 7:08
In 1.3.2 this is using the "SHARE" intent chooser which lets me choose whether
to share via Bluetooth, Email, Facebook, Gmail, Messaging, Twitter,...) This
chooser is built into Android and pulls up whatever apps on the device have
registered a listener for the SHARE intent. So we have no control over how the
Facebook app decides to handle that.
Original comment by jeremy.w...@gmail.com
on 29 Sep 2010 at 7:17
I think this is a bug in the Facebook intent handling. It still seems broken.
We are using the following code:
Intent shareIntent = new Intent(android.content.Intent.ACTION_SEND);
shareIntent.putExtra(Intent.EXTRA_SUBJECT, story.getTitle());
shareIntent.putExtra(Intent.EXTRA_TEXT, String.format(
"%s: http://www.npr.org/%s", story.getTitle(), story.getId()));
shareIntent.setType("text/plain");
Facebook is redirecting to their mobile UI. It has nothing to do with us, and I
think we're using the API correctly here.
Here's a further explanation of the issue, and their workaround:
http://groups.google.com/group/android-developers/browse_thread/thread/731d7891c
116a5d5
I would prefer not to do that, since it seems brittle. Facebook should just fix
their app.
Original comment by mfreder...@google.com
on 29 Sep 2010 at 7:26
Ah ha! Well caught, friends. That seems kinda pathetic, right? Last time I
heard, Facebook had a few people working for them...
Original comment by jpenn...@gmail.com
on 29 Sep 2010 at 8:43
They've done 9 updates in the last year (since the issue was reported on
android-developers. Who knows if it's in their own discussion forum as they
don't have search options there. (I suppose I could post it in the bugs thread
or in a new one.)
I hate to add more code (that could introduce bugs) but if others complain of
this, we may want to consider the workaround provided, just so that we can
improve the customer experience.
Original comment by jeremy.w...@gmail.com
on 29 Sep 2010 at 9:07
Original issue reported on code.google.com by
jpenn...@gmail.com
on 15 Jun 2010 at 8:19