Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

5.5.3 EmptyError: no elements in sequence

See original GitHub issue

RxJS version: 5.5.3

Code to reproduce: since my update to 5.5.3 i’m getting errors in otherwise perfectly fine running angular 5.x application

this is the error i’m getting this morning

all was working perfectly prior to 5.5.3

difficult for me to trap what the reason could be thanks

Error: Uncaught (in promise): EmptyError: no elements in sequence
EmptyError: no elements in sequence
    at new EmptyError (EmptyError.js:27)
    at FirstSubscriber._complete (first.js:154)
    at FirstSubscriber.Subscriber.complete (Subscriber.js:121)
    at MergeMapSubscriber._complete (mergeMap.js:144)
    at MergeMapSubscriber.Subscriber.complete (Subscriber.js:121)
    at MapSubscriber.Subscriber._complete (Subscriber.js:139)
    at MapSubscriber.Subscriber.complete (Subscriber.js:121)
    at EmptyObservable._subscribe (EmptyObservable.js:82)
    at EmptyObservable.Observable._trySubscribe (Observable.js:173)
    at EmptyObservable.Observable.subscribe (Observable.js:161)
    at new EmptyError (EmptyError.js:27)
    at FirstSubscriber._complete (first.js:154)
    at FirstSubscriber.Subscriber.complete (Subscriber.js:121)
    at MergeMapSubscriber._complete (mergeMap.js:144)
    at MergeMapSubscriber.Subscriber.complete (Subscriber.js:121)
    at MapSubscriber.Subscriber._complete (Subscriber.js:139)
    at MapSubscriber.Subscriber.complete (Subscriber.js:121)
    at EmptyObservable._subscribe (EmptyObservable.js:82)
    at EmptyObservable.Observable._trySubscribe (Observable.js:173)
    at EmptyObservable.Observable.subscribe (Observable.js:161)
    at AppErrorHandler.handleError (app.exception.ts:47)
    at Object.next (core.js:5377)
    at SafeSubscriber.schedulerFn [as _next] (core.js:4223)
    at SafeSubscriber.__tryOrUnsub (Subscriber.js:246)
    at SafeSubscriber.next (Subscriber.js:193)
    at Subscriber._next (Subscriber.js:132)
    at Subscriber.next (Subscriber.js:96)
    at EventEmitter.Subject.next (Subject.js:63)
    at EventEmitter.emit (core.js:4203)
    at core.js:4652

Issue Analytics

State:
Created 6 years ago
Reactions:42
Comments:30 (2 by maintainers)

Top GitHub Comments

16reactions

dhabierrecommented, Dec 3, 2017

This can help (using rxjs 5.5.3 - “rxjs”: “^5.5.2”)

Bug with empty path:

const routes: Routes = [ { path: “”, component: SynthesisComponent }, { path: “home”, component: SynthesisComponent }, { path: “about”, component: AboutComponent }, … ];

Ok when using pathMatch: ‘full’:

const routes: Routes = [ { pathMatch: ‘full’, path: “”, component: SynthesisComponent }, { pathMatch: ‘full’, path: “home”, component: SynthesisComponent }, { pathMatch: ‘full’, path: “about”, component: AboutComponent }, … ];

From https://github.com/angular/angular-cli/issues/8724 (nawnitraman)

16reactions

Citocommented, Dec 2, 2017

Me too with an Angular 5.0.5 project. After downgrading rxjs to 5.5.2 the problem went away.