allow custom SMS OTP messages from client

Source: supabase/supabase#10873 · opened by @anngbaum

We have an active iOS and Android app. Both use SMS OTP for verification. On iOS, the auto-fill with the OTP works very nicely out of the box. On Android, however, we have received user complaints that login is clunky. With Google's [current offering]( my understanding is that we can offer similar functionality, but it requires adding an ugly hash to the end of the message: ![Screen Shot 2022-12-12 at 10 36 24 AM]( One way I thought this could work better is if the client could pass an optional parameter up to the verifyOTP endpoint like additional_info, and have that be appended to the message in the same way as {{ .Code }}. That way if the client knows it's an Android device, we could append that hash. So from Android, we would simply run: let { session, error } = await supabase.auth.verifyOTP({ phone: '+13334445555', token: '123456', type: 'sms', additional_info: 'FA+9qCX9VSu', }) and the SMS language …

4 years ago