[twitter-dev] Re: Network Error: 204 ("Response error: "Failed to validate oauth signature and token")

[pga]

Hi Taylor,

Thank you for your input. Here are details:

1. Additional sources:
void OAuthTwitter::authorizeXAuth(const QString &username, const
QString &password)
{
Q_ASSERT(m_netManager != 0);

QUrl url(TWITTER_ACCESS_TOKEN_XAUTH_URL);
url.addQueryItem("x_auth_username", username);
url.addQueryItem("x_auth_password", password);
url.addQueryItem("x_auth_mode", "client_auth");

QByteArray oauthHeader = generateAuthorizationHeader(url,
OAuth::POST);

QNetworkRequest req(url);
req.setRawHeader(AUTH_HEADER, oauthHeader);

QNetworkReply *reply = m_netManager->post(req, QByteArray());
connect(reply, SIGNAL(finished()), this,
SLOT(finishedAuthorization()));
}

2. HTTP request:
POST

3. Url (content of 'url' object):
https://api.twitter.com/oauth/access_token?x_auth_username=myn...@o2.pl&x_auth_password=mypassword&x_auth_mode=client_auth

4. Authorization header (content of 'oauthHeader' object):
OAuth oauth_consumer_key="myconsumerkey",oauth_signature_method="HMAC-
SHA1",oauth_signature="kqb27IFO2BM3iEO4fhfYK%2BbTc3Y
%3D",oauth_timestamp="1304491190",oauth_nonce="3uLG1a72zvcGdyJr",oauth_version="1.0"

5. Body:
none (empty)

6. Additional observations:
When I type username instead of e-mail (currently I use e-mail and
password to login to Twitter) then xAuth pass successfully but only on
the simulator and only first time... Reproducibility 100%.

Best Regarrds,
Pawel

On 2 Maj, 16:56, Taylor Singletary 
wrote:
> Hi Pawel,
>
> OAuth problems tend to require digging a bit deeper than surface error
> messages to debug -- to help you in this case, we would need to know at
> minimum: the HTTP Authorization header used in your request, the format of
> the POST body you are sending (but not the actual usernames and passwords),
> and the exact URL you are accessing -- all details that the library you are
> using likely make difficult, but not impossible, to ascertain. The signature
> base string is also extremely useful for debugging, but also requires you to
> filter out details of usernames and passwords.
>
> In most cases a problem like this is due to a parameter encoding error or by
> a request with POST bodies and signature base strings not in agreement.
>
> @episod  - Taylor Singletary
>
> On Sun, May 1, 2011 at 11:11 PM, pga  wrote:
> > Hi all,
>
> > I develop an application for Symbian platform in Qt. I have
> > encountered a problem when trying to pass xAuth using QTweetLib
> > library. I have both consumer key and secret. I just got conformation
> > from Twitter API Policy guys that I should be able to pass xAuth using
> > these credentials (I have permission) but I'm not.
>
> > Here is the snippet of code:
> > m_oauthTwitter = new OAuthTwitter(a_netManager, this);
> > connect(m_oauthTwitter, SIGNAL(authorizeXAuthFinished()),
> > SLOT(xauthFinished()));
> > connect(m_oauthTwitter, SIGNAL(authorizeXAuthError()),
> > SLOT(xauthError()));
> > …
> > m_oauthTwitter->authorizeXAuth(username, password);  //  username and
> > password are OK
>
> > I got following error (from application's output console – Qt Creator
> > IDE):
> > OAuth tokens are empty!
> > Network Error:  204
> > Response error:  "Failed to validate oauth signature and token"
>
> > The error occurs on both real device (Nokia N8) and simulator (Windows
> > XP). Date/Time seem to be set correctly.
>
> > Could you advice me what should I try to solve the problem?
>
> > Best Regards,
> > Pawel
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk
>
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: OAuth Authorization screen on Windows Phone 7 (WebBrowser control)

[Matthieu GD]

On May 3, 9:35 pm, Ben Ward  wrote:
> Hi Chris, Matthieu and any others running into this issue:
>
> On May 3, 2011, at 5:00 PM, LoungeFlyZ wrote:
>
> > Something has changed in the last few days and now the page is
> > rendering a little "better" but scrolling/panning/zooming isnt working
> > & i cant enter text in the username or password fields.
>
> > Is there anything i can do to help diagnose this issue?
>
> The update we put out this morning fixes the general rendering of the OAuth 
> screen in WP7 (there's a couple more minor layout improvement tweaks coming 
> as well, but the blocking problem is rectified.) It now works perfectly in 
> Mobile IE on the phone, but for reasons which are inexplicable, loading the 
> exact same page within a phone:WebBrowser control in an application suffers 
> from cropped rendering and the no-scrolling behaviour described here.
>
> Having spent a few hours in Visual Studio, and reproduced it, it appears you 
> can work around the issue by setting IsScriptEnabled="False" on the control.
>
> I'll continue to investigate what's causing the render bug, but the above fix 
> should hopefully set everybody running again.
>
> Thanks for your patience, and to Chris and Matthieu for corresponding with me 
> on Twitter whilst debugging the issue.

Thanks Ben, I can confirm it works with IsScriptEnabled="False".

I re-enable it on my control after the rendering of the auth page
because my callback page is using a script to pass the token, but like
Ben mentionned on Twitter I could have also parsed the e.Source
parameter on the navigated event.

Matthieu

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] OAuth Authorization screen on Windows Phone 7 (WebBrowser control)

