[SOLVED] Error: Handler with name 'u' already exists

help
3

Hi! I have the similar issue.
Today after updating Chrome to latest version I have an Error in browser’s console
"Exception in callback of async function: Error: Handler with name ‘hookWithOptions’ already exists."
and app doesn’t work!

4

What meteor version you use?

5

those project is on 1.2.1

I have found some older topics on stackowerflow related to this error
they say that this error is caused by multiple onBeforeAction in Iron Router
I just tryed to comment all onBeforeAction in my code, but it doesn’t change situation

6

This affect to me as well in meteor 1.3

7

same? affects one (or some) users, but not all?
you also have same console output in Chrome?

9

found this

10

yes, found this too
tryed to delete all onBeforeAction in order to see if they are involved, but nop…
seems like it is something new

11

We have the same issue. Our app broke for Chrome users… How annoying.

12

The title should be something like Meteor app crashed after chrome update.

13

Meteor really needs more practical way to debug production errors. Sourcemaps?

14

Try this : meteor update iron:middleware-stack

And your problem will definitely resolve.

21 Likes
15

started getting this in canary, nits is right iron:middleware-stack@1.1.0 does the trick.

16

I started seeing users get this issue as well starting on 5/25. Turns out that was the same day that Chrome released version 51.0.2704. Once I upgraded to the latest Chrome version on my own machine, the issue came up for me.

iron:middleware-stack@1.1.0 fixed the issue.

4 Likes
17

iron:middleware-stack@1.1.0 fixed the issue for me too, thanx!

1 Like
18

thanks everyone!
20 chars

19

omg, thanks everyone! worked like a charm!

1 Like
20

Thank s a lot. It worked for me

1 Like
21

+1 here, it worked for me too!

1 Like
22

+1 here. Thank you! Worked!

1 Like
23

+1 here. It’s working!