Google Cloud Support asked me to reach out here to get an answer as to why we're receiving an error that is shutting down our API. The error is: QUOTA_CIRCUMVENTION
Details
Project impacted: Barrows Levy Videos (id: barrows-levy-videos)
Description: Circumventing our quota restrictions via multiple projects acting as one.
We are only using one project and have the playlist getting pulled into the website https://www.barrowslevy.com/.
How do we resolve this issue? We've already been shut down with a previous API and we had to create a new Restricted one. This one was also flagged.
How are we circumventing the quota? What can we do to NOT circumvent the quota?
Related
I am getting this message in my AdMob account.
IAB TCF v2.0 errors detected We've detected an issue on your IAB TC string on one or more of your sites or apps. These errors may affect your ability to serve ads to European users. A detailed report is available for you on the EU user consent page.
And as I found error 3.3 indicates that The TC string last updated date was more than 13 months ago. and the suggested action is CMP should delete the old TC string and reobtain consent.
And I am using Funding Choices as a CMP, so how can I resolve this issue?
Do I need to do any changes to the app for it?
Please guide me on the solution if anyone has solution of this issue, it will be very helpful to me
Thanks
according to that Google group if you are using UMP SDK, and you probably are as you're using Funding Choices like me, it should be handled by the SDK itself. So nothing to worry about, if the error persist, meaning it present itself in several different days, than I fear the only way is to open a ticket with Google Admob.
Currently the creation of a channel through the Graph API frequently results in the relative, corresponding Sharepoint folder not being created.
When using the Graph API to create a channel the response indicates creating the channel was a success, but when going to the files tab it shows:
"Your files can’t be found, working on it to restore them."
After having clicked on the files tab in the Teams UI, the folder is created eventually (after a couple of minutes).
But because automated processes depend on the channel folder, we don’t want to ask the user to manually open the team before the other processes can continue.
So: Team created: Ok -> Channel created: Ok-ish (But missing the linked folder) -> One-drive/share point folder, with the name of the channel: Not created
Sometimes the folder is created properly, but lately more often it is not created (Not even after 3-4 days of waiting) until the user opens the files tab in the Teams client.
This behaviour is new since it worked flawlessly until a week ago. Is there a known workaround for this?
We're following the default documentation for creating a channel via Graph API as described in the Microsoft Graph Reference
Best regards,
Dominic
This is by design or rather limitation of SPO provisioning is async as in create team succeeds without waiting for SPO site provisioning completes. In those scenarios when channel get provisioned before SPO that get created without files folder. The recovery mechanism is accessing files tab in the channel.
Currently there isn't any solution to check if provisioning is completed. However, there is a feature ask to provide an API to provision similar to what happens on the client (clicking on Files tab). We do not have any ETA on this.
I am using Zapier to send a pin to my Pinterest account from Google Sheets
but it is showing me an error:
We had trouble sending your test through. The app returned "Sorry! We
blocked this link because it may lead to spam.". It looks like the
server for your connected app is down or currently experiencing
problems. Please check the app's status page or contact support if
there are no reported issues.
My Sample Record
My sample Excel File
My Board Link where I want to pin
If you have not already reached out to them, I would suggest that this is the perfect question for Zapier's support team. They are quite punctual and have access to information regarding specific app integration status' that we, the general public, will not. That said this looks like it may be a symptom of an error with Zapier's Google Sheet integration. At the time of this writing Zapier is reporting 429 errors concerning Google Sheets. If I am ever facing unexplained errors with one of my zaps the first place I check is https://status.zapier.com/ which has live updates and reports on any integrations that may be facing issues.
I run my own VPS in Amsterdam where I have a MySQL database that is being populated and maintained using ASP.NET. It's a Windows Server.
I use this API for four of my existing Android apps (published and working) with a few thousand users who never had any issues connecting to the API through those apps. Recently I finished one of the apps on the iOS platform and it got rejected because Apple couldn't get it to load any content, or it would get stuck on loading without ever returning anything (after we implemented a loading progress animation). After a lot of messaging between me and Apple's review team, they ended up accepting my app to be passed through review even though they never got it to work (or so I believe, they just said they would re-review it and it suddenly got approved after 7 rejects). None of my friends, family or users ever experienced any issues like this on either Android or iOS.
A good friend of mine who did most of the work on the API is also from the USA, which makes me doubt it's a location problem.
I must note that pretty much 99.99% of my users are Dutch and all my projects are build for Dutch users.
Does anyone have experience or ideas in this field? I'm about to publish an update for the already published app and I'm afraid they will reject it because of the same issue.
The exact message I got at first was:
Specifically, upon launch we found that the app failed to load any content.
Changing the API calls to be over HTTPS seems to have fixed the issue, Apple now has access to my API through all my apps.
I have implemented the requestPasswordResetForEmailInBackground code to my app (xcode 7 using swift) for a login-screen. I used several tutorials, but I'm having the following error:
"Internal server error."} (Code: 1, Version: 1.12.0).
I'm wondering if more people have seen this problem, because the site of Parse states that this is a problem we can't solve.
Thanks.
This feature is not available on Parse Server. The team is working on implementing it but has not given a timeframe (yet) on a release. I you have an app in production and really want to get a mail service out now, check out services, like Mailgun. I expect that, when the Parse team adds the mail service, it will be a lot better than what was offered on the "old Parse."