[Ben Ward]

Hi Chris, Matthieu and any others running into this issue:

On May 3, 2011, at 5:00 PM, LoungeFlyZ wrote:

> Something has changed in the last few days and now the page is
> rendering a little "better" but scrolling/panning/zooming isnt working
> & i cant enter text in the username or password fields.
> 
> Is there anything i can do to help diagnose this issue?

The update we put out this morning fixes the general rendering of the OAuth 
screen in WP7 (there's a couple more minor layout improvement tweaks coming as 
well, but the blocking problem is rectified.) It now works perfectly in Mobile 
IE on the phone, but for reasons which are inexplicable, loading the exact same 
page within a phone:WebBrowser control in an application suffers from cropped 
rendering and the no-scrolling behaviour described here.

Having spent a few hours in Visual Studio, and reproduced it, it appears you 
can work around the issue by setting IsScriptEnabled="False" on the control.

I'll continue to investigate what's causing the render bug, but the above fix 
should hopefully set everybody running again.

Thanks for your patience, and to Chris and Matthieu for corresponding with me 
on Twitter whilst debugging the issue.

Ben

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] access token expires ?

[Joshua Nguyen]

I have obtained the access token; then i check for new @mentions twice
a minute. In ~9 hours, Twitter returns an error : Timestamps out of
bounds.

I see this error is relating to the time difference between Twitter
and my system; but i changed nothing in my system time.

Does access token expire ? How can I solve this problem ?

Thanks

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control

[Matthieu GD]

On May 3, 8:00 pm, LoungeFlyZ  wrote:
> Hi Ben,
>
> Thanks for your reply about this issue.  I am also seeing this in my
> Windows Phone 7 application.
>
> Something has changed in the last few days and now the page is
> rendering a little "better" but scrolling/panning/zooming isnt working
> & i cant enter text in the username or password fields.
>
> Is there anything i can do to help diagnose this issue?
>
> Thanks,
>
> Chris.


I have the same issue, I emailed to Ben a screenshot of the problem on
my applicaion,

Matthieu

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Connecting and posting a tweet..

[Talasan]

I'm pretty lost! :)

I've gone through the documents and I've once successfully posted a
tweet. No idea how that happened, however. I'm attempting to do a one-
page validation for this so that I can keep it relatively simple
without redirects.

How can I accomplish this, however? Here is my code, and I'd greatly
appreciate somebody to point out the fallacies. Thank you.


if(!@$_GET['oauth_token']) {
$connection = new TwitterOAuth($db['twc_api'], 
$db['twc_secret']);
$temp = $connection->getRequestToken($OAUTH_CALLBACK);
$twit_url = $connection->getAuthorizeURL($temp);
$_SESSION['oauth_request_token'] = $token = 
$temp['oauth_token'];
$_SESSION['oauth_request_token_secret'] =
$temp['oauth_token_secret'];
} else {
if(!isset($_SESSION['oauth_access_token']) ||
$_SESSION['oauth_access_token'] == '') {
$connection = new TwitterOAuth($db['twc_api'], 
$db['twc_secret'],
$_SESSION['oauth_request_token'],
$_SESSION['oauth_request_token_secret']);
$temp = $connection->getRequestToken();
$_SESSION['oauth_access_token'] = $token = 
$temp['oauth_token'];
$_SESSION['oauth_access_token_secret'] =
$temp['oauth_token_secret'];
}
}

