As announced last month, today marks the beginning of callback URL whitelisting enforcement. Apps using Sign in with Twitter who have not whitelisted their URLs will experience disruption. To whitelist your URLs, follow the guidance in our May forum post.https://twittercommunity.com/t/action-required-sign-in-with-twitter-users-must-whitelist-callback-urls/105342 …
-
-
@TwitterAPI-কে উত্তর দিচ্ছেন
I found out about this change when `omniauth` returned 403s. It would've been helpful if you promoted API change tweets to users in the platform that have Apps in their account. Even Instagram sent me an email, and that's from a company that deprecates it's own official gems.
১ reply ১ টি পুনঃটুইট ২টি পছন্দ -
@CSMattRyder @TwitterAPI-কে উত্তর দিচ্ছেন
Were you able to fix this? I can't seem to get this working in development no matter the callback url I set. Others seem stuck as wellhttps://stackoverflow.com/questions/50826742/omniauth-twitter-with-rails-5-stopped-working-oauthunauthorized-403-forbidden …
১ reply ০ টি পুনঃটুইট ০টি পছন্দ
Yeah, was as simple as setting that callback url to /auth/twitter/callback. Try installing `better-errors` and using the debugger prompt to ensure the right URLs are being set.
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।