Wait…
The “Platform Policy 2.3” say that you can’t add your own text to the post, and you can’t append additional text, but what if you don’t do those?
What if you have a “Share” button, that simply… well… share an app
Is this a violation too?
See below what i mean.
Roy.
<POM>: If you’re talking about sharing via native.showPopup() on Android, Facebook allows developers to share an image or URL, including a custom image or URL you generate on the fly. Non-Corona apps support this on Android, but Corona SDK-built ones do not. This is what Rob said Engineering is looking into.
The November 2014 thread discusses this at some length:
<corona273>:
No, I’m talking about General rules about posting to Facebook, (bit off topic but it is a conversation after all)
If using the facebook* library, creating a button that simply share the app with no additional text , like the image in green above, is this a violation?
Roy.
Corona engineering seems/appears to have taken the stance that if you’re prohibited from auto-filling text (by policy), then they won’t support the share intent at all (by technology). There’s some sort of disconnect here.
Dave: I think that’s the best description of Corona’s policy that I’ve read so far.
Because Facebook prohibits auto-filled out text (by policy), Corona has chosen (by technology) to disable even the allowed sharing of URLs and images. I actually suspect there’s some Android code saying IF SHARING_INTENT_TARGET == “FACEBOOK” THEN ABORT that needs to be commented out to restore the defaults.
But I’m confused about one point. You said that “FB does indeed support Androids internal share intent, and from Corona (and it does work – i’ve done it myself).”
I just tried to share a URL (no text) and a URL and image (no text) with native.showPopup() on Android L on a Nexus 5 with the Facebook app installed and a user account logged in. Facebook is available as a sharing target from other apps. But it does not show up as one in a Corona-built app.
Can you share what you did to make this work?
Full details are here “somewhere” here on the forum (i’ve lost track), but in short:
“pretend” that you’re going to do an email share, and set up the options accordingly (my use was just to share a captured image, so didn’t care that i couldn’t prefill text for subject or body),
now, and this is the key, and is the kludgy/hokey part that prevents it from being usable in real-world applications, but does prove the concept/theory: go into your settings-apps, find whatever app you currently have associated with the email share intent (it’s probably gmail :D), and clear out that association.
now when you attempt to share an email you’ll get the “just once/always” chooser.
so fire up your app, try to share an email, then choose facebook, just once.
and done (assuming you have the facebook app installed, of course), your pic was just posted.
now try it again, but choose twitter (assuming you have twitter app installed) just once. and done, photo posted.
now try it again, but choose g+ just once, and done, photo posted.
now try it again, but choose ANY OTHER app you happen to have that has some reasonable chance of knowing what to do with an image file, and it probably “just works” too.
when done experimenting, select your original email client and “always” to put things back the way they were.
the point is: if Corona allowed you to FORCE the creation of a chooser (so as to override any pre-existing association, and is literally a one-line addition if you’ve already got all the other code in place) you could issue a “generic” share intent and do “simple sharing” on android+facebook today.