if(isset($_POST['submit_tweet'])) { # Handle tweet submissions
$connection = new TwitterOAuth($db['twc_api'], 
$db['twc_secret'],
$_SESSION['oauth_access_token'],
$_SESSION['oauth_access_token_secret']);
$content = $connection->get('account/verify_credentials');
$msg = $_REQUEST['tweet'];
$update_status = $connection->post('statuses/update', array(
'status' => $msg.' '.bitly($money_url, 
$db['bitly_login'],
$db['bitly_api'])
));
$tweeted = true;
print_r($update_status);
if($update_status->error) echo 'An error occurred';
else Header('location: '.$reward_url);
}

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control

[LoungeFlyZ]

Hi Ben,

Thanks for your reply about this issue.  I am also seeing this in my
Windows Phone 7 application.

Something has changed in the last few days and now the page is
rendering a little "better" but scrolling/panning/zooming isnt working
& i cant enter text in the username or password fields.

Is there anything i can do to help diagnose this issue?

Thanks,

Chris.

On Apr 30, 4:18 pm, Ben Ward  wrote:
> Hi Bob, Tom, and others,
>
> On Apr 29, 2011, at 11:50 PM, Bob12345 wrote:
>
> > I've been using a WebBrowser control in my Window Phone application to
> >logininto Twitter. Today I noticed that thelogin/authorizationpage
> > format had changed and it is now unusable in a web browser control
> > that my application displays. The text on thepageis squeezed
> > together, and thepageunscrollable.
>
> I've seen a couple of reports of this concerning rendering in the current 
> browser on Windows Phone 7. This is obviously unintended and I'm working on a 
> fix.
>
> On Apr 30, 2011, at 9:09 AM, Tom van der Woerdt wrote:
>
> > It sounds like all UIWebView, WebBrowser and probably Android's WebView are 
> > blocked. This is definitely a *good* thing for security reasons.
>
> > The "workaround" I recommend: launch the actual browser, using a 
> > :// link (something like myapplication://tokenDone) as the return 
> > URL. This is a LOT safer for the users.
>
> Although I'm personally a strong advocate of the protocol redirects, I can 
> assure you that we have not actively blocked access to the OAuth screens in 
> any context or browser with these updates.
>
> If you're having trouble with the auth screen in a web view, I'm going to 
> need more information from you because there's no debugging tool for a 
> UIWebView in third party apps. If you can trap any rendering or script errors 
> from a browser view control in your development environment, please send them 
> to me and I'll use them to look for any problems. Email me directly if you 
> prefer.
>
> Thanks,
>
> Ben
> / @benward
> / Twitter platform developer

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control

[LoungeFlyZ]

Thanks a lot Ben,

I am also seeing this behavior on Windows Phone 7.   How can i help
you with this?

Something changed again recently (i.e. last couple of days).  Now i
see the page rendering "better", but scrolling/panning/zooming dont
work & i cant enter anything into the username/password textboxes.

If needed i can provide a screenshot of what i am seeing.

