With the "Advanced Twitter API" plugin, how to get users to authorize the Twitter API?

[tanaka.jun.jp]

Hi Zeroqode team,

I’m using the Advanced Twitter API plugin, but been facing an issue.

Through my app (clicking the button below), I can’t seem to go through as done in your demo app.

Instead, it only shows me an error message as below reading;
“Whoa there! The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake.”

Could you tell me how I might be able to fix this?

---

What I’ve tried

• I’ve regenerated API keys and Access Tokens over and over and copy-pasted them into the plugin setting as below. (The keys shown are old ones).
  

  

• I had removed the keys from the “-dev” columns from the above screen.

• My Twitter API Authorization workflow is as follows
  

  
  
  
  

• My Twitter Developer account settings;
  – Read and Write
  – 3-legged OAuth is enabled
  – Callback URLs (not sure about them, but just did read this): my app URL, its page URL I’ll be using the API in, my app URL but without the last " / "
  – Website URL: my app URL
  

  

Any tips would be much appreciated.
Thanks in advance!
Jun

[tanaka.jun.jp]

Looking for help…! @Serg @Ecaterina @alexandru

[kate]

@tanaka.jun.jp, thanks for reaching out, and please accept my apologies for the late reply.

@tanaka.jun.jp

Callback URLs (not sure about them, but just did read this): my app URL, it’s page URL I’ll be using the API in, my app URL but without the last " / "

Please be sure to introduce the related callback URLs into your Twitter development account.

Within the “Callback URLs” section you should include all pages where the Twitter plugin is used/included, and on “Website URL” you need to indicate the general URL address of the application.
See the example on our demo page:

For example, we’ve created a zq_twitter_test page on your app, and its address https://magnele.com/version-test/zq_test_twitter should be also included in Callback URLs.

After that, within the “Keys and tokens” tab, please regenerate and insert all the related fresh API keys and tokens in corresponding fields.

Please try the suggested variant and let me know how it goes.
Hope it helps!

[tanaka.jun.jp]

Thanks @kate,

Within the “Callback URLs” section you should include all pages where the Twitter plugin is used/included, and on “Website URL” you need to indicate the general URL address of the application.
See the example on our demo page:
After that, within the “Keys and tokens” tab, please regenerate and insert all the related fresh API keys and tokens in corresponding fields.

I tried all that (screenshot ↓), but it still gives me the exact same error message mentioned above.
Or what else can I do to possibly solve this?
(I hope the “Request email address from users is disabled” setting is not causing the issue?)

The URLs I put in as Callback URLs should be fine:

For example, we’ve created a zq_twitter_test page on your app, and its address https://magnele.com/version-test/zq_test_twitter should be also included in Callback URLs.

magnele.com is not my app. But I understand your point.

Thanks again,
Jun

[tanaka.jun.jp]

@kate or maybe @Serg @Ecaterina @alexandru
Hope to hear back on this before the end of the day.

[tanaka.jun.jp]

@kate @Serg @Ecaterina @alexandru, or anyone from @zeroqode
Help please. Been left more than a week…

[kate]

@tanaka.jun.jp,

Please accept my sincere apologies for this awful delay. I’m sorry for this
Let us please check the details you’ve provided and get back to you tomorrow.

Once again, sorry for the delay.

[Serg]

Hi @tanaka.jun.jp, sorry again for the delayed reply.
Allow me to reply on behalf of my colleague.

@tanaka.jun.jp

I tried all that (screenshot ↓) , but it still gives me the exact same error message mentioned above.
Or what else can I do to possibly solve this?

If the issue persists, kindly note that inserted API keys & and tokens possibly are inserted wrong and/or are not regenerated considering the newly inserted URL link.
We’ve checked the authorization process on the settings page of your app using out API keys & tokens and all was working well.

To fix the issue, please:

• insert related page URL to the corresponding project on Twitter

• within the “Keys and tokens” tab, please regenerate and insert all the related fresh API keys and tokens in corresponding fields.

• make sure that the link inserted in the callback URL - is the same that you obtain on preview, and Bubble is not adding anything else to the link end.
  

  

So, for testing purposes, please use any registered user profile from your app

Hope it helps. Please apply the proposed solutions and tell if the issue will disappear.

Looking forward to your reply.
Regards,

[tanaka.jun.jp]

Hi @Serg

Thank you for the reply!

• insert related page URL to the corresponding project on Twitter

My apologies, I was missing the last " / " - I should have had “XXXX.bubbleapps.io/version-test/settings/” on Twitter Developer settings in my case.

• make sure that the link inserted in the callback URL - is the same that you obtain on preview, and Bubble is not adding anything else to the link end.

The URL I get right after hitting the “Preview” button is like this;
https://XXXX(my app name).bubbleapps.io/version-test/settings/Lorem%20ipsum…?debug_mode=true
With this URL, it wouldn’t work through to Twitter authorization.
But when I drop “Lorem%20ipsum…?debug_mode=true” and make it to https://XXXX.bubbleapps.io/version-test/settings/ it does work through just fine.

Now, my question is, when I deploy the app to live, will the “Lorem%20ipsum…?debug_mode=true” part be removed without me doing anything? Or will I have to do something to have it removed when live?

Excuse me if my question is now out of your work scope.
Thank you again!
Jun

[Serg]

Hi @tanaka.jun.jp, sorry for the delayed reply (due to the weekend).

@tanaka.jun.jp

when I deploy the app to live, will the “Lorem%20ipsum…?debug_mode=true” part be removed without me doing anything? Or will I have to do something to have it removed when live?

If the “settings” page will be accessible only for logged-in users - then no actions are required.
By now, before going live, to have a proper testing process, please run your page from any particular user profile from your app database.

@Serg

So, for testing purposes, please use any registered user profile from your app

Hope it helps. If there is anything else that I can help with, please let me know.
Regards,

[tanaka.jun.jp]

Hi @Serg,

I think now it’s solved, thank you again!

The followings are just for note -

If the “settings” page will be accessible only for logged-in users - then no actions are required.

I just made this Workflow, which does kick me out when not logged in. I believe this is good enough.

And I found that, if I blank Type of content in the Settings page, the unwanted “Lorem%20ipsum…?” bit out of “https://XXXX(my app name).bubbleapps.io/version-test/settings/Lorem%20ipsum…?debug_mode=true” is gone, because that way the Settings page doesn’t require any data sent into the page

Thank you again for answering my questions!
Jun

[Serg]

Hi @tanaka.jun.jp, thanks for letting us know that the issue is solved .

If there is anything else that I can help with, please let me know.

Have a nice week!
Regards,