Our application has some years of Calendar and Contacts API use, and now we have to add GMail API for sending e-mails. I added it on our console and it say it is enabled, but I can't use it, and I get a message telling the application is blocked (but Calendar and Contacts are going very well). Please, what is missed? Thank you!
In google developer console. Go to the Oauth consent screen. Click the edit button at the top, then save and continue. I think its the third page you come to which allows you to add additional scopes.
Remember there's no going back I really think they are going to unverify your app.
Please let me know how it goes when you do it. I am keeping notes on exigence's with the verification process.
Related
I recently asked this question and user's #DalmTo and #Sergio NH they gave me an exhaustive answer for which I thank them very much.
Moving forward to question, we started publishing the application, and its verification was not required, since no scope was added (here it is a little unclear why the requests worked in an application with a test mode in which these scope were not added (google drive, google sheet and google ads)).
However, this time the application in the "In Production" mode began to give us an "Unverified app screen" (see Unverified app screen). We decided that we still need to add scope to the list, and, of course, that the scope list (their list is described above) requires verification by Google.
We started filling in the necessary fields, while studying the Google documentation at the same time, and came across the following information (see block Verification process -> What are the requirements for verification?):
Apps not applicable for verification
Apps for internal use only
(single domain use) Apps for personal use only Apps that are Gmail
SMTP plugins for WordPress Apps that are in development or
staging/testing
Apps for personal use only
And this is just our case: we have already received permission from Google Ads and are just generating simple reports that we want to integrate with Google Sheet. I.e., this is an elementary script that works within this account (however, we still need to request the first concert screen, even for this developer account) and cannot be distributed to any other accounts.
But when adding our scope, Google requires us to pass verification, forcing us to fill in the required fields, in the form of domains and their verification via the Search Console (we have already done this and this stage does not cause difficulties) and links to Youtube videos - where we must show how scope is used.
And just this stage is not clear. We do not allow other people's accounts to connect to this application, and the software does not have any interface, it is just a script that receives data from Google Ads and saves it to Google Sheet (creating a file via Google Drive). We have described all this in the scope usage description field. But the link to the Youtube video is require field, and we sincerely do not understand why (considering our case) we should record something, and most importantly, what exactly we should record in this case. If the documentation itself says that in our case we do not even need a verification.
Maybe we did not understand something and now we are doing it wrong? We will be glad to receive any tips from experts working with Google Cloud Console and apologize in advance for broken English.
We also apologize in advance to the StackOverflow community that we have to publish such elementary (which we are absolutely sure of from our side) questions here. We come here from Google Cloud Console - > Support - > Community support, and we must first try to publish posts in the Google Groups specified there, but they simply do not answer us, apparently considering our questions too elementary and not worthy of attention (however, these same questions in Google Groups are moderated) (for example, the previous question). And we are no longer able to contact any other support. Once again, we apologize for having to ask about this here.
It is true that if your app is a single use app then you do not need to be verified.
However if you don't get your app verified then there will be some restrictions.
you will see the unverified app screen
your refresh tokens will probably only be good for two weeks.
In the case of the YouTube api uploaded videos will be suck private.
If you can live with those points then you don't need to verify your app and you can continue as is.
If on the other hand you don't want to see the unverified app screen and you want a refresh token that will last longer then two weeks. You will need to verify your app. Yes, Even if your app is a console application running as a job some where you still show the consent screen. This is the YouTube video you will need to show Google. Show the consent screen popping up show the URL bar and then show your script running. You also need to set up the homepage and privacy policy screens. Yes i 100% agree with you that this is silly.
When you go though the process. Explain to google that this is a single use script running as a job some where.
Unfortunately when Google changed it so that Refresh tokens expire for unverified apps they pretty much tied the hands of all developers who are running such single user scripts. We now have to get our apps verified if we don't want to have to request a new refresh token every two weeks.
If your program needs to access the requested scopes of the Google account privacy, even though the user is yourself, you also need to provide a youtube video to demonstrate how you use this program. The auditor cannot guarantee whether you will make this program public.
I'm trying to write a simple clientside script that used the venmo api to automate some aspects of my account. The first step is getting an access token by going to the developer tab on the settings page. However, whenever I click, "Get Token", the page just redirects me to my profile settings tab with no further information. Going back to the developer tab, nothing has changed, and I still don't have an access token. I've already filled in every aspect of my profile; my name, phone number, profile image, everything. I can't find anyone else with a similar problem. What am I doing wrong?
Unfortunately, the Venmo API is no longer available to new developers. I was having the same problem and reached out to them directly to confirm. The message I received from one of their support staff yesterday:
Thanks so much for your interest in Venmo! Unfortunately at this time we have discontinued accepting new users of our Developer API. We want to support all of our friends in the development community as much as we can, but at this time we are focusing our efforts towards expanding on our recent launch of the ability to use Venmo to purchase items in select merchant apps. Going forward this will allow us to provide many of the same capabilities previously powered by our Developer API in a more streamlined experience for users and developers alike. I apologize for the inconvenience.
It's too bad.
Could someone please give me a single up to date tutorial for implementing OAuth with twitter. I have gone through so many tutorials I have lost count, and not a single one of them is up to date with the new xCode. I tried the MGTTwitter, but there is no tutorial for it. On his own website, where it gives link to tutorial, it just links you to this
http://ww35.2bros1blog.com/2010/07/switching-from-basic-to-xauth-with-mgtwitterengine-on-iphone/
So no idea that that is about
I tried
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
But I dont know how to add the static folders to xCode. I tried adding the targets, but nothing to add.
Tried following
http://mobile.tutsplus.com/tutorials/iphone/twitter-api-iphone/
However, it is out of date. When I run the app, using my consumer key and secret, when I click authorise, it just closes window, then brings up authorisation window again. I enter user and pass again, does the same thing over and over again.
I downloaded latest version of sharekit, didnt really want to go down this root as all I want is the twitter authorisation and I think adding over 50 files or so is a bit much for one feature, but thought I would give it a shot. But when I open it up, comes up with error around facebook
(null): error: /Users/adam/Downloads/ShareKit-ShareKit-7a05403/Classes/ShareKit/Sharers/Services/Facebook/../../../../../Submodules/facebook-ios-sdk/src/FBDialog.bundle: No such file or directory
All I want is a simple authentication so users can accept and then send tweets from the app. I dont want to use the twitter framework as then users have click send twice, i.e type message into textview, then then twitter viewcontroller appears, then they click send again. I want them to be able to tweet from within the app. Yet I just cannot seem to find any tutorial that explains how to do this in detail.
Could someone please point me in the direction of a tutorial that does this, I didnt think it would be this much hassle to implement a simple authorisation into iPhone, but this is driving me insane!!!
Edit:
I got
http://www.icodeblog.com/2010/09/16/dealing-with-the-twitter-oauth-apocalypse/
This one working, however when I sign in, app crashes and the log says
Authenticated with user (null)
Anyone have any idea about that one?
Found out why I was having a problem with these twitter tools. They were using http rather than https to authenticate with Twitter which is no longer allowed. Just changed it to https and works fine
This is a problem that every developer will face when building their apps: how to contact the reviewer of your app to notify them of an update, new release, help topics, etc?
Some things I am thinking:
Include an RSS feed in your app which you can update to notify the users of the app.
Include a twitter feed regarding your app. How to go about this?
Include a way for the users to subscribe to a mailing list. This way, I can send a mass-email to the users who opted-in? Any suggestions here?
Any other ways that you think this can/should be done? Any existing solutions you can point me to will be great. Thanks in advance.
One way, for contacting a specific user who created a review of an application is to go to Zune Social (at http://social.zune.net/home) and create a new message. You can then enter the Zune Tag of the user who created a review.
Personally, I'd try to do all three - have a web page/site, with an RSS feed, and a subscription link (so they can subscribe to the RSS feed via email) and then post any updates to your twitter account as well.
You can't really force a user to do any of these, but having the options available, and linked from inside your app on the about page is probably good practise.
You could also include some kind of "Update Available" feature inside the application. Try to make this as unobtrusive as possible obviously. Obviously if they've still got the app installed they'll get an update notification from the marketplace anyway.
Sam
Besides the suggestions made by samjudson, I'll also recommend having a support-page with a direct option to send a email to you. Here's a example of a support-page from one of my applications. I've received lot of emails with suggestions for improvements, or complains about bugs. And since it's by email, it gives you the option to respond directly to people.
Another thing about reviews. Don't take them to serious. Most people only rate negatively (since humans like to complain), and by such a lot of reviews are often misinformed, outdated, or the users just been plain ignorant.
The context is a desktop app using the client-side OAuth flow for authentication.
When I first built this app nearly a year ago, Facebook's documentation said to use the following URL to generate the login/authorization dialog:
https://graph.facebook.com/oauth/authorize?client_id=XXXXXXXX&redirect_uri=YYYYYYY
This is working right now. However, I've reviewed the newly updated Authentication Guide and now see that Facebook is saying to use:
https://www.facebook.com/dialog/oauth?client_id=XXXXXXXX&redirect_uri=YYYYYYY
Does anyone know what the difference is between them, and more importantly do I need to change it? Like I said, it is working now, but I'm a little concerned about something changing when the 10/01/2011 deadline comes around.
My second question is: Does anyone know what enabling the "OAuth Migration" setting in the Apps -> AppName -> Advanced page does?
The URLs redirect to each other. But still, please make the change to the new URL. Whenever the docs change urls and the semantics are the same, you should update so as to avoid unnecessary breaking changes. Even more so with desktop apps.
Second answer: That will issue you different access tokens for now.