Any help/guidance you can provide would be much appreciated.  Right
now my users cant login to Twitter :(

Thanks,

-Chris.





On Apr 30, 4:18 pm, Ben Ward  wrote:
> Hi Bob, Tom, and others,
>
> On Apr 29, 2011, at 11:50 PM, Bob12345 wrote:
>
> > I've been using a WebBrowser control in my Window Phone application to
> >logininto Twitter. Today I noticed that thelogin/authorizationpage
> > format had changed and it is now unusable in a web browser control
> > that my application displays. The text on thepageis squeezed
> > together, and thepageunscrollable.
>
> I've seen a couple of reports of this concerning rendering in the current 
> browser on Windows Phone 7. This is obviously unintended and I'm working on a 
> fix.
>
> On Apr 30, 2011, at 9:09 AM, Tom van der Woerdt wrote:
>
> > It sounds like all UIWebView, WebBrowser and probably Android's WebView are 
> > blocked. This is definitely a *good* thing for security reasons.
>
> > The "workaround" I recommend: launch the actual browser, using a 
> > :// link (something like myapplication://tokenDone) as the return 
> > URL. This is a LOT safer for the users.
>
> Although I'm personally a strong advocate of the protocol redirects, I can 
> assure you that we have not actively blocked access to the OAuth screens in 
> any context or browser with these updates.
>
> If you're having trouble with the auth screen in a web view, I'm going to 
> need more information from you because there's no debugging tool for a 
> UIWebView in third party apps. If you can trap any rendering or script errors 
> from a browser view control in your development environment, please send them 
> to me and I'll use them to look for any problems. Email me directly if you 
> prefer.
>
> Thanks,
>
> Ben
> / @benward
> / Twitter platform developer

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Can I specify my own URL for the Tweet button?

[Arnaud Meunier]

Hey David,

The Tweet Button will share your URL as a t.co link that redirects to the
URL you provide (in your case: t.co --> bit.ly --> final destination). If
you're using the count box, think also to set the "counturl" parameter to
the final destination. Cf exemple here:
http://dev.twitter.com/pages/tweet_button#using-shorturl

Arnaud / @rno 



On Tue, May 3, 2011 at 3:48 PM, David Harkness  wrote:

> Greetings all,
>
> Our site currently has a Tweet button for news articles and reviews
> with correctly styling and retweet count. We are using Bitly to
> shorten the URLs on the backend, but this has caused us to hit the
> rate limit.
>
> To solve this I created a controller to do the shortening when the
> user clicks the Tweet button and redirect to Twitter's share URL, and
> I changed the Tweet button to point to this controller instead of
> twitter.com. However, the Twitter JavaScript is overwriting my URL. Is
> there any way to tell the JS API to leave the URL alone so we can call
> our own URL?
>
> Alternatively, are there any analytics available with Twitter's URL
> shortener that we can access? The only reason we need Bitly is for
> real-time analytics, and if t.co URLs can provide us the same features
> we'd be more than happy to use them.
>
> Thanks,
> David
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Can I specify my own URL for the Tweet button?

[David Harkness]

Greetings all,

Our site currently has a Tweet button for news articles and reviews
with correctly styling and retweet count. We are using Bitly to
shorten the URLs on the backend, but this has caused us to hit the
rate limit.

To solve this I created a controller to do the shortening when the
user clicks the Tweet button and redirect to Twitter's share URL, and
I changed the Tweet button to point to this controller instead of
twitter.com. However, the Twitter JavaScript is overwriting my URL. Is
there any way to tell the JS API to leave the URL alone so we can call
our own URL?

Alternatively, are there any analytics available with Twitter's URL
shortener that we can access? The only reason we need Bitly is for
real-time analytics, and if t.co URLs can provide us the same features
we'd be more than happy to use them.

Thanks,
David

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] is there video or audio link inside

[Taylor Singletary]

Hi John,

There's currently no sure-fire way to determine if a link in a Tweet leads
to renderable content or the disposition of that content as a picture or a
video.

However, by using Tweet Entities (
http://dev.twitter.com/pages/tweet_entities ) you can get expanded
information about many of the URLs presented in Tweets -- for some URLs like
t.co-based URLs, they'll also be unshortened. Most API functions that return
Tweet data respond to an additional query parameter, include_entities=true
which expands the resource response to include the additional data nodes.

A great additional thing you can do is keep up to date with the services
that embed.ly supports ( by using their API every so often to update your
list of their supported services: http://api.embed.ly/docs/service ) and
leverage embed.ly to render rich content when its origin is identifiable by
the tweet entities.

@episod  - Taylor Singletary


On Tue, May 3, 2011 at 7:17 AM, John Carver wrote:

> Hi people.
>
> i wonder is there a way to determine if video or audio link inside
> statuse body? especially when short ls provided? i mean is there a n
> indication about?
>
> Any replies and thoughts would be appreciated.
>
> Thanks.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] is there video or audio link inside

[John Carver]

Hi people.

i wonder is there a way to determine if video or audio link inside
statuse body? especially when short ls provided? i mean is there a n
indication about?

Any replies and thoughts would be appreciated.

Thanks.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] java

[Vladimir Dvornik]

im too

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Delete and Mark favorite method is not working

[monika tapadiya]

Hello ,,,
I am using MG Twitter Engine API. Delete update method is not working
I used
[_engine deleteUpdate:[tweet updateId]];

Please Tell me what should I pass in [_engine deleteUpdate: ? ??/?]

And same problem with [_engine markUpdate:[tweet updateId]
asFavorite:YES];

