My goal is to retrieve Google Voice voicemail audio messages and download them.
On May 27, 2015 - Google permanently disabled the ClientLogin API for Google Voice and encouraged migration to OAuth2.0.
I created a project in the Google Developers Console, but I was unable to identify the API that should be used. I am not alone (Google voice PHP OAuth 2.0).
It seems unlikely to me that Google would permanently disable the Google Voice ClientLogin API without having a working solution available -
especially since they deprecated the GV ClientLogin API more than 2 years ago and left it available for use for so long afterwards.
After further research, I discovered that the GMail API permits downloading of attachments.
Theoretically, if I set Google Voice to forward all Voicemails to GMail, I could download the audio file using the GMail API
(gmail.users.messages.attachments.get).
NOTE: I am not certain that this will work! I worry it may not because when you click on Play Message in Gmail, it forwards to the Google Voice
page - where you can choose to download the message. It seems this approach may result in needing a Google Voice API as well.
How are we supposed to retrieve Google Voice voicemail audio messages and download them using OAuth2.0?
I own a Google Voice app for Windows 8 (GVoice) which very recently broke due to the removal of ClientLogin. From my research it looks like there is now no longer a programmatic way to authenticate to Google Voice. ClientLogin is gone, and Google Voice is not a select-able API in Google's (OAuth) Developer Console.
I'm going to interpret this question as "how do I programmatically access Google Voice now that the ClientLogin service is no longer available?"
My app uses the unofficial google-voice-java API, and that API also broke in June 2015 when the ClientLogin service stopped working.
I was able to get it working again by having it log in using a different method, but not with OAuth 2.0. See the comment thread for issue 60 (see comments 6 and 9 in particular) for an outline of the solution.
Related
Question says it all. I'm trying to interact with getting/creating/editing playlists using the Spotify iOS SDK in Swift 5. I can't find any documentation about it at all and all the other Stackoverflow questions I find are a few years old or not relevant. I'm using the SPTAppRemote, but I've got a feeling that I can't interact with playlists using this class?
The best way I found to interact with playlists and API endpoints was to use the access_token you receive from logging in and then sending regular API requests to the Web API with that token. It seems like the iOS SDK is more for authentication and playback while the Web API is used for manipulating playlists, searching, etc.
When Google Play has not been signed in, running BillingClient.startConnection() results in BillingResult returned by onBillingSetupFinished() showing billingResult.getDebugMessage():
Google Play In-app Billing API version is less than 3
This error is gone as soon as Google Play is signed in.
Is there a way to get an accurate error for this situation?
The message indicates that you are using a Google Play Developer API that is lower than v3.
The Google Play Developer API will only support the v3 endpoint after 1 December, 2019. Here is the blog post:
https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer-api.html
For more context, the Google Play Billing Library (currently 2.1.0) is the client API used in your Android app.
The Google Play Developer API (currently v3) is the server API used for managing purchases and managing your app on Google Play.
Can I use Alexa skill from my iOS application (just like we do it from the Echo dot etc)?
I checked a few old links which are working as follows, and I think it can be done using AVS:
record the message
upload it and get Alexa's response
Play it using some player
For that, it needs token (which can be obtained if a user logs in).
I checked a few SO links (link1, link2) as well but didn't get the answer.
Is there any SDK or API to do it? I didn't get enough info from AWS documentation.
Is it even possible? How to use AVS in my iOS app?
I believe you need to explore AWS LEX. It is the same service that powers Alexa. It allows you to create conversational bots, that can consume voice or text input and can give back voice or text output. You can integrate lex in any application whether it is mobile, web or voice application.
Here is a useful link that you can follow to understand how you can utilize LEX for your iOS app.
Deploying an Amazon Lex Bot in Mobile Applications
I want to use a user's voice as his password to authenticate him. I have googled and found many third party API's providing solutions for voice authentication. I have 2 questions however,
Does iOS SDK provide support to make voice authentication system using built-in API's e.g. CoreAudio etc.?
Are there any third party API's which don't require voice recordings to be uploaded to there server for authentication. (I want the app to work without internet)?
I have an application for my client that uploads videos on youtube on behalf of my client.
What my client do is provide his user name and password in my app and then app uploads videos using Youtube DATA API V2(Username/password credentials).
But since username/password authentication mechanism is not available in V3, I have to change the user involvement that is required in the new Authorization mechanism. But my client is does not agree.
The question is, what if I continue to use API V2 and not switch to V3. Is there any chance that Google will stop V2 and I have to move to V3?
Is there any way I keep authenticating using credentials and not switch to OAuth 2.0?
You asked: Is there any chance that google will stop V2 and I have to move to V3?
Short answer: You need to switch to YouTube's v3 API.
From Google:
The YouTube Data API (v2) has been officially deprecated as of March 4, 2014. Please refer to our deprecation policy for more information. Please use the YouTube Data API (v3) for new integrations and migrate applications still using the v2 API to the v3 API as well.
If you haven’t yet migrated from the previous API version (v2), we wanted to remind you it will be unsupported as of April 20, 2015, and shut down soon thereafter. To make it fast and easy for you to migrate, check out the new Migration Guide. It’ll help you identify the v3 API methods and parameters that correspond to the functionality that you've been using in the v2 API. It also points out new features that the v3 API supports.
Source
Your second question: Is there any way I keep authenticating using credentials and not switch to OAuth 2.0? I do not know the answer to. Maybe ask as a separate question?