we have an application that uses Authy API to send and verify OTP codes via SMS. I recently noticed on Twilio site that Authy API will be deprecated by November 1 2022. Any calls made to API after May 2023 will result in error. https://www.twilio.com/blog/migrate-authy-to-verify
I am unable to understand that should we plan the migration from Authy to Verify before November 1 2022 or May 2023.
Any clarity on this would be helpfull.
From the blog post:
Twilio will support the Authy API through November 1, 2022. After this date, we’ll start to deprecate the service for SMS/Voice. Any requests sent to the API after May 1, 2023, will automatically receive an error.
You should plan to migrate sooner rather than later because you do not want to push the migration back until it is a rush to do before the May 2023 cut-off.
The API will continue to work until May 2023, but after that it will no longer work.
Related
Hi we have a system that already has a large userbase (100k+) of microsoft users which we push updates to, using the refresh token we have saved during their inital signup.
The REST APi will get deprecated on the 30th of November in favour of the Graph API. https://devblogs.microsoft.com/microsoft365dev/outlook-rest-api-v2-0-deprecation-notice
I have upgraded all API calls to the new graph api but am faced with the following error:
CompactToken parsing failed with error code: 8004920A
From further digging it seems like it is caused since the tokens are not interchangable between the two APIs:
https://learn.microsoft.com/en-us/answers/questions/1010061/migration-from-rest-to-graph-refreshed-token-throw.html
So is there a way to port these users into the new API without having them to go through the oauth flow again, since we don't have a functionality to request this from the users?
We were calling the token flow without the scope parameter, which was working fine with the DEPRECATED API. But with the new Graph API, we had to add the relevant scope query param, and the returned token worked with the new API calls. Hope this helps someone.
Also related, the Exchange Team has published on Nov 23, 2022 that the decommissioning has been pushed to 2023, and that they will give a 6 month notice prior to the actual decommission date.
https://techcommunity.microsoft.com/t5/exchange-team-blog/outlook-rest-api-v2-0-and-beta-deprecation-update/ba-p/3682745
We use PHP backend to connect to appcelerator notification REST API. In this scenario does APNs provider API requirement starts March 31 notice applicable to Appcelerator Mobile Backend Services
Check out the post at: https://devblog.axway.com/featured/product-update-changes-to-application-development-services-appcelerator/
It says September 1, 2022: End of Support – Mobile Backend Services.
So make sure to transfer to a different push provider e.g. to Firebase (https://github.com/hansemannn/titanium-firebase-cloud-messaging) before that date.
The Titanium SDK is open source so you still can use that after that time
As AccountKit is being depreciated on September 9, 2019, Im just using the email verification, is there a good alternative or do I have to start building my own?
Thanks!!
Depreciation timeline:
September 9, 2019: Account Kit will stop integrating with new apps. Existing integrations will continue to function normally.
December 9, 2019: If you’re using SMS as a means to verify phone numbers, the daily SMS limit will be reduced to a maximum of 1,000 messages per app ID per day.
March 9, 2020: Account Kit will no longer be available for developers and partners.
June 2020: Developers and partners will have until this date to retrieve data and information from the Facebook platform unless they initiate deletion before the deprecation, in which case their data will be retrievable for 30 days before being deleted from our system.
I recommend Firebase Authentication(https://firebase.google.com/docs/auth/). there is some alternatives feature of Firebase Auth:
Email and password-based authentication
Federated identity provider integration (sign via Google, Facebook, Twitter, or GitHub)
Phone number authentication
Custom auth system integration
Anonymous auth
You can check the docs to learn more
We received notification from Twilio regarding Security changes.
We are using PHP SDK. Do we need to need take any action in this regard? If so, what should we do?
I think the best approach would be to read this notice and follow the instructions:
https://support.twilio.com/hc/en-us/articles/360007724794-Notice-Twilio-REST-API-s-TLS-and-Cipher-Suite-Security-Changes-for-June-2019
I know we can retrieve email contacts from the "Contacts" app.
What if I want to retrieve other email from let's say gmail inside my app. Is this possible?
Is there an sdk to retrieve it? e.g (the app will prompt user to login to gmail, and it will send back all the email contact)
What about Yahoo and Exchange?
Maybe this question about Gmail might help you.
I think similar to Gmail case, you can do with Exchange API and Yahoo
But Yahoo currently says:
Access to Yahoo’s IMAP service is one of the top requests from the application developer community. We are happy to announce that a Yahoo IMAP service with OAuth-2.0 will be available in early 2015. As announced on Dec 19th, 2014, we will no longer support the current Yahoo-customized Mail APIs after February 16, 2015. We will provide a migration path to this new service, which will allow us to better serve the developer community. For more information, send a mail to imap-service#yahoo-inc.com.