Thanks In  Advance

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] issue with authorization URL

[Felipe Peña Riveros]

Hi everyone.

I've developed an application which links LAMS (http://
www.lamsinternational.com/) and Twitter.

Up to last week, everything was working OK. Now, when I'm trying to
reach authorization URL, the browser throws the follow error:

provide is not defined
[Detener en este error] (function(){var A=(function(){var
B=(t...lse})});provide(">tfw_bundle_evaled");

Any thoughts on this?

Thanks in advance.

Felipe

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: New oAuth Authenticate Page

[Varun Airon]

Hi Guys,

I am using Twitter OAuth authentication on Android and it shows a new popup
window.

Guys I am facing one Issue using Twitter OAuth authentication. Once logged
in, I am not able to log out from my twitter account. I am using Signpost
api. I am using oauth/authorize still not able to enter my another
credentials.

Is there any way to get logout from Twitter ??

Any Help would be appreciated.

Thanks,


On Tue, May 3, 2011 at 2:22 PM, Tom van der Woerdt  wrote:

> I don't know whether it's the only working solution, but it is the only
> proper OAuth procedure and as far as I'm aware, also the recommended one.
>
> Tom
>
>
> On 5/3/11 4:50 AM, Bess wrote:
>
>> I'd like to confirm the all the developers here on this mailing list.
>> Does the new OAuth redesign page prevent you from using OAuth in a new
>> popup window?
>>
>> This OAuth hack is officially not going to work going forward?
>>
>> Hi Tom van der Woerdt,
>>
>> Your recommend using the workaround launching OAuth in a safari
>> browser outside the app? Your suggested approach will require user to
>> quit and exit app and authenticate with OAuth using device mobile
>> browser. Then ask user to go back to the app again. Is this the only
>> working solution?
>>
>> On Apr 30, 9:09 am, Tom van der Woerdt  wrote:
>>
>>> I've heard this before.
>>>
>>> It sounds like all UIWebView, WebBrowser and probably Android's WebView
>>> are blocked. This is definitely a *good* thing for security reasons.
>>>
>>> The "workaround" I recommend: launch the actual browser, using a
>>> :// link (something like myapplication://tokenDone) as the
>>> return URL. This is a LOT safer for the users.
>>>
>>> Tom
>>>
>>> On 4/30/11 8:55 AM, Bob12345 wrote:
>>>
>>>  I'm having this problem too. My login browser inside the phone app is
 now rendered useless, it doesn't even scroll.
 On Apr 28, 1:41 pm, Shannon Whitley
  wrote:

> I was surprised to see a newly formatted oAuth Authenticate Page.  The
> new page doesn't account for the scores of oAuth implementations that
> popup a new window.
> There is an ad-hoc standard for the window height and width that makes
> for a decent user experience.  The new format will cause issues for
> the user since it results in page scrolling.
> Can we discuss this new page format and determine if it can be changed
> or if we can have alternate formats?
>

> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: New oAuth Authenticate Page

[Rich]

I can confirm on the iPhone, embedding the oAuth page in a UIWebView
inside your app is still working for me on live devices, and I hope it
remains that way too!

On May 3, 3:50 am, Bess  wrote:
> I'd like to confirm the all the developers here on this mailing list.
> Does the new OAuth redesign page prevent you from using OAuth in a new
> popup window?
>
> This OAuth hack is officially not going to work going forward?
>
> Hi Tom van der Woerdt,
>
> Your recommend using the workaround launching OAuth in a safari
> browser outside the app? Your suggested approach will require user to
> quit and exit app and authenticate with OAuth using device mobile
> browser. Then ask user to go back to the app again. Is this the only
> working solution?
>
> On Apr 30, 9:09 am, Tom van der Woerdt  wrote:
>
>
>
>
>
>
>
> > I've heard this before.
>
> > It sounds like all UIWebView, WebBrowser and probably Android's WebView
> > are blocked. This is definitely a *good* thing for security reasons.
>
> > The "workaround" I recommend: launch the actual browser, using a
> > :// link (something like myapplication://tokenDone) as the
> > return URL. This is a LOT safer for the users.
>
> > Tom
>
> > On 4/30/11 8:55 AM, Bob12345 wrote:
>
> > > I'm having this problem too. My login browser inside the phone app is
> > > now rendered useless, it doesn't even scroll.
>
> > > On Apr 28, 1:41 pm, Shannon Whitley  wrote:
> > >> I was surprised to see a newly formatted oAuth Authenticate Page.  The
> > >> new page doesn't account for the scores of oAuth implementations that
> > >> popup a new window.
>
> > >> There is an ad-hoc standard for the window height and width that makes
> > >> for a decent user experience.  The new format will cause issues for
> > >> the user since it results in page scrolling.
>
> > >> Can we discuss this new page format and determine if it can be changed
> > >> or if we can have alternate formats?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: New oAuth Authenticate Page

[Tom van der Woerdt]

I don't know whether it's the only working solution, but it is the only 
proper OAuth procedure and as far as I'm aware, also the recommended one.


Tom


On 5/3/11 4:50 AM, Bess wrote:

I'd like to confirm the all the developers here on this mailing list.
Does the new OAuth redesign page prevent you from using OAuth in a new
popup window?

This OAuth hack is officially not going to work going forward?

Hi Tom van der Woerdt,

Your recommend using the workaround launching OAuth in a safari
browser outside the app? Your suggested approach will require user to
quit and exit app and authenticate with OAuth using device mobile
browser. Then ask user to go back to the app again. Is this the only
working solution?

On Apr 30, 9:09 am, Tom van der Woerdt  wrote:

I've heard this before.

It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.

The "workaround" I recommend: launch the actual browser, using a
:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.

Tom

On 4/30/11 8:55 AM, Bob12345 wrote:


I'm having this problem too. My login browser inside the phone app is
now rendered useless, it doesn't even scroll.
On Apr 28, 1:41 pm, Shannon Whitleywrote:

I was surprised to see a newly formatted oAuth Authenticate Page.  The
new page doesn't account for the scores of oAuth implementations that
popup a new window.
There is an ad-hoc standard for the window height and width that makes
for a decent user experience.  The new format will cause issues for
the user since it results in page scrolling.
Can we discuss this new page format and determine if it can be changed
or if we can have alternate formats?


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: Follow action doesn't work

[Matt Wang]

I have double checked my Authentication credentials, it has been authenticated, 
besides, I can tweet and retweet messages via my app by using xAuth.


On 3 May 2011, at 03:44, Bess wrote:

> http://apiwiki.twitter.com/w/page/22554652/HTTP-Response-Codes-and-Errors
> 401 Unauthorized: Authentication credentials were missing or
> incorrect.
> 
> Possible that your xAuth has been rejected?
> 
> On Apr 28, 1:36 am, Matt Wang  wrote:
>> Dear Sir or Madam,
>> 
>> I am programming for Number 10 iphone application.Currently,this
>> application has xAuth access and can post information via twitter.
>> 
>> However, when I try to call [twitterEngine
>> enableUpdatesFor:@"follower"] for adding a follower. it will return a
>> 401 error.
>> 
>> here is my code:
>> 
>> - (void)accessTokenReceived:(OAToken *)token forRequest:(NSString
>> *)connectionIdentifier {
>> 
>> [self.twitterEngine setAccessToken:token];
>> 
>> }
>> 
>> - (void)requestSucceeded:(NSString *)requestIdentifier{
>> 
>> switch (stage) {
>> case postLogin:
>> 
>> stage = loginCorrect;
>> break;
>> case loginCorrect:
>> 
>> if (twitterAction == follow) {
>> NSString *follower = [NSString 
>> stringWithFormat:@"Number10gov"];
>> NSLog(@"Try to Follow %@",follower);
>> NSLog(@"enableUpdatesFor: 
>> connectionIdentifier = %@",
>> [twitterEngine enableUpdatesFor:follower]);
>> 
>> } else if (twitterAction == retweet || twitterAction 
>> == tweet) {
>> ...
>> //
>> 
>> post and retweet work well. but follow action didn't work. could you
>> help me to point out what is the problem?
>> 
>> if you can give me a example code to show how to do follow action in
>> xAuth, that would be great.
>> 
>> Many Thanks for your help.
>> 
>> I am looking forward to your reply.
>> 
>> Many thanks.
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Twitter4j / showStatus method

[LucMartinPro]

Hi Arnaud

Currently we are using Twitter4j with the following parameters:

•   lang is omitted, nl or en
•   query has several values
•   since is the day of the last retrieval
•   rpp is 100

We loop through the results, getting up to 15 page (of 100rpp each so
up to 1500 results), starting at page 1. If we find a tweet that is
older than the actual previous retrieval date we stop. If we find a
page returns less than 100 results we stop.

We can replace the since with since_id which will limited the number
of results slightly, but we will still need the same number of pages
(up to 15).

I agree we could use the streaming API then backfill missing data if
required, but we still miss the language constraints available from
the search API.

Thanks again for your help.

Luc

On May 2, 6:01 pm, Arnaud Meunier  wrote:
> Hey Luc,
>
> 1) You should not, indeed. But this tweet was probably posted before its
> Author turned protected. In that case, it can take some time to reflect on
> search results.
>
> 2) That unfortunately doesn't help me to reproduce your issue. What is the
> exact request you've been making? When? Full HTTP request/response would
> help. Concerning tweet IDs, they are not sequential but they are always
> increasing (on a 1 second interval). So you could use the since_id parameter
> with the last tweet ID you received.
>
> 3) If for some reason you lost connection with the Streaming API, you could
> still backfill with the same process you're using today :)
>
> Arnaud / @rno 
>
> On Mon, May 2, 2011 at 3:35 AM, LucMartinPro
> wrote:
>
>
>
>
>
>
>
> > Hi Arnaud
>
> > Thank you for your fast reply! I have some more infor for you;
>
> > 1)      If the tweet is protected why does it show up in the tweet list? Is
> > there a way to filter these out? Because if they’re not public and we
> > cannot read / retrieve it, why are we even notified it exists?
>
> > 2)      We started polling every 15 minutes, but these problems started
> > occurring when we started polling every 5 minutes. We do not use a
> > “since_id” contraint, just the date-limited “since” constraint”.
> > That’s because, as far as we understand, the tweet IDs are not
> > incremental so using the “since_id” could cause tweets to be missed.
> > By using “since”, using the last retrieval date, then looping through
> > the results until we find an older result, should give us all new
> > tweets.
>
> > We currently do not use the streaming API because we can’t miss any
> > tweets. If our retrieval application goes down for 15 minutes for
> > maintenance, we won’t get any notifications. By using a date-limited
> > query (why isn’t there a date/time limited query?) through the search
> > API we can get everything since our last retrieval run, as long as the
> > number of tweets does not exceed 1500 (Twitter’s maximum number of
> > results for a query).”
>
> > Thanks in advance!
>
> > Luc
>
> > On Apr 29, 6:36 pm, Arnaud Meunier  wrote:
> > > Hey Luc,
>
> > > You're not getting rate limited. Let's take a closer look on these two
> > > errors:
>
> > > 1) First error: *Sorry, you are not authorized to see this status*
> > > That means the tweet you're trying to get is "protected". Only people
> > > approved by its author (following him) can read / retrieve it.
>
> > > 2) Second error: *since_id too recent, poll less frequently*
> > > Looks like the since_id tweet you provided hasn't been indexed yet. Would
> > be
> > > interesting to know the value you used and if you can reproduce this
> > error
> > > (using the same since_id value).
>
> > > On an unrelated note, what kind of search requests are you doing? Have
> > you
> > > considered the statuses/filter method of the Streaming API? That could be
> > a
> > > much more efficient way for you :)
>
> > > - More info on:
> >http://dev.twitter.com/pages/streaming_api_methods#statuses-filter
> > > - Twitter4j doc:
> >http://twitter4j.org/en/javadoc/twitter4j/TwitterStream.html#filter(t...)
>
> > > Arnaud / @rno 
>
> > > On Fri, Apr 29, 2011 at 6:53 AM, LucMartinPro
> > > wrote:
>
> > > > Hello
>
> > > > We are using our application CommCenter, to search twitter and get
> > > > full tweet + user data based on query results using the Twitter4j
> > > > query and showStatus methods. We need both as the query method does
> > > > not return enough information (like retweet count and follower count),
> > > > and we can't search using showStatus. Therefore, we first use query to
> > > > get "basic" results, then for each call showStatus to get the detailed
> > > > information.
>
> > > > However, we're getting 403 errors such as
>
> > > > 403:The request is understood, but it has been refused. An
> > > > accompanying error message will explain why. This code is used when
> > > > requests are being denied due to update limits (http://
> > > > support.twitter.com/forums/10711/entries/15364).
> > > > error - Sorry, you are not authorized to see th