-
Notifications
You must be signed in to change notification settings - Fork 87
verifyToken received by requestSms fails after update to v3.0 #57
Comments
Has this ever been resolved ? |
facing the same issue, what's the status? is it fixed or not ? |
Hi, sorry for the late reply. This is in our timeline for next release that will happen next week. |
So, I was taking a look at this and couldn't reproduce the issue. Using https://github.com/luisuribe/authy-sample-app I did some tests with a token starting with zero and it works. Could you please share some code so we can check and maybe find a solution? Also, please have in mind that from 2.2 to 3.0 there's a lot of changes (sadly without a changelog, but that's going to change) that could cause your app to stop working. |
This issue is not reproducible, moreover kindly add method to generate
Qrcode as well for google authenticator, I have created one but I want you
to implement it in our branch so it will be good for others too.
public function getQrCode($format,$authy_id, $opts = [])
{
$authy_id = urlencode($authy_id);
$format = urlencode($format);
$resp = $this->rest->post("/protected/{$format}/users/{$authy_id}/secret",
array_merge(
$this->default_options,
['query' => $opts]
));
return new AuthyResponse($resp);
}
…On Wed, May 1, 2019 at 12:19 AM Luis Uribe ***@***.***> wrote:
So, I was taking a look at this and couldn't reproduce the issue. Using
https://github.com/luisuribe/authy-sample-app I did some tests with a
token starting with zero and it works.
Could you please share some code so we can check and maybe find a solution?
Also, please have in mind that from 2.2 to 3.0 there's a lot of changes
(sadly without a changelog, but that's going to change) that could cause
your app to stop working.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALHOYRAGMSGMFKW2JXJVD4TPTCLUJANCNFSM4FRD3K6Q>
.
|
Hi @luisuribe, Resolved |
Trying to upgrade from v2.2 to v3.0
Able to receive a token (int in v3.0, was string in v2.2) via SMS, but when verifying given token, API returns "token invalid"...
Is there a changelog somewhere I can read through to try to find (breaking) changes ?
Have already gone through the docs at https://www.twilio.com/docs/authy ...
The text was updated successfully, but these errors were encountered: