Imagine we have foo$ and bar$ and both of them are BehaviorSubjects.

I have a bug in angular that sometimes in some cases foo$.subscribe(bar$) works fine, in most casses actually.

But sometimes I have a bug and its not working until I do foo$.subscribe(foo => bar$.next(foo)), and even worse it seems like it works the first time and then the second time it dose not work.

I experienced this bug sometimes but still rearly. Not sure even how to make a proper minimal reproduction. I would like to understand what makes this causing the bug? And is the angular team aware of it? I didn't see anywhere so far anyone posting about it.

---

Have checked if it solves anything by removing zonejs and it dose not.

Imagine we have foo$ and bar$ and both of them are BehaviorSubjects.

I have a bug in angular that sometimes in some cases foo$.subscribe(bar$) works fine, in most casses actually.

But sometimes I have a bug and its not working until I do foo$.subscribe(foo => bar$.next(foo)), and even worse it seems like it works the first time and then the second time it dose not work.

I experienced this bug sometimes but still rearly. Not sure even how to make a proper minimal reproduction. I would like to understand what makes this causing the bug? And is the angular team aware of it? I didn't see anywhere so far anyone posting about it.

---

Have checked if it solves anything by removing zonejs and it dose not.

• angular
• rxjs
• observable
• subject

Share Improve this question Follow asked Mar 20 at 12:34 Muhamed KarajicMuhamed Karajic 8111 silver badge77 bronze badges 4

• 3 Hi, without a repro this is very hard to investigate. – Matthieu Riegler Commented Mar 20 at 12:37
• I tougth maybe its a very very general issue which I'm just not aware of. I'll try to make a repo. – Muhamed Karajic Commented Mar 20 at 12:38
• @MatthieuRiegler here is a minimal repo stackblitz/edit/… You can see in the console hello... is logged once when doing it the first way, and doing it the second way its logged as many times as you click the button. – Muhamed Karajic Commented Mar 20 at 13:10
• After looking it however myself I see the issue is actully in the this.onDestroy$.next(); call. but still strange that it works fine when changing the line of code. – Muhamed Karajic Commented Mar 20 at 13:12

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 2

When you do this.foo$.pipe(takeUntil(this.onDestroy$)).subscribe(this.bar$);

The bar$ subject actually completes when the foo$ subscription completes (because if the takeUntil).

This is become subscribe(this.bar$) implies

foo$.subscribe({
  next: value => bar$.next(value),
  error: error => bar$.error(error),
  complete: () => bar$plete(),
})