Hello All,
Quick Summary:
Titanium Version: 1.6.2
Platform: IOS 4.3, and Android 2.2
Using the Facebook Comment social plugin in a webview in conjunction with the Titanium Facebook module seems to be incompatible and requires the user to re-authenticate to us the webview. Has anyone been able to use the Facebook Titanium Module and then one of the Facebook social plugins where the user doesn't have to re-authenticate? If so how did you make it work?
The longer version: We are using The Facebook module for titanium authenticate and we know it works because we get an access token that is 258 characters in length like: jiq-0000Sgnz1s77lEwh0000AVCe123456-h7eyAyrQ.eyJpdiI6Ik5OTnFic2J4X0ZNL00000V00000V2cifQ.MqR0BkP7CczroebW76_565656txrN81IxZe000M78ioCpeQrV8GMQ8s1STPQPk25em499999qtneHN9BXys0000EnqVOHnuc0INlQodT-S90VjX0000uePQ3vPZl1HF60000n000YkUV8szhl12345678yTOtbDvh8YCrxMRi1Q
I know it works because can take this token and use it with
curl https://graph.facebook.com/99394368305?access_token=<real_above_value> which will return: "{"id":"99394368305","from":{"name":"Coca-Cola","category":, [SNIPPED…]
The problem shows up when I attempt to make use the Facebook social plugin: https://developers.facebook.com/docs/reference/plugins/comments/
The plugin checks for a session and all I have is the accessToken when I print the session I also have is: Session_key, uid, expires, secret, base_domain, access_token sig
I'm not sure how to reconcile the differences between the Facebook Titanium module and what the kind of session information the webview needs as needing the user to log in which is a deal breaker.
Your Answer
Think you can help? Login to answer this question!