Is anybody looking into this issue? Over a month since the first post. Still
nothing.
Amit
--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?
Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via
I've seen 2 things recently that can cause it. 1) Your user you connect
with becomes deauthed from the app, or 2) I upgraded my version of roauth
gems in ruby today, and it broke the way I was handling params and I was
getting 401s.
I expect your reason is probably something different though.
Is this a feature or a bug? It would be very handy to use it this
way ... if it was a feature ...
Ole
--
Jan Ole Suhr
s...@mobileways.de
On Twitter: http://twitter.com/janole
On Jul 15, 11:14 pm, Abraham Williams 4bra...@gmail.com wrote:
A users access_token for a single application wont
Ok, I stumbled upon what part of my valid URL was preventing my app
from getting registered. The URL had an underscore, like
http://blah_blah.woof.com.
Despite what the error message says, this is a valid URL format. How
about a message that says No underscores allowed or something?
On Jul 22,
Please, let me summarize.
On Android, working with intents and after sharing successfully, the
window closes automatically so it returns to the previous page. The
window that automatically closes should have set up a timeout because
it takes some seconds to be closed. If for example client
On Jul 27, 2011, at 3:43 AM, Victor Ruiz wrote:
On Android, working with intents and after sharing successfully, the
window closes automatically so it returns to the previous page. The
window that automatically closes should have set up a timeout because
it takes some seconds to be closed. If
Hi Amit,
We fixed the pagination issue with this bug but are still working on the
maximum results issue (separate but related). There's no current ETA I can
share, but the full 1,000 available results for the queries that yield that
much data will be reinstated.
@episod
Can you link to the specific case where the iPhone UI isn't behaving
as expected?
What about the oauth page? first make sure you're already logged in
your twitter account,copy the following link then paste it in a new
window/tab,use any browser you want;Firefox,Chrome or safari
