Actually, I’m connect with cloud server.
E-mail and Notify works OK, but twitter broken.
EDIT - Twitter status on Cloud Server is now unclear again… I don’t tweet anyhow, so I am leaving this issue well enough alone 
Rebuild code with Arduino Uno + Wiznet W5500 Ethernet2
Not worked too with twitter and OK with E-mail.
Bumped, Twitter widget is dead.
@Gunner, I hate to bring this up again, but when @Dmitriy said they have no plans to make the Twitter Widget work and you asked if this included the Twitter Widget working with the Cloud Server and @Dmitriy said, “No” … can I take this to mean they plan to fix the Twitter Widget in conjunction with the Cloud Server? Has there been any further discussion regarding a bug fix in the last few weeks I may have missed?
I haven’t a clue how to interpret some of Dmitriy’s answers 
I don’t clearly recall any follow up commentary… but I suspect twitter may be one of those “soon to be dropped” options from Blynk’s beginnings.
I never twit (tweet? twitter?), so I personally don’t care… I was just trying to assist others whenever it came up, so I created an account that shall forever remain unused 
And then I saw this in another recent topic… so now I really don’t know 
@Gunner for BLE/BT Blynk.tweet (and, probably, Blynk.mail) will work in same way as Blynk.notify, so it is not about twitter widget in its ordinary way.
OK… so Blynk can still use twitter?? It is just that a few people have ran into issues (using Cloud) tryng to do so, that havent been resolved… or even officially looked at. AKA this topic for one.
Again, I am not going to test it anymore myself … so I will leave this issue as is for others to work on. But thanks.
I mean that the update I’ve uploaded to beta is not about sending tweets to twitter. It just handle the tweet/notify request from BLE/BT hardware and shows an alert with their message, nothing connected to twitter.
OK, I got it… so my reference of your other post was not relevant to this OP 
But rather that post was just saying that notification (and apperenly twitter) calls in the sketch will now register on the phone in BT/BLE connection mode now, just as it did in other WiFi, ethernet, etc. modes.
Sorry to confuse this OPs issue then.
@BlynkAndroidDev, Would you please talk to @Dmitriy and find out whether Twitter Widget + Cloud Server is dead or whether the bug will be fixed.
@BlynkAndroidDev, @Dmitriy, @vshymanskyy or @Eugene,
Would one of you please help us understand the situation as it relates to the Twitter widget. Would you please acknowledge that it’s not working in conjunction with the cloud server. Would you please let us know if this bug will be fixed or whether the Twitter widget is being retired.
Thank you,
Joe
1 Like
Hello. We will check. From your side you need to check if your account is active, you don’t send the same message in your tests, you don’t exceed message limit.
Thank you, @Dmitriy!
The problem could (in theory) be my Twitter account, however, I guarantee the issue is not sending the same message more than once (I always include a timestamp in each message) and I’m not exceeding the message limit.
To the broader Blynk Community … is the Twitter widget working for you (with the cloud server)? On either platform? With any firmware version?
As stated in my OP, I thoroughly tested the Twitter functionality when I made the post (though haven’t tried using it since). It worked before in the same manner (with a timestamp to make every tweet unique) and even a brand new account didn’t make a difference. Using the original code didn’t make a difference either.
I’m using the cloud, not a local server. More information regarding versions and hardware can be found in the OP.
All the things Dmitriy mentioned were functioning correct in my case.
If I can be of any help let me know. Good luck devs!
@PeterNL, Your OP was clear and comprehensive. I basically followed the exact same steps. The Twitter widget isn’t working for @Gunner and @maxxir. I was just wondering if the Twitter widget is currently working for anyone. I’m sure @Dmitriy will help us sort this out.
1 Like
You are abusing name tagging. Please stop doing that. Once someone is in the topic, they get notifications.
Issue confirmed. Twitter had limited our application due to high update rate. Waiting for response from twitter.
Not by default. I receive Notifications when someone directly replies to my post, when someone “Likes” my post and when someone identifies me in a post using @wickedbeernut. Note: I received a notification when Dmitriy replied to my post on this topic. However, I didn’t receive a notification when you posted to the topic complaining that I was abusing tagging. You didn’t reply to me, nor did you include @wickedbeernut. Obviously, you didn’t “Like” my post. 
Consequently, I wasn’t notified. I’ve never changed my Notifications settings. This is the default behavior. This is the difference between Tracking a topic (default) and Watching a topic. I could change my settings from,
to,
however, this won’t change the way in which the vast majority of your Community Members receive Notifications. I don’t believe I’m abusing “name tagging”. I believe I’m using it exactly the way it was intended to be used. I’d be happy to use it more sparingly.
The Twitter Widget is working again. Thank you!