Is there a way track where the unhandled promise error has happened?

Ionic Framework ionic-v3
1

Is there a way to know where really this error has happened? All i get is a reference to the polyfill

"Error: Uncaught (in promise): false
02-27 22:28:06.047 32263 32263 I chromium:     at s (/build/polyfills.js:3:4211)
02-27 22:28:06.047 32263 32263 I chromium:     at s /build/polyfills.js:3:4034)
02-27 22:28:06.047 32263 32263 I chromium:     at /build/polyfills.js:3:4574
02-27 22:28:06.047 32263 32263 I chromium:     at t.invokeTask /build/polyfills.js:3:9723)
02-27 22:28:06.047 32263 32263 I chromium:     at Object.onInvokeTask (/build/main.js:42519:37)
02-27 22:28:06.047 32263 32263 I chromium:     at t.invokeTask (/build/polyfills.js:3:9659)
02-27 22:28:06.047 32263 32263 I chromium:     at e.runTask (/build/polyfills.js:3:7083)
02-27 22:28:06.047 32263 32263 I chromium:     at i (/build/polyfills.js:3:3671)", source: /__ion-dev-server/ion-dev.js?v=1.1.4 (156)
2

Chrome’s Developer Tools have a “Pause on Caught Exceptions” checkbox that might be of service.

1 Like
3

but still, for some reason, i’ve only polifylls.js and main.js: the exception location does not get translated to the original source

4

This is a dev build, not prod, right? Do you have things that look like src/pages/foo/foo.ts underneath the outline view of the Sources tab?

5

nope, running: ionic run -l -c -s android --device
it only happens on my famous super slow zenfone2

6

Hmm. I’ve never used ionic run, I always just build .apks and deploy them via adb. Is it possible you’re banging into #10194?

7

wooow another bug! :stuck_out_tongue: I already added .catch(logErrors) to every .dismiss() of all my LoadingController… will look also into this one :slight_smile: and maybe i will try without “live reload” maybe its some kind of issue with it

8

ok it only happens on the phone when running live reload… it must be some nasty bug, not reproducible with the browser or the emulator

1 Like
9

Thanks for reporting back, and sorry I couldn’t help fix it.

1 Like
10

closed - won’t fix - not a bug :stuck_out_tongue:

11

ok solved, i just added the catch to the navController.pop()
when turning back i was reloading a google map and that’s slow because of many markers
but for some reason the catch never triggers, so basically there is no real error!
:frowning:
It has something to do with transistions and how them intereact with the IonViewDidEnter function.

12

You might want to open an issue, because a skim of this monster indicates that this whole ball of wax is believed fixed by Ionic as of 2.0.0.

1 Like
13

Here we go: https://github.com/driftyco/ionic/issues/10588

1 Like