Templates Plugins Courses

Advanced Twitter API plugin not obtaining user details' Screen Name but everything else

Hi @kate or any Zeroqode member,

The Advanced Twitter API plugin doesn’t seem to obtain user details’ “Screen Name”, whereas everything else seems to be working just fine. Although, until some days or a few weeks ago, I think user details’ Screen Name and everything was working fine.
What can I do to get Screen Name?

Via the Bubble debugger, it gives me the following long error message:


{“statusCode”:403,“body”:"{“errors”:[{“message”:“You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: Getting Started with the Twitter API | Docs | Twitter Developer Platform, no-store, max-age=0”,“content-length”:“360”,“x-response-time”:“4”,“x-connection-hash”:“8df74d46d851fa56c479314dad1bd20b129062550a389bbb7832dee404f61fc0”,“date”:“Mon, 25 Jul 2022 20:09:49 GMT”,“server”:“tsa_a”,“connection”:“close”},“request”:{“uri”:{“protocol”:“https:”,“slashes”:true,“auth”:null,“host”:“api.twitter.com”,“port”:443,“hostname”:“api.twitter.com”,“hash”:null,“search”:"?include_email=false",“query”:“include_email=false”,“pathname”:"/1.1/account/verify_credentials.json",“path”:"/1.1/account/verify_credentials.json?include_email=false",“href”:"https://api.twitter.com/1.1/account/verify_credentials.json?include_email=false"},“method”:“GET”,“headers”:{“Authorization”:"OAuth oauth_consumer_key=“vH9I5ZM32EuzHwMYS4nmRIoGj”, oauth_nonce=“5mC4mscBuWNlM9ML8eEwVTTwfnVPvzcq”, oauth_signature=“1QbyPyTKrVPTCd0Xz1q3gwUr2Qk%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1658779789”, oauth_token=“1550167437861163010-OVXhmoepgvPYIWJX69xXqVb6W0OwKO”, oauth_version=“1.0"”}}}


Screenshots of the error part:

Note:

UI Builder: The “Twitteraccount” element is visible.

Workflow: “Twitteraccount A Callback Tokens ready” (after it went through Twitter Authorization)

Debugger, “Run next”: Everything works just fine except for user details’ Screen Name. The error message is the one mentioned above (some letters in the URL in the error message are different each time, but shouldn’t matter I suppose?).

Please let me know if you need any other info.
Thank you in advance! :pray:

Hello @tanaka.jun.jp

Thanks for reaching out.

Your setup seems to be correct, it is indeed a strange issue, therefore we would need to run additional tests in your app. Can you please share the link to your application here, on in the DM’s. Also, if possible please enable edit rights so that we can run some tests on the separate page :slight_smile:

Looking forward to your reply.

1 Like

DM’ed :slight_smile:
Thank you for the very prompt reaction, @Kirill!

Thanks for your patience @tanaka.jun.jp

We have checked the plugin and it seems to be working fine we suspect that the issue is not in the plugin itself. However, while we are trying to pinpoint the exact issue, I’d like to kindly ask you to do the following.

  1. Please try to fill in the optional keys fields

  2. Please let us know what does the element ‘Read permission lubenda’ do? It is on your page load.

  3. As we haven’t identified the problem on the plugin’s side we recommend you to contact Twitter Support and ask about this problem and the error that you get. They will understand the problem a bit better as the issue is related to their platform :slight_smile:

Please try to do the following things and let me know the result

Apologies for not being able to resolve your issue today and hopefully we figure out what is the issue in your case!

1 Like

Appreciate your investigation @Kirill.

  1. Please try to fill in the optional keys fields

I just filled them in with the exact same keys as the live ones – tested right now, still the same results as first described.

.

.

  1. Please let us know what does the element ‘Read permission lubenda’ do?

Nothing to interfere with Twitter API, I think. It’s just another SaaS that takes care of GDPR and such lawful stuff (link to Iubenda). Twitter API was working just fine with this until some (unknown) time ago.

.

.

  1. As we haven’t identified the problem on the plugin’s side we recommend you to contact Twitter Support and ask about this problem and the error that you get. They will understand the problem a bit better as the issue is related to their platform :slight_smile:

Got it. Anything I can share, I will.
Meanwhile, I would appreciate your findings too. :crossed_fingers:

Thank you again!

1 Like

Hi @Kirill, just an update.

I guess it was lame of me not really reading the given error message — I just needed to apply for Twitter API Elevated access, which I did just now.
Hopefully within 48 hours (as they say) I will gain access to it and the issue will be solved :crossed_fingers:

Will share how it goes.

2 Likes

Hi @Kirill, sorry, still needing your help :frowning:

  • A few hours ago today I got approved by Twitter for Twitter API Elevated access. Nonetheless, after getting through Twitter’s “Authorize app” screen (Screenshot 1) and coming back to my site, Twitter authorization on my site still didn’t work, showing the popup saying “Sorry, we ran into a temporary bug and can’t complete your request. We’ll fix it as soon as we can, please try again in a bit!” (Screenshot 2)

Screenshot 1:

Screenshot 2:

  • After the error popup, the Bubble debugger just dies out at “Twitter: Get token” and doesn’t carry out the rest of the workflow.
  • Looking into Chrome dev tool Console, I find the following error message (Screenshot 3):

run.js:8 Unexpected server error: please report the code parameter to the team
at n.from_json_client (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1458269)
at https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:91724
at https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1406557
at https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1406370
at h.resolve (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1405914)
at https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:45659
at https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:811689
at Object.r [as WaitFor] (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1410821)
at i.wait_for_lib (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:1245119)
at h.recheck_uid (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:811220)
at Object. (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:8:45626)
at i (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:4:27983)
at Object.fireWith [as resolveWith] (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:4:28749)
at A (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:6:14203)
at XMLHttpRequest. (https://dhtiece9044ep.cloudfront.net/package/run_js/f180ff46840632f55f5edf4ead96e0c2f666fb4fd8fc1db1dc182b3ddbffd8c5/xfalse/x16/run.js:6:16491)

Object
d.log @ run.js:8


Screenshot 3:

  • After this error, I’ve changed the Twitter API tokens/keys just in case — no luck.
  • I’ve tried and input newly generated Twitter API tokens/keys into the live mode only, then also into the dev mode — no luck.

Now, is there anything you could kindly check for me or suggest I should do? I’m lost :confused:

Thank you again,
Jun

Hi @tanaka.jun.jp

We’ve just checked your app and everything seems to work well. Can you please check it on your side again and let me know if the issue still persists?

Thanks,

Kirill

Hi @Kirill,

Thank you for checking up.

I still get the exact same result, not working.
Also, the page you’ve created in my app doesn’t seem to be working, either; via that page, I can’t even go through the Twitter authorization screen (Screenshot).
Do you have any specific setup for it to be working?

Are you still getting the error on ‘Twitter: get tokens’ action? We can’t seem to reproduce the issue in your app. We receive the Nametwitterscreen name and all the other data: Loom | Free Screen & Video Recording Software. As for the page created, it was mainly created to check the workflows and run some tests.

Looking forward to your reply.

Lol, nice to see it working. But no, on my end it’s still not working… I just created a completely new user, but no good. Still the same error popup.

Sorry but could you maybe tell me what your setups are like the following?
Mine are;

  • version of the Advance Twitter API plugin: 1.14.0 (latest)

  • version of Bubble: Version 16 (some experimental features not deployed)

  • used browser and its version: Chrome, version 103.0.5060.134 (latest)

  • used PC, OS name and version: MacBook Pro, macOS Big Sur, version 11.2

Please let me know if there’s any other setups you think might be different than mine. Desperate here.

Thank you so much for your time, @Kirill.

We are suspecting that the issue is that the Twitter account you are testing with does not have any tweets or followers, and the account does not follow anyone. If the account does not have any of these, the authorization is going to fail.

Also, are you previewing the page in live mode or development mode? Can you please screen record the authorization process? (Use the Loom tool if possible) It is very strange indeed, as we have tested both on the latest macOS and Windows devices, and the authorization works on our end.

Please let me know these additional details, so that we can resolve it asap :slight_smile:

Solved!! Confirmed on test and live mode both! Thank you so much!!!
Is there anywhere I can tip you (or Zeroqode)? For now I can and will only tip a little one, but later will do a bigger one.

We are suspecting that the issue is that the Twitter account you are testing with does not have any tweets or followers, and the account does not follow anyone. If the account does not have any of these, the authorization is going to fail.

It was really this…! Looks like Twitter have added restrictions like this (when they added the Essential/Elevated access etc) that I’m sure were never there some time ago. Really appreciate you figuring it out for me!!

Happy to hear that it works well now, and thank you for kind words :slight_smile:

The best tip you can do is to leave an honest review about our products and support! You can share your thoughts on Trust pilot, here is a link: Zeroqode Reviews | Read Customer Service Reviews of zeroqode.com. We always appreciate our customers’ feedback and value each review.

In case there are any other questions, just let me know and I’ll be happy to help.

1 Like

I just left a review there :smiley: Hope that helps you guys grow even more!
Thank you so much again @Kirill!

Jun

2 Likes