You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this is indeed a sample network response for us to examine via PonyDebugger, its not as helpful an example as it would be with some twitter data responses + data loaded into the tableview.
As well, it's a bit misleading -- I was expecting some twitter search results, and the error initially lead me to think I wasn't running the sample correctly, or had mysterious ponyd configuration problems.
The text was updated successfully, but these errors were encountered:
I'm pretty sure that Twitter won't have any more public endpoints, and I also don't think that it's a great idea to store tokens in the app, nor require users to add tokens just to run a test app, so we probably will have to change the test app. I'm open for suggestions.
I just display the result URL, title and content fields, and use the URL as the "id" for the CoreData integration part.
Granted, it's not as interesting as the Twitter sample would have been, but it might be a decent stop-gap solution until someone comes up with something better.
(accidentally clicked close issue earlier... oops!)
Posting a GET request to https://search.twitter.com/search.json?q=@square results in 410 GONE code due to retirement of Twitter's v1.0 API: https://dev.twitter.com/blog/api-v1-retirement-final-dates
While this is indeed a sample network response for us to examine via PonyDebugger, its not as helpful an example as it would be with some twitter data responses + data loaded into the tableview.
As well, it's a bit misleading -- I was expecting some twitter search results, and the error initially lead me to think I wasn't running the sample correctly, or had mysterious ponyd configuration problems.
The text was updated successfully, but these errors were encountered: