[ALOY-1289] Alloy social.js plug-in incompatible with newest Twitter APIs
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | None |
|---|
| Status | Open |
|---|
| Resolution | Unresolved |
|---|
| Affected Version/s | n/a |
|---|
| Fix Version/s | n/a |
|---|
| Components | Builtins |
|---|
| Labels | builtins |
|---|
| Reporter | Tim Poulsen |
|---|
| Assignee | Ingo Muschenetz |
|---|
| Created | 2015-06-29T13:24:25.000+0000 |
|---|
| Updated | 2019-03-19T15:49:43.000+0000 |
|---|
Description
Authenticating an app via the Alloy social.js built-in no longer works. Twitter returns a long number, which they direct you to enter into the app. The built-in has no support for this, thus the app cannot be authenticated and you can't send tweets.
Attachments
It appears that the social.js built-in is set up to handle Twitter's PIN-based authentication (https://dev.twitter.com/oauth/pin-based) with the code at https://github.com/appcelerator/alloy/blob/master/Alloy/builtins/social.js#L519. However, it's no longer automatically handling that PIN. Until recently, my app worked just fine using social.js. I have not changed my handling or usage of the library, yet now users are being prompted with the PIN. Perhaps Twitter's response payload has changed. The docs give no guidance on how to manually handle this PIN and there are no sample apps that use it. Maybe this is simply a documentation issue?