Hi @themingster,
Do you use the transformer Tweeter or TweetSearch?
Thanks
Hi @danilo_inovacao, it's the "Tweeter" transformer I'm using to post a tweet and I follow that account to pick up the notifications.
By the way I'm quite the novice at FME.
Hi @themingster, i tested here in my PC and has this error too. I believe the policies authorization of tweet was changed, so the reason the error is show in transformer.
Thanks,
@themingster
I installed the FME Desktop 2017 1.0.0 ( Build 17523 - Beta ) and tested the transformer but without success. The same error was show in the Log file 
.
I checked that the url to send request in twitter actually is: https://dev.twitter.com/oauth and not https://api.twitter.com/oauth/access_token that is generate by transformer TweetSearch.
I believe the reason the error is the URL.
Thanks in Advance,
Danilo de Lima
I am also facing the similar issue with the "TweetSearcher" transformer since a couple of days. Before that, it was working absolutely fine.
https://knowledge.safe.com/questions/47672/tweetsearcher-authentication-issue.html
My guess is that Twitter have changed something. I've flagged it as a high-priority issue with our developers and will get back to you.
My guess is that Twitter have changed something. I've flagged it as a high-priority issue with our developers and will get back to you.
Mark, thanks very much.
I thought I had broken something or that it was a firewall issue.
Will wait your reply.
Adrian
As a temporary workaround, you may be able to use the Twitter API through a HTTPCaller.
In this question I mention how to I have spoken about how to authenticate with it, and then use the general Twitter search tool. I'm not sure what the limitations are from the authentication method. https://knowledge.safe.com/questions/45854/httpcaller-and-twitter-api-authentication-problems.html
Looks like it'll be fixed in the next release :-)
"Tweeter_Tweeter(TwitterFactory): Due to a change in the Twitter API, all Twitter transformers are non-functional. Updated transformers will be released with FME 2017.1.1"
My guess is that Twitter have changed something. I've flagged it as a high-priority issue with our developers and will get back to you.
Hi @Mark2AtSafe,would you be able to let us know as soon as it is available even in a beta release of 2017.1.1? Thanks.
Hi @Mark2AtSafe,would you be able to let us know as soon as it is available even in a beta release of 2017.1.1? Thanks.
Will do @gisinnovationsb - it should be very soon now. I'm hoping for a beta fix by the end of the week. We're aware it's a priority issue for users and we're doing all we can do get it fixed asap.
Will do @gisinnovationsb - it should be very soon now. I'm hoping for a beta fix by the end of the week. We're aware it's a priority issue for users and we're doing all we can do get it fixed asap.
Thanks @Mark2AtSafe, and also to all the developers working on this as it is not easy to keep track on the API changes made by third party products.
My guess is that Twitter have changed something. I've flagged it as a high-priority issue with our developers and will get back to you.
Thanks Mark,
One use of the Tweeter is to let me know when the server storage is below a certain threshold and I can therefore take action. This is because the IT company we employ has a habit of phoning us when the storage gets low, then they send us a bill for the pleasure!
Got a phone call from them last night
£££££££
Thanks Mark,
One use of the Tweeter is to let me know when the server storage is below a certain threshold and I can therefore take action. This is because the IT company we employ has a habit of phoning us when the storage gets low, then they send us a bill for the pleasure!
Got a phone call from them last night
£££££££
@themingster @gisinnovationsb Have a try with the latest 2017.1.1 beta. I believe the fix should be in there for Desktop. You may have to create a specific web connection, and I don't think Server is ready yet because the interface isn't updated to handle those yet. I'll see if I can give it a go myself too.
@themingster @gisinnovationsb Have a try with the latest 2017.1.1 beta. I believe the fix should be in there for Desktop. You may have to create a specific web connection, and I don't think Server is ready yet because the interface isn't updated to handle those yet. I'll see if I can give it a go myself too.
Hi Mark. It sounds great. I will give it a try and get back to you. Also please let us know when it runs on server as I want to try it out on fme cloud.
SOLVED.....
The beta works(Windows x86 for me), I just needed to upgrade the transformer and enter the Twitter account info an authenticate it again and now everything working again.
https://www.safe.com/support/support-resources/fme-downloads/beta/
@themingster @gisinnovationsb Have a try with the latest 2017.1.1 beta. I believe the fix should be in there for Desktop. You may have to create a specific web connection, and I don't think Server is ready yet because the interface isn't updated to handle those yet. I'll see if I can give it a go myself too.
@Mark2AtSafe Success!!! Thanks for the help. The transformer just needs updated and Twitter account re-entered.
Will do @gisinnovationsb - it should be very soon now. I'm hoping for a beta fix by the end of the week. We're aware it's a priority issue for users and we're doing all we can do get it fixed asap.
Hi @Mark2AtSafe, are they any updates on the server side? Thanks
Hi @Mark2AtSafe, are they any updates on the server side? Thanks
Hi @gisinnovationsb - yes, I believe the final commits went in last Friday. The build number that looks best to me is 17646. So far only build 17643 is on the web site. If you really needed it then that version should work (but there were a couple of minor bugs that got fixed in 17646, so it wouldn't be perfect). Let me know if you try it and have problems.
Hi @gisinnovationsb - yes, I believe the final commits went in last Friday. The build number that looks best to me is 17646. So far only build 17643 is on the web site. If you really needed it then that version should work (but there were a couple of minor bugs that got fixed in 17646, so it wouldn't be perfect). Let me know if you try it and have problems.
Thanks for the update @Mark2AtSafe , I wanted to give it a try on Cloud as well, but it is not urgent. I will start working with what I have.
Thanks for the update @Mark2AtSafe , I wanted to give it a try on Cloud as well, but it is not urgent. I will start working with what I have.
News is that 17647 is the current candidate to be released next Tuesday. Just giving it a final look over to make sure is all good to go.
News is that 17647 is the current candidate to be released next Tuesday. Just giving it a final look over to make sure is all good to go.
That's fantastic, thanks !
