-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get property 'isProxied' of undefined or null reference (like #1661) #2774
Comments
We've been seeing this error too but on @stencil/core: 2.3.0 (we're not using the pwa toolkit). A vast majority of these errors seem to be coming from safari users but intermittently. |
I'm getting this error with my published components when trying to load from unpkg. It's very really annoying to have a broken library published and clients waiting for a new version while I have no idea how to fix it. BTW I also have this error in Chrome. |
I also discovered, that the generated build and documentation is broken, not matching or missleading. In this documentation https://stenciljs.com/docs/distribution the script tag points to There are two mistakes in this.
Here you can check my broken published bundle https://www.jsdelivr.com/package/npm/@footage.one/search-components?path=dist |
I've narrowed down this issue to Safari iOS version 12. The only way to fix this is to run a babel rollup plugin (which breaks tests) |
Getting this issue in Chrome while using a Cypress-Test 🤔 |
Hey folks! Could you please update to the latest version and help me ID if this is intermittent or not? With sourcemaps now shipped in v2.9.0, I hope that folks hitting this can use them to determine where precisely this occurs and why. |
I'm still seeing this issue on v2.12.0, intermittently and mostly (though not exclusively) with mobile Safari users. Up to and including Safari 15. |
Same issue but with Chrome and Testcafe |
I've got this issue on iOS 15 as well. Has anybody found a workaround or a fix ? |
I am also interested in a fix/workaround. Using our application in Safari is blocked by this issue. Interestingly the application shows up after reloading the page. So I am wondering about an ESM loading issue in WebKit (see below). After enabling source mapping, I can see that the affected code is this one. The implementation dynamic module loading in Safari might have an issue, this line does not seem to work in Safari. Wondering if is related to this WebKit issue (Race condition makes ESM modules to evaluate twice)? The issue is still marked as open, but I could not reproduce it with Safari Version 15.3 (17612.4.9.1.5) (Monterey 12.2). Does anyone have more information? Any suggestions are appreciated, thank you. |
Hello all, We have the same problem in the project that i am part of. In our case we have the following scenario: GIVEN the application with a valida user session This seems to be releated to an import module. If that component is previously loaded before the session expiration, this is not a problem, and we can use the component even if the session is expired. Any thoughts on this? Kind regards |
Hello all, we faced this issue too and did a quickfix which works well. if (navigator.userAgent.indexOf('Safari') > -1) {
window.onunhandledrejection = event => {
if (event.reason.message.includes('isProxied')) {
location.reload();
}
};
} How it works: Maybe this help somebody else to go on. Best |
I am also getting error when ever there is new build, can we get some solution or workaround. "@stencil/core": "^2.6.0", "build": "stencil build --prod --no-cache && node ./src/tasks/after.build.js", p-e82b5571.system.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'isProxied')
|
Hey there 👋 I’m having trouble reproducing this on my end with the latest version of Stencil (v4). If anyone is willing/able, would you be able to create a minimal reproduction case for the team? If not, I completely understand. Again, I apologize for the lack of response here |
Thanks for the issue! This issue has been labeled as Please reproduce this issue in an Stencil starter component library and provide a way for us to access it (GitHub repo, StackBlitz, etc). Without a reliable code reproduction, it is unlikely we will be able to resolve the issue, leading to it being closed. If you have already provided a code snippet and are seeing this message, it is likely that the code snippet was not enough for our team to reproduce the issue. For a guide on how to create a good reproduction, see our Contributing Guide. |
Thanks for the issue! This issue is being closed due to inactivity. If this is still an issue with the latest version of Stencil, please create a new issue and ensure the template is fully filled out. Thank you for using Stencil! |
Stencil version:
@stencil/[email protected]
@Stencil/router 1.0.1
I'm submitting a:
[ x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/
Current behavior:
Probably related to #1516. stencil build --es5 when using Ionic components builds, but then when served produces the error in the console: "Unhandled promise rejection TypeError: Unable to get property 'isProxied' of undefined or null reference"
Expected behavior:
For the PWA toolkit to load in both dev and prod builds.
Steps to reproduce:
The following code is causing the issue, copypasted from the pwa toolkit. Without it, the page renders fine. Please note I am using lite-server, not the Stencil dev server, because I cannot get that to work right now (reported under separate issue).
Related code:
Other information:
Original issue watchers:
@Aaron-Sterling @d0whc3r @meriturva @rieshy @warapitiya @JimGaleForce @havard024 @ali-master @andersonfvrj @pwespi @dutscher
The text was updated successfully, but these errors were encountered: