When I launch my application on the mobile chrome simulator or even on a smartphone (chrome or safari) I have this error, not on the desktop:
Error: Zone.js has detected that ZoneAwarePromise `(window|global).Promise` has been overwritten.
Most likely cause is that a Promise polyfill has been loaded after Zone.js (Polyfilling Promise api is not necessary when zone.js is loaded. If you must load one, do so before loading zone.js.)
at Function.Zone.assertZonePatched (zone.js:68)
at new NgZone (core.js:40989)
at getNgZone (core.js:42356)
at PlatformRef.bootstrapModuleFactory (core.js:42169)
at core.js:42250
at es.promise.js:114
Related
I'm not sure what changed in Chrome but the Graphiql GUI tool is not loading.
In Firefox and Safari it works just fine. I have disabled all Chrome extensions, restarted Chrome, and restarted my Mac. The error persists. How do I debug this?
In graphql-workspace.min.js it errors on:
this.state.config.state.proxy || this.state.config.state.headers.forEach(function(e) {
Error:
graphiql-workspace.min.js:1 Uncaught TypeError: Cannot read property 'forEach' of undefined
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at performInitialMount (react-dom.min.js:13)
at p.mountComponent (react-dom.min.js:13)
at Object.mountComponent (react-dom.min.js:14)
at mountChildren (react-dom.min.js:14)
at m._createInitialChildren (react-dom.min.js:13)
at mountComponent (react-dom.min.js:13)
Here is a picture of it working in Firefox:
Not sure why headers is undefined.
I am using:
Elixir, Phoenix, Absinthe, Absinth-Plug, Vue, Vue-Apollo, apollo-boost, graphql,
Since the GUI appears to be loading from a CDN I'm wondering if that's a direction I should explore. However the network tab in chrome shows no failures.
It seems that much of the activity/history of using Graphiql is saved to localStorage. I'm not sure what broke the history but I inspected the broken config in the console with a few breakpoints. This lead me to discover that localStorage was being used. I then cleared a lot of key/values in there and my Graphiql rendered successfully.
I am trying to solve a mystery:
A page from a React web app can be loaded in Safari on iOS
That page can be loaded in Chrome on iOS if you choose "Request Desktop Site"
That page is blank when attempting to load it in Chrome on iOS if you go with the default "Request Mobile Site"
The page works fine in desktop browsers
I have taken steps to enforce a timeout on the server side, in case there is a connection that is hanging. But when I consult the logs, the requests complete quickly without any of the usual follow-on activity. My guess is that there is a JavaScript error of some kind that is causing the React app to bail.
What is a good next step that might be helpful in troubleshooting this issue?
ETA: Added new information that confirms the requests are making it from Chrome to the Golang server, as expected.
I think what's going on is that the "Request Mobile Site" mode falls over when there's a large JavaScript bundle, whereas the "Request Desktop Site" doesn't for some reason.
For anyone who runs into this situation, something that worked for me was to decrease the amount of JavaScript that the iOS Chrome app has to load, e.g., using code splitting, user agent sniffing and redirection to a less memory-intensive page in the case of iOS Chrome. After doing this, things worked fine. I'm guessing that less memory is available to apps running in the "Request Mobile Site" mode than in the "Request Desktop Site" mode.
I cannot get appcache to work on the iPad and iPhone.
At first I thought the problem was that it was called manifest.appcache so I changed it to appcache.manifest because the Safari documentation specified that it should end in .manifest
didnt work.
When logging appcache events on a mac mini while debugging safari on the ipad I see
checking
error
But when I debug safari on the mac mini i see
checking
noupdate
It works as expected on every other non ios device i have tested and on all 5 browsers on my pc.
I have confirmed that the doc type returned is text/cache-manifest
Here is what the manifest looks like from one of the pages
https://mysite.com/Mobile/appcache.manifest?page=MyPage.aspx
CACHE MANIFEST
CACHE:
MyPage.aspx
Mobile.jpg
js/vendor/jquery/jquery-1.7.1.min.js
# Resources that require the user to be online.
NETWORK:
/Mobile/appcache.manifest?page=MyPage.aspx
*
Also I do not see a request in the Safari debugger timeline profiler to the manifest file
I'm getting the "Aw Snap" message consistently in Chrome when performing the following:
Load a page that displays a silverlight rendering
Click on a button that fires off a fancybox containing an iFrame that contains the same Silverlight rendering
Close the fancybox
Receive the dreaded "Aw Snap" message
Reload page and page loads up again
Notes:
This does not happen in IE
This does not happen in Firefox
When I go to chrome://crashes/ there is no record of the crash
Chrome Version: 24.0.1312.57
Silverlight Version: Silverlight 5 (5.1.10411.0)
Searching through Google's Chrome issue board yielded very little and any issue reported that was similar was either years old or did not have a response. Hoping that someone has encountered the same problem and has a workaround.
I get this error message when using Google Maps API v3 (release channel), trying to pan around the map and I have my console window open:
Uncaught TypeError: Object #<HTMLDivElement> has no method 'setCapture'
I know that closing the console and reloading the page solves the error, but this is very inconvenient as I'm developing a map app at the moment and I need to test it and read debug messages.
Other browsers (Safari 6 for instance) don't show this error and panning works fine, console window open or not.
I'm using Chrome 21.0.1180.89.
I had the same problem, when i had left the settings for useragent override to Internet Explorer, in the developer tools settings window.
Unchecking the override solved the issue.