Authentication issue with Twitter endpoint
I believe that this sample (TwitterClientCore App) does not work anymore as Twitter has deprecated the use of v1.1 endpoint as stated in: https://developer.twitter.com/en/docs/twitter-api/v1/tweets/filter-realtime/overview (it returns 403 forbidden error)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: e9636d03-2832-6aaf-9b92-dc67e7ba16fb
- Version Independent ID: eb372908-c7f1-313b-198e-8f960cadda6c
- Content: Social media analysis with Azure Stream Analytics
- Content Source: articles/stream-analytics/stream-analytics-twitter-sentiment-analysis-trends.md
- Service: stream-analytics
- GitHub Login: @enkrumah
- Microsoft Alias: ebnkruma
Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.
Thanks , Let me know
Il giorno ven 5 ago 2022 alle 19:12 Kranthi Pakala @.***> ha scritto:
Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.
— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/96761#issuecomment-1206718638, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOGTLTFQBYFEVSINRY66JILVXVKQRANCNFSM55WZYH4A . You are receiving this because you authored the thread.Message ID: @.***>
#reassign: @an-emma
Any updates on this? thank you
Any updates ?
Il giorno ven 5 ago 2022 alle 21:30 Ebenezer Nkrumah < @.***> ha scritto:
#reassign: @an-emma https://github.com/an-emma
— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/96761#issuecomment-1206840840, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOGTLTD3IHASADF5VQGJ543VXV2WDANCNFSM55WZYH4A . You are receiving this because you authored the thread.Message ID: @.***>
Thanks for spotting it. investigating now.
Any updates? Im having the same issue
Any updates? Im having the same issue
@an-emma
hi @thecodeman1987 , we are tracking this problem internally, and it might take some time to update the doc. I'm closing the case for now and updating the doc as soon as we find a solution. Thank you.
#please-close