Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't send OTPs with MessageBird for Auth - access key invalid #1554

Closed
2 tasks done
katherineqian opened this issue Apr 25, 2024 · 8 comments
Closed
2 tasks done

Can't send OTPs with MessageBird for Auth - access key invalid #1554

katherineqian opened this issue Apr 25, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@katherineqian
Copy link

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I keep receiving the 422 response Request not allowed (incorrect access_key) even when a cURL request with the same access key from MessageBird is succeeding.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Go to https://app.bird.com/settings/security/access-keys to generate an access key as described in the docs.
  2. Get an access key with permissions for creating and viewing from /workspaces/*/channels/*/messages as described in Messagebird docs.
  3. Try making a cURL request to send a text message with the generated key. Observe that the request succeeds.
  4. Try sending an auth OTP using the same key entered into the Supabase dashboard. Observe that the request fails with Request not allowed (incorrect access_key).

Expected behavior

OTP should send to the desired phone number if the access key is working elsewhere.

Screenshots

N/A

System information

  • OS: Flutter on MacOS
  • Browser (if applies) [e.g. chrome, safari]: N/A
  • Version of supabase-js: Using supabase_flutter: ^2.3.4
  • Version of Node.js: N/A, using supabase_flutter: ^2.3.4

Additional context

Add any other context about the problem here.

@katherineqian katherineqian added the bug Something isn't working label Apr 25, 2024
@MichaelKirsch
Copy link

Same problem here

@kangmingtay
Copy link
Member

Hey @katherineqian and @MichaelKirsch, it seems like the change from messagebird to bird caused the integration to break here - the messagebird SMS provider was added quite awhile back (#210) and is only compatible with the old API.

@Ozzy1997
Copy link

Ozzy1997 commented Aug 2, 2024

hello there is there a fix fro this ?

@levismithxyz
Copy link

any fixes for this?

@kangmingtay
Copy link
Member

Hi everyone, as mentioned previously, there seems to be some incompatibility between MessageBird's API and their API after they rebranded to Bird.

We recently launched a hook for sending SMS, if you want to use Bird as the SMS provider, you can use the hook to directly make requests to their API endpoint. Here are some links which may be useful:

@J0
Copy link
Contributor

J0 commented Aug 27, 2024

Hey team,

Going to close but feel free to comment, or open a ticket if there are any issues with implementing the provider.

@J0 J0 closed this as completed Aug 27, 2024
@avocadodip
Copy link

avocadodip commented Sep 19, 2024

Would love to see this fixed for the new API!

@lubuggiano
Copy link

Would love to see this fixed for the new API!

Me too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants