Is there a problem with Polydev?
I develop an app using Polymer, and since Friday I have this error "Cannot read property '_bound' of null" for every paper-button action.
Before the error didn't popped up, and the actions worked fine.
Related
Here is the issue
error TS2416: Property 'supportsDOMEvents' in type 'ɵangular_packages_platform_browser_p
latform_browser_o' is not assignable to the same property in base type 'ɵDomAdapter'.
As #DrTeeth already mentioned, it's hard to help w/o any further infos.
But I've had a similar problem and want to share what had helped for me: This was a simple inconsistency of my dependencies. I', using a 3rd party Angular Component Library which was incompatible with the newer (Ivy-enabled) version, after I updated Angular itself. For me, the error message had some details about the package in question and after updating it, too, everything worked fine.
Recently iam trying to update my angular project from 8 to 9. While updating i also updated wijmo from wijmo/wijmo to #grapecity/wijmo package as it supports IVY.
But after the completing the upgradation, i can able to compile the application but i am getting the following error at run time
global-error-handler.service.ts:43 Error: Uncaught (in promise): TypeError: (0 , t[n]) is not a function
TypeError: (0 , t[n]) is not a function
at backend.js:61
at Reflect.<anonymous> (backend.js:61)
at push../node_modules/#grapecity/wijmo.angular2.grid.detail/__ivy_ngcc__/index.js.__decorate (index.js:28)
at index.js:53
at Object../node_modules/#grapecity/wijmo.angular2.grid.detail/__ivy_ngcc__/index.js (index.js:53)
at __webpack_require__ (bootstrap:84)
I'd like to get some more info about this error. The quick thing to check is property initialization order. In Ivy, the properties are interpreted as they are specified in markup (previously wijmo controlled how they were interpreted). So you can break components by setting certain properties before others.
For example, if I tried to set the selectedIndex on a combobox BEFORE I set the data source, then the app would break at runtime because there are no items in the list to select yet.
More info here: https://www.grapecity.com/wijmo/docs/GettingStarted/Angular-Components#property-initialization-order-in-angular-9-ivy-and-higher
The next thing to check is component decorators (if you are inheriting our components). There are some breaking changes in decorators in Ivy.
For example, you might need to add {descendants: true} to ContentChildren queries.
Or you might need to add an #Injectable decorator to your class.
You can read more about breaking changes in Ivy and how to fix them here: https://angular.io/guide/ivy-compatibility-examples
But please feel free to contact us to work directly: wijmoexperts#grapecity.com
According to this and this, it should be easy to have Android Studio break on an uncaught exception. However, whatever I try, I seem not to get it working.
I set the "Class Filter" on my Activity, but the app just crashes on an uncaught exception, no breakpoint triggered.
Are you sure that the exception being raised is from the class that you've specified in the class filter?
Try configuring to break on all exceptions without the class filter enabled to validate that it's actually the specified class raising the exception: https://stackoverflow.com/a/28862538/3063884
I was unable to get the debugger to stop for anything until I clicked on the app folder in the project view (one level below root). Clicking on the Root folder of the project didn't work either.
I'm new to polymer and I started to follow this easy first tutorial on the official website
http://www.polymer-project.org/docs/start/tutorial/step-1.html
all was very easy but nothing was working. Or better, I have only one problem. When I tap on the top menu ("All or favourite") nothing changes and I get this error on console
Uncaught TypeError: undefined is not a function Element.js:104
Selected: favorites (index):65
Uncaught TypeError: undefined is not a function Element.js:104
Exception caught during observer callback: TypeError: undefined is not a function
at b.classList (http://127.0.0.1/polymer/components/platform/platform.js:13:20941)
at Polymer.selectedIndexChanged (data:text/javascript;base64,CgogIFBvbHltZXIoJ3BhcGVyLXRhYnMnLCB7CiAgICAKICA…cG9uZW50cy9wYXBlci10YWJzL3BhcGVyLXRhYnMuaHRtbC9wYXBlci10YWJzLmpzCg==:45:26)
at e.invokeMethod (http://127.0.0.1/polymer/components/polymer/polymer.js:12:10242)
at e.notifyPropertyChanges (http://127.0.0.1/polymer/components/polymer/polymer.js:12:9459)
at Object.Observer.report_ (http://127.0.0.1/polymer/components/platform/platform.js:12:12892)
at Object.createObject.check_ (http://127.0.0.1/polymer/components/platform/platform.js:12:18346)
at Object.global.Platform.performMicrotaskCheckpoint (http://127.0.0.1/polymer/components/platform/platform.js:12:13792)
at http://127.0.0.1/polymer/components/platform/platform.js:16:24471
at Object.c [as callback_] (http://127.0.0.1/polymer/components/platform/platform.js:15:9571)
at Array.c (http://127.0.0.1/polymer/components/platform/platform.js:12:27047)
I thought I did something wrong so I downloaded the example file but I have downloaded the source of the example and I still get the same errors.
Any help? =)
Thx everyone!
Some components in the tutorial repo were out of sync. If you pull the updated repo, these errors should go away.
Updating chrome to version 35 or use Chrome Beta
It errors on my linux box which has Chrome Version 34.0.1847.137.
It works on windows7 with Chrome 35.0.1916.153m
I had the same problem.This is the error report https://github.com/Polymer/polymer-tutorial/issues/3
And this is where you can find the answer
https://github.com/Polymer/polymer-tutorial
It worked for me :)
My flex project uses a small swc library. It runs under Flash Builder.
While running the application in debug mode I can see plenty of "TypeError: Error #1009: Cannot access a property or method of a null object reference." displayed in console.
But I have no extra information: which method or property caused the error, on which type, where, etc.
My flex app has an uncaught error mechanism, but no error is caught.
I tried to set compiler option "-debug" to true but no change occurred, logs are not more verbose.
I got the library sources and looked for an Error handling where this log would be written, but I found nothing.
Somebody already encountered such issue?