I have recently created a project using the youtube data api v3. As the project uses sensitive scopes:
../auth/youtube
../auth/youtube.force-ssl
I have submitted the oauth consent screen for review. The review team that told me that there is no need to review the project.
Since then (2 months ago) the project is stuck at "Your consent screen is being verified. This may take up to several days. Your last approved consent screen is still in use.".
I am unable to resubmit the project at this point. Users will see the app as "unsecure" as it has not passed review yet.
Has anyone else experienced this before? Is there any way to get in touch with google if you are not on an payed support plan?
Related
We have a mobile app and our users got a
"sign in with google temporarily disabled for this app"
When they tried to login their YouTube account with iOS (There's no problem with Android devices).
We submitted a verification request long time ago, and we got from YouTube an email (May 26th 2020),(May 26th 2020):
"Hi Adam,
Thanks for working with us on the YouTube API Services compliance review. We have completed your review and do not require any further actions from you at this time.
We may reach out again to re-review your API Client for compliance with YouTube API Services Terms and Policies.
We appreciate your time working with us on this and please continue to comply with the YouTube API Services Terms and Policies."
Since then, nothing had changed and our app hasn't been verified yet, and our users can't connect with their youtube accounts.
What can we do? We are just waiting and we don't even know how to contact YouTube and ask about our specific case/project.
Thanks you,
Adam.
sign in with google temporarily disabled for this app
Means that your application has not been verified by google. You need to go through the verification process.
You can use a project for development without verification. However there are some limitations (more information here). Basically, you have now reached the limit of 100 users accessing the application.
If you still havent heard anything from google after they say they have verified your application I think the only thing you can do is to submit it again and double check that you are using a client that was created under the project that you requested verification for there's really nothing else you can do.
Hi While using Google Calendar in my iOS APP, the screen prompts a warning like as bellow
This app isn't verified by google yet...
only proceed if you know and trust the developer
To avoid this warning I need to submit my iOS App to Google OAuth Verification
I searched in different sites but i didn't get a clear doc to Submit An iOS App for Google OAuth Verification.
Could someone help to provide the steps/guidelines link to Submit An iOS App for Google OAuth Verification.
Thanks in advance...
Go to the google developer console Under credentials
You will find the consent screen tab
At the very bottom of this page you will find a button
Before submiting you should read though the information provided on that page along with the links
OAuth verification
To protect you and your users, your consent screen
and application may need to be verified by Google. Verification is
required if your app is marked as Public and at least one of the
following is true:
Your app uses a sensitive and/or restricted scope
Your app displays an icon on its OAuth consent screen
Your app has a large number of
authorized domains
You have made changes to a previously-verified
OAuth consent screen The verification process may take up to several
weeks, and you will receive email updates as it progresses. Learn more
about verification.
Before your consent screen and application are verified by Google, you
can still test your application with limitations. Learn more about how
your app will behave before it's verified.
Hello Everyone I am using the prime 31 facebook plugin for the Unity 3D engine and I am running into an issue of testing out the ability for our users to post a message containing their score onto their facebook wall.
I believe the issue is related to needing to add a publish_permission to my app yet I can't test this feature because I believe I have to have that permission approved to utilize it in my pap.
I also noticed that the approval process calls for explaining your usage of said permission and submitting your app with what I imagine would be a form of implementation .
So I guess my confusion has to do with the general process of having my publish permissions approved and whether or not i can make use of the publish permissions in my not-approved app for testing at the very least .
You should always be able to test your permissions with the admin/test/developer users of the specific app.
Have a look at https://developers.facebook.com/docs/apps/review/login#do-you-need-review which is stating that
...your app's developers will be able to see, and grant, any permission without requiring review by Facebook.
Note: People who are listed in your app's Roles tab will have access to extended permissions without going through review (e.g. publish_actions or manage_pages). For example, if you use the Facebook Plugin for Wordpress to publish your blog posts to your Facebook Page or Profile, you do not need to submit for review so long as all your publishers are listed in your app's Roles tab.
Also, if you're the developer of an app and are the only person using it, then your app doesn't need to go through review. Since you're the developer, all app capabilities should be available. You will still need to take your app out of developer mode, but you should be able to do that without going through review.
I'm trying to set up an iOS 6.0 and up app on Facebook developers, everything's hooked up and working fine using the latest SDK. The problem is that, though authentication works fine, later in the app it's requesting post permissions and when a Facebook account is not a member of the Facebook app in the Dev center, these permissions aren't requested, the screen just pops to Facebook and back to the app again without doing anything. When I try to use the app with my account that is an admin on Facebook Dev, then it works.
The posting action in question is a Facebook Graph post and it works fine for the admin account.
In previous apps I haven't requested publish permissions through the Facebook developer portal in the app settings (you know, the app review bit by Facebook), so that can't be it either. Those apps work with accounts that are not a member.
I know the code is fine, the code is re-used from previous apps.
I think it's because I am unable to enter the proper Facebook app ID in the Settings. Could that be the cause? Though the app ID is in iTunes Connect, Facebook can't find it yet because the app in review at Apple.
Any thoughts on this nightmarish user rights issue?
Since API v2 was introduced, with every new app you need to go through review for any permission apart from the three “basic” ones (those are public_profile, email and user_friends) – see https://developers.facebook.com/docs/facebook-login/permissions/v2.1
Otherwise you will only be able to ask users that have a role in the app (admin/developer/tester) for permissions – that is helpful either during testing, or for an app that is for a limited user base only; f.e. if you want your app to publish updates from your website to your Facebook page, which requires manage_pages – in such a case you should not submit for review, but just use that permission with your admin/developer/tester account associated with the app. That is further explained here – https://developers.facebook.com/docs/apps/faq#apps-all-users-are-developers
I am submitting an app that integrates with another system. In order to use the app you need to have a system login which Apple would not have.
What are the guidelines for sumbmitting an app of this nature? I assume there could be some issues if the only screen that the Apple test team can see is the login screen.
Thanks,
Joe
I created a couple of apps similar to this. We provided Apple with more or less dummy accounts that could get past the login screen, and view the basic functionality of the app, but didn't release any secret information we didn't want out
You should provide a test account for Apple reviewers and specify the login credentials when submitting the app.