Hi @kanishk3687,
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
Hi @danillo_inovacao,
Thank you for quick response. I checked Twitter API and it mentions about access_tokens (https://dev.twitter.com/oauth/reference/post/oauth/access_token), however, I am not sure what is the workflow of FME TweetSearcher Transformer.
Strangely, it was all working fine a few days back. That means, there must be some recent changes within Twitter API.
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 @kanishk3687, like @Mark2AtSafe wrote the URL was changed. :)
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
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 any news on this one? All my workspaces with TweetSearcher are now failing with 403 Forbidden and causing me some headaches!
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
Hi @colinhenderson. Did you try @jlutherthomas's workaround suggestion?
Hi @Mark2AtSafe any news on this one? All my workspaces with TweetSearcher are now failing with 403 Forbidden and causing me some headaches!
Not yet. I've been off on vacation until today, so I will check it out and see what the status is.
Hi @Mark2AtSafe any news on this one? All my workspaces with TweetSearcher are now failing with 403 Forbidden and causing me some headaches!
It seems to be a bigger issue than you would expect. It means adding some extra OAuth support and that means updating both the engine and the interface. From what I can see I wouldn't expect a solution in the next couple of weeks (I just don't see an imminent fix). Can you go with the HTTPCaller workaround for now?
NB: It's not that we aren't doing anything - I can see lots of action going on in development. It's just going to be a longer time than I think anyone realized at first.
as an fyi, in the future I think transformers like these will end up being moved to the FME Store. That way they can be updated without you having to update FME every time (though having said that, the combination of OAuth and interface changes might have made it necessary anyway in this case).
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.
Was hoping to avoid the HTTPCaller workaround, but since that seems like the way forward for now I'll implement it.
Was hoping to avoid the HTTPCaller workaround, but since that seems like the way forward for now I'll implement it.
Yes, dealing with the authentication issue has been more trying because Twitter's approach is different than the others (Google, Salesforce, Dropbox, etc) that we support now. We are close to having the new support into a Beta FME 2017.1.1 - and if you don't need this on FME Server we may be able to get you something sooner rather than later. Let us know your timelines (via live chat or support@safe.com) and we can advise on options. Our goal is to release 2017.1.1 in early Sept.
Yes, dealing with the authentication issue has been more trying because Twitter's approach is different than the others (Google, Salesforce, Dropbox, etc) that we support now. We are close to having the new support into a Beta FME 2017.1.1 - and if you don't need this on FME Server we may be able to get you something sooner rather than later. Let us know your timelines (via live chat or support@safe.com) and we can advise on options. Our goal is to release 2017.1.1 in early Sept.
Thanks Dale, will need this on server and timeline is pressing - this week! I have created a custom transformer which I'll share on the FME Hub as I needed some additional functionality as well - multiple tweet searching - so I was already wrapping the original transformer anyway.
