![]() | user_timeline NSURL |
|
14 Dec 2011, 20:32
Jim Schultz (25 posts) |
just a heads up, if you use https as the book shows in section 3.3 of the reloadTweets method you’ll get an authentication error response. the book shows NSURL *url = [NSURL URLWithString:@”https://api.twitter.com/1/statuses/user_timelin…]; change it to: NSURL *url = [NSURL URLWithString:@”http://api.twitter.com/1/statuses/user_timeline…]; not sure if this is an errata type issue or not but i thought somebody else could find this useful. |
|
14 Dec 2011, 20:41
Chris Adamson (277 posts) |
I didn’t experience that when writing it, but it’s possible that I authenticated my simulator doing something else and therefore didn’t get hung up on the https:. If http: works for you, that should make things simpler for everyone. Please file this as an errata. Thanks. |
|
20 Dec 2011, 11:06
Rick Evans (3 posts) |
using HTTPS works for me. I noticed a couple of things that confused me in this section. When specifying the “twitterParams”, in the book it showed:
But if I want to see my tweets, then “pragprog” must be my Twitter screen name. I found the Twitter API documentation, some of the best I have used as it is so amazingly complete (https://dev.twitter.com/docs/api) and it did not take much effort to locate the API being used in your book which I did not know if it should be referenced in your book or not: https://dev.twitter.com/docs/api/1/get/statuses… This statement is incorrect as it should be “queue” instead of thread> |
|
20 Dec 2011, 11:44
Chris Adamson (277 posts) |
Rick: yes, I think we mention earlier in the chapter that you need to use your own screen_name⦠we included “pragprog” in the sample code because that’s what we generated the screenshot from (I think on the first mention, we had “yourtwitterhandle” as a dummy value). Thanks for the point on dispatch_get_current_queue()... this has already been filed in the errata. |
| You must be logged in to comment |

