Do I need to worry about these 2 errors? (warning?)


#1

Text:
JS: Angular 2 is running in the development mode. Call enableProdMode() to enable the production mode.
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.callJSMethodNative(Native Method)
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1022)
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.callJSMethodImpl(Runtime.java:907)
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.callJSMethod(Runtime.java:895)
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.callJSMethod(Runtime.java:879)
01-09 06:24:25.802 5659 5659 W ExifInterface: at com.tns.Runtime.callJSMethod(Runtime.java:871)
JS: Connected to API.
JS: clipToBounds with value false is not supported on Android. You can use this.android.getParent().setClipChildren(false) as an alternative


#2

So far, the best I can tell from looking through the Angular 2 source code is that this setting (“dev mode”) controls whether or not long stack traces are enabled. I found that in @angular/core/src/application_ref.js. The isDevMode() method is exported, so other modules may reference this method to change their behavior, too–I haven’t gone through the entirety of the Angular 2 source code, yet, so I’m not sure if this is referenced anywhere else.

In short, my suggestion is to call enableProdMode() in your builds that you intend to be publicly available. It is generally a good practice not to show your users too much about your source code, which a long stack trace could provide.

I’m not sure about the second error you mentioned.