It all the sudden stopped working last week, and it's no longer listed on data.healthcare.gov page.
Is it a technical error, or a policy issue that you no longer provide this data? Or is there a new link and can you please provide it?
For example:
https://data.healthcare.gov/resource/itgc-a3uf.json?state=IL&county=COOK
I have valid API key, so that's not an issue with credential and access.
It does appear that the data set has been removed or hidden from public view. However, I would recommend that you contact the maintainers for advice.
Related
I have a sidebar that is opened using an onLoad() trigger in Google sheets. Up until about an hour ago, it was working fine. Now, it opens and is completely blank. In the console, the head and body tags were completely empty and I had the following error messages:
I've tried disabling some extensions that could've been causing problems, but that hasn't seemed to do anything.
Does anyone know what could be going on? Any insight is appreciated
I'm writing this answer as a community wiki, since the issue was resolved from the comments section, in order to provide a proper response to the question.
It would also be used to clarify the comment. If you are experiencing this particular error or alert and you considered it is a bug. You should be able to follow the link to share the logs and report the issue
https://issuetracker.google.com/issues
You can use the keyword or search by:
refused to load script it violates the following
From different reviews of this error, it is generally due to the browser or the local host of the application. You can find some other example and issue reporting options over the references section.
Reference
https://bugs.chromium.org/p/chromium/issues/detail?id=1054624
https://bugs.chromium.org/p/chromium/issues/detail?id=1220994
I've been working for Google Apps Script for a while. I have many programs where I've authorized Gmail, Docs, Drive, Calendar, UI, etc... I'm just now adding Contacts...but it is not working
My first step is to Contacts.createContact(), but this is failing no matter what I've done. Documentation says that the "https://www.google.com/m8/feeds" scope is needed. I have that. I also added "https://www.googleapis.com/auth/contacts"
I've turned on API in the Admin for the Workspace. I've made the app the trusted. I've removed authorization for everything and readded. The odd thing is that in giving authorization when it lists everything asking for permissions, under contacts is says "Contacts: See, edit, delete..." It specifically does not say "Create".
I've followed all of the documentation I can find for Google and turned on everything and given permissions to everything. Still, I cannot createContact.
This worked for me:
function createADoggieContact() {
ContactsApp.createContact("Cooper","Dachshund","Cooper#cooper.com");
}
createContact
I didn't post code, because it was not a code problem. After hours and hours of trial and error, I found the problem. This is not documented anywhere that I could find in Google. Google support couldn't figure it out as well. I've left feedback that they will hopefully take.
I hope this helps someone else who is running into this problem. It was caused by the fact that the very first method I was trying executing in order to bring up the authorization was the ContactsApp.createContact(). Calling this first and in order to bring authorization appears to not be allowed or something they will permit as the very first operation. Don't know if this is security related.
I changed my code instead to use ContactsApp.getContact() to a known and existing contact. That code worked!!! Authorization popped up. Granted. Got the info. I then changed the code back to the .createContact()....it all worked fine.
This appears to only be when you are first trying to use the ContactApp and authorize it for the very first time in your code. Perhaps it was just a glitch in my account, but the same glitch could happen for someone else.
We have an web app that we add MS Teams as a tab. It uses AAD for logging in and the SAML2.0 protocol. When setting it up within our own company, it worked without a hitch, but when we tried to add it to the ecosystem of one of our clients, it fails during the login redirect with: "login.microsoftonline.com not allowed to be embedded". We believe the issue is coming from the X-FRAME-Options: DENY
screenshot
But it's working within our own ecosystem. I asked our client if they have any kind of custom safe-guards in place that might be driving this behaviour but the answer came back negative. Does anyone know where this option could be added in/ removed from? Browsing the net says that that's not something that can be removed, but it definitely is not present in our own setup.
Thanks in advance
Normal web SAML cannot work by definition in an iframe in Teams tab, it has to follow Teams tab supported auth as of now. Giving few reference that might help: Have a look at Single sign-on support for tabs - Teams | Microsoft Docs and Teams SSO sample.
Please refer this question for discussion - How to deal with a redirect in Microsoft Teams Tab
We ported our site to Google maps, but we get different errors when loading a map using the JavaScript Maps API (v3 of course). Other times the map loads correctly. The two most prominent errors are:
"Google has disabled use of the Maps API for this application. See the
Terms of Service for more information
http://www.google.com/intl/en_US/help/terms_maps.html." (JS Alert)
And:
"This site has exceeded its daily quota for maps. If you are the
creator of this site, please visit the documentation to learn more."
(this is a DOM overlay)
Live minimal example:
This code is not yet live but there's a minimal example here: http://mappat.com/maptest.php. It is simply Google's own Hello World example with our key filled in and even that gives problems.
Network traffic inspection:
I noticed the first error is shown when 'AuthenticationService.Authenticate' fails (returns [0,5,0]), the second when 'QuotaService.recordEvent' returns [0,null,0]. These are remote calls from within the SDK and I don't know if these details are relevant.
What we tried:
Billing is enabled by the way and we stay way below our quota limits. I tried a lot of things already, new key, waiting a few days, turning the Maps API off and on again in the console, etc. I filled in the allowed referrers but also left it open to allow others. No difference.
I don't dare to start a new project in de dev console because this whole thing started when I did actually just that because I had (different) problems with the server-key. That server part is now working flawlessly btw, kind of ironically.
[Edit: I just tried to leave out the API key when loading the JS maps file, which, fingers crossed, seems to work. But now the server-side calls to places/searchtext start to give random "The provided API key is expired." errors, again (same reason we created the new project). Coincidence? Also, I don't like this option, especially with regards to the future (reaching 25k, going beyond and going Business Account)].
So, I'm stuck. Hence my first SO question ever. Could it be that we are blacklisted? Perhaps because of the duplicate project? Is there a way to find that out and/or to get us 'reset'? Or am I simply overlooking something?
Any help is appreciated because until we solve this, this is a deal-breaker.
Sidenote: I also filed a bug report because I think giving random errors on itself is not expected behaviour. It's up to the dev team to decide if they agree. If not, we still have a problem, hence this SO question.
I think you have a syntax error in your php var dump:
<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?key=AIzaSyDYuWR5wqux1_iTmfIWPveheIOr5PhqjEs&?>sensor=FALSE&language=en">
</script>
you have ?> just before sensor
This issue magically disappeared after a week or so.
I didn't get any response from Google, but they may have change/reset something behind the scenes, of course. The bug is still marked 'new', by the way.
My advice to others having this issue is to first check some basic things, since the individual errors I got could also result from actual things you're doing wrong (ie mistake in allowed-referers). If all seems okay after triple checking, just remove the API key from the request, test along like that for a while and retry in a couple of days.
Has anybody found that the Obout Calendar control has stopped working in the latest Google Chrome update (17.0.963.56 m)?
We have an active licence with Obout, but following two emails and two telephone calls we have yet to receive a response or even an acknowledgement that an issue exists. Anyone using the latest version of Chrome can replicate the issue on the published examples:
http://www.obout.com/calendar/calendar_live_styles.aspx?style=default
Try paging through the months a few times and you should eventually see the following error:
Uncaught TypeError: this is not a Date object.
If anybody has a workaround or can shed light on the matter I would love to hear from you. At the moment it has crippled our live site and we are frantically looking for a solution.
The new version of the Obout Calendar has been released today:
http://www.obout.com/calendar/changelog.aspx
It contains the fix for the latest Google Chrome.
I have seen the problem and am also waiting to hear back from Obout. Have sent 3 emails and as yet nothing. I have only just bought the suite this week! and am hoping that this difficulty in getting a response is just my lack of using the correct channels.
OK Problem Solved!...Obout have just emailed me a revised DLL. Happy to forward this if anybody requires.