Open GAferguson opened 1 year ago
Ok I u installed again, but installed from Aurora store rather than F Droid and I got logged in! Thanks all
Any solutions yet? None of the possible solutions commented under this issue work for me. Tried using Twitter for Ipad API's and changing Oauth to xAuth and all the other solutions.
Any solutions yet? None of the possible solutions commented under this issue work for me. Tried using Twitter for Ipad API's and changing Oauth to xAuth and all the other solutions.
Did you clean the app cache first and then do the other steps?
Ok I u installed again, but installed from Aurora store rather than F Droid and I got logged in! Thanks all
Just for other people's reference, I didn't need to use the Aurora store version of the app to make this hack work. I just did app cache cleaning then changed to iPad API then switched to xAuth.
Any solutions yet? None of the possible solutions commented under this issue work for me. Tried using Twitter for Ipad API's and changing Oauth to xAuth and all the other solutions.
User settings, oauth, password sign in, not sign in,
For me, XAuth worked.
For me, XAuth worked.
Sometimes xauth doesn't work and sometimes oauth doesn't work, i don't know why exactly,
Any solutions yet? None of the possible solutions commented under this issue work for me. Tried using Twitter for Ipad API's and changing Oauth to xAuth and all the other solutions.
Did you clean the app cache first and then do the other steps?
Yes I did read and do the other steps as well.
Any solutions yet? None of the possible solutions commented under this issue work for me. Tried using Twitter for Ipad API's and changing Oauth to xAuth and all the other solutions.
Did you clean the app cache first and then do the other steps?
Yes I did read and do the other steps as well.
Unistall and reinstall twidere,
For me the only solution was generating my own API v2 key (i.e. elevated API access) through Twitter's developer portal - even Twitter Lists are working. And it seems to me this will be the best (maybe only) long-term solution. I think only some users will go through the "hassle" of generating an API key, so maybe even Twitter won't bother that much about these users of third-party Twitter clients using their own keys.
I'm currently using TwidereX version 1.6.0.59, installed through AuroraDroid (F-Droid client). I've cleaned cache and all app data before trying to use my generated API key.
Nothing works for me, including using my own API. TwidereX 1.7.0-beta1.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using:
This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
FYI: it seems that Twitter are definitely going after accounts using their own API keys with 3rd-party apps.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using:
This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
- They never sent me an email. I've checked thoroughly. It didn't happen.
- They don't say which "rules and policies" I've violated.
- They don't say what "certain functions" have been limited.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
WHY aren't you using official Twitter consumer key and consumer secret?
FYI: it seems that Twitter are definitely going after accounts using their own API keys with 3rd-party apps.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using: This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
- They never sent me an email. I've checked thoroughly. It didn't happen.
- They don't say which "rules and policies" I've violated.
- They don't say what "certain functions" have been limited.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
WHY aren't you using official Twitter consumer key and consumer secret?
How exactly? Can you provide clarification, please?
FYI: it seems that Twitter are definitely going after accounts using their own API keys with 3rd-party apps.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using: This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
- They never sent me an email. I've checked thoroughly. It didn't happen.
- They don't say which "rules and policies" I've violated.
- They don't say what "certain functions" have been limited.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
WHY aren't you using official Twitter consumer key and consumer secret?
How exactly? Can you provide clarification, please?
Unistall and reinstall twidere, user settings , oauth, enter official consumer key and consumer secret, password sign in(it is under sign in), don't click sign in,
FYI: it seems that Twitter are definitely going after accounts using their own API keys with 3rd-party apps.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using: This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
- They never sent me an email. I've checked thoroughly. It didn't happen.
- They don't say which "rules and policies" I've violated.
- They don't say what "certain functions" have been limited.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
WHY aren't you using official Twitter consumer key and consumer secret?
How exactly? Can you provide clarification, please?
Unistall and reinstall twidere, user settings , oauth, enter official consumer key and consumer secret, password sign in(it is under sign in), don't click sign in,
what is the official consumer key?
FYI: it seems that Twitter are definitely going after accounts using their own API keys with 3rd-party apps.
I have had success in the past using my own API v2 keys with Twidere (no 'X'), but recently I have been unable to like, post, reply, quote retweet, retweet, block or mute. That is, I have read access, but no write access. This happened during a period when I had been inactive on Twitter and have not posted, replied, liked, or (quote) retweeted — that is, I've been quiet and shouldn't be noticeable. For the past month, there's literally nothing that I've been doing other than refreshing and scrolling my feed on Twidere, and not excessively; I'm under my rate limit. Nevertheless, in the developer dashboard, I see the following message for my app, associated with the API keys I am using: This App has violated Twitter Rules and policies. As a result, certain functions will be limited. An email has been sent to [my email address] with details. For assistance, submit a support ticket.
- They never sent me an email. I've checked thoroughly. It didn't happen.
- They don't say which "rules and policies" I've violated.
- They don't say what "certain functions" have been limited.
For the moment, I'm just going to use Twidere as a reader, and when that breaks, I'm done with Twitter.
WHY aren't you using official Twitter consumer key and consumer secret?
How exactly? Can you provide clarification, please?
Unistall and reinstall twidere, user settings , oauth, enter official consumer key and consumer secret, password sign in(it is under sign in), don't click sign in,
what is the official consumer key?
Okay its working for me. I didnt realize I kept tapping the button that brings up the box for inserting keys and not tapping the actual signin button.
Twitter have announce that they will paywall API access. How will this news, posted today, affect access to 3rd-party clients like Twidere? Does this not indicate that Twitter is going to get tougher on 3rd-party apps?
Starting February 9, we will no longer support free access to the Twitter API, both v2 and v1.1. A paid basic tier will be available instead
I think the cost is going to be the big decider for what happens.
Apologies for the spam on this issue, just wanted to share my most recent experience.
Since the breakage a month or so ago I've been successfully using my own keys. Today, I tried switching to the "official" keys after the API cost announcement and just can't get it working. I get "Invalid API Settings" on sign-in, using all sign-in methods and combinations of settings. Tried uninstalling/reinstalling, using the default settings from Twidere, using other official keys, and nothing seems to be working.
Then I switched back to my own keys and was able to log in, but now I only have read-only access and can't post or like, whereas before I had no problem doing so. Twitter functionality is pretty much dead for me at this point.
Apologies for the spam on this issue, just wanted to share my most recent experience.
Since the breakage a month or so ago I've been successfully using my own keys. Today, I tried switching to the "official" keys after the API cost announcement and just can't get it working. I get "Invalid API Settings" on sign-in, using all sign-in methods and combinations of settings. Tried uninstalling/reinstalling, using the default settings from Twidere, using other official keys, and nothing seems to be working.
Then I switched back to my own keys and was able to log in, but now I only have read-only access and can't post or like, whereas before I had no problem doing so. Twitter functionality is pretty much dead for me at this point.
Ipad key + xauth or mac key + oauth + password sign in( under sign in)
Ipad key + xauth or mac key + oauth + password sign in( under sign in)
Could you provide a bit more clarity on this, please? I'm unable to parse these instructions. Thanks!
Ipad key + xauth or mac key + oauth + password sign in( under sign in)
Could you provide a bit more clarity on this, please? I'm unable to parse these instructions. Thanks!
In the box that appears when you click the button in the twidere app login page at the top, Read previous comments in the thread,
edit: seems to have resolved itself on its own now!
After the rate limit mess earlier today, I can once again scroll my timeline and lists, post new tweets and retweet fine. But I can't like tweets anymore. I get a "Network error: empty data". I also can't load anyone's tweets on their profile page - it loads the info blurb and any pinned tweets, as well as the "likes" tab in the profile, but the tweets/media tabs are empty. Is anyone else also experiencing this?
I've been on official keys since the initial 3rd-party purge in January (iPad keys at first, Mac keys now). Swapped to Mac keys because gifs in tweets didn't show with the iPad keys, but work fine with the Mac ones.
edit: seems to have resolved itself on its own now!
After the rate limit mess earlier today, I can once again scroll my timeline and lists, post new tweets and retweet fine. But I can't like tweets anymore. I get a "Network error: empty data". I also can't load anyone's tweets on their profile page - it loads the info blurb and any pinned tweets, as well as the "likes" tab in the profile, but the tweets/media tabs are empty. Is anyone else also experiencing this?
I've been on official keys since the initial 3rd-party purge in January (iPad keys at first, Mac keys now). Swapped to Mac keys because gifs in tweets didn't show with the iPad keys, but work fine with the Mac ones.
Didn't know about the GIF thing for the Mac keys, thanks!
xojojo - can confirm the same behavior you're experiencing on my end over the past 10-12 hours. Last cycle the limits went away after a certain period of time (12 hours? 24?) and I was able to "like" again. I'm using the iPad key. As long as I can read in the app it's all good.
Becoming increasingly concerned about the future - the native application is unusable to me.
After you set up mac key and secret, switch to oauth2, better than oauth,
Does anyone have the ipad keys? The link is now 404. Changed phones and now my client is locked out again
Does anyone have the ipad keys? The link is now 404. Changed phones and now my client is locked out again
CjulERsDeqhhjSme66ECg and IQWdVyqFxghAtURHGeGiWAsmCAGmdW3WmbEx6Hck
Does anyone have the ipad keys? The link is now 404. Changed phones and now my client is locked out again
CjulERsDeqhhjSme66ECg and IQWdVyqFxghAtURHGeGiWAsmCAGmdW3WmbEx6Hck
Life saver! Thank you very much, I'm back in
Sad to see the list went down. There's a reup here if anyone's still looking for something other than ipad: https://droptext.cc/3yvzy (or use the archive version https://web.archive.org/web/20230226052239/https://gist.github.com/shobotch/5160017)
just looking for an update here. is anyone able to use twidere with full functionality (now, in april) using any particular set of keys?
just looking for an update here. is anyone able to use twidere with full functionality (now, in april) using any particular set of keys?
I've been using Twitter for Mac keys since February. I have no problems accessing my timeline, lists, and search, though I probably wouldn't even notice if I was missing tweets. I'm not posting anything myself anymore so can't say if notifications and such are working. But for basic scrolling/liking/retweeting it's been working fine for me.
hey AntGeth - I was able to access on a new phone this morning success and victory
used TWTR For Mac API key /secret from this link https://gist.github.com/pvieito/ee6d2c8934a8f84b9aeb467585277b8a
ensure that your 2FA is disabled (temporarily) on twitterdotcom ( error message follows if not )
Working just fine here.
Just for clarification: the screenshot appears to be of the Twidere X app and not the Twidere app, right? The repo for Twidere X appears to be here: https://github.com/TwidereProject/TwidereX-Android
It works just the same.
got x (mostly) working with the twitter for mac keys. thanks to all!
got x (mostly) working with the twitter for mac keys. thanks to all!
Google release doesn't need key , direct download https://github.com/TwidereProject/TwidereX-Android/releases/download/1.7.0-beta02/android-google-release.apk
got x (mostly) working with the twitter for mac keys. thanks to all!
update. a week ago my twitter account was "permanently suspended". no warning, no reason given. it definitely wasn't anything i said (hadn't tweeted in quite a while). all i'd been doing was reading (and maybe a like or two) using twidere (and browser). i've appealed but no word yet.
got x (mostly) working with the twitter for mac keys. thanks to all!
update. a week ago my twitter account was "permanently suspended". no warning, no reason given. it definitely wasn't anything i said (hadn't tweeted in quite a while). all i'd been doing was reading (and maybe a like or two) using twidere (and browser). i've appealed but no word yet.
So, are you still banned?
yup. no response from them at all. i'm not sure any humans are still employed by twitter.
Well fuck it all now
Lists stopped working for me now. Still available via official app, but says not available in Twidere....Time to cue up The Doors - The End
Lists stopped working for me now. Still available via official app, but says not available in Twidere....Time to cue up The Doors - The End
Use twittnuker for android https://github.com/vanita5/twittnuker Or focustwitter x for iPhone
@Hasan5750 tried Tweetnuker, using the Twitter for Android Key and xAuth (everything else didnt work) also doesnt show lists or my own profile correctly. What settings are you using? (also isnt Tweetnuker more out of date than Twidere now?)
@Hasan5750 tried Tweetnuker, using the Twitter for Android Key and xAuth (everything else didnt work) also doesnt show lists or my own profile correctly. What settings are you using? (also isnt Tweetnuker more out of date than Twidere now?)
I'm using it with twittnuker key!
@Hasan5750 thanks, that works somehow (is someone paying for the new API access for that key?). Gonna try the Twittnuker Key on Twidere tomorrow, still having the 140 character limit is annoying. But for anyone who just wants to read that seems to be the best solution for now. Now if only TweetDeck started working properly again.
Check before submitting issue -- Thank you!
You can ignore this form if this issue is a feature request.
Expected behavior
Actual behavior
Steps to reproduce
Extra info
Android version: (version code here)
Network type:
App version: (version code here)
Build variant:
Micro-blogging service:
App settings: