Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

this.scheduler.notify is not a function in Angular Fire with Angular 19.1.4 #3618

Open
riya-amemiya opened this issue Feb 6, 2025 · 8 comments

Comments

@riya-amemiya
Copy link

riya-amemiya commented Feb 6, 2025

After updating Angular and related packages, getting error "this.scheduler.notify is not a function" when using Angular Fire. Need help identifying exact reproduction steps.

Updated to (Not Working)

  • @angular/core: 19.1.4
  • @angular/fire: 19.0.0
  • zone.js: 0.15.0

Previously Working with

  • @angular/core: 18.2.2
  • @angular/fire: 18.0.1
  • zone.js: 0.14.10

Error Stack

this.scheduler.notify is not a function
    at core.mjs:6165:28
    at cleanupTask (rxjs-interop.mjs:281:17)
    at Object.next (rxjs-interop.mjs:287:21)
    at ConsumerObserver.next (Subscriber.js:91:33)
    at SafeSubscriber._next (Subscriber.js:60:26)
    at SafeSubscriber.next (Subscriber.js:31:18)
    at observeOn.js:6:130
    at AsyncAction.<anonymous> (executeSchedule.js:3:9)
    at angular-fire.mjs:72:26
    at _ZoneDelegate.invoke (zone.js:369:28)

Question
Can anyone help identify the exact steps to reproduce this error? What operations/methods trigger this specific error?

  • Error occurs immediately on the top page without any user interaction
  • Application is running with SSR enabled
  • Error only appears on client-side, not during SSR

core.mjs:6165:28
cleanupTask (rxjs-interop.mjs:281:17)
SafeSubscriber.next (Subscriber.js:31:18)
executeSchedule.js:3:9
angular-fire.mjs:72:26

@google-oss-bot
Copy link

This issue does not seem to follow the issue template. Make sure you provide all the required information.

@riya-amemiya
Copy link
Author

I'll share a minimal reproduction repository once I can create one

@LanderBeeuwsaert
Copy link

@riya-amemiya you're not the only one
#3592
it seems to have to do with Auth for us, but I was not able to easily create a minimal repro.
We're not using SSR

@LanderBeeuwsaert
Copy link

@riya-amemiya if you would be able to make a minimal repro that would be great. I've tried but I haven't succeeded. But also the angular team requested a reproduction to be able to look into fixing this.

@riya-amemiya
Copy link
Author

@LanderBeeuwsaert

Thank you for sharing the information. While I'm not sure if I can reproduce it, I will do my best to help ensure that everyone, including myself, can update to Angular v19 without any issues.

@DougieBoi227
Copy link

I'm getting the same issue. What's weird is I don't get this error with local dev env but I do when deploy to prod (firebase hosting)

@LanderBeeuwsaert
Copy link

I've been able to make a minimal reproduction:
https://github.com/LanderBeeuwsaert/notify-scheduler-issue2

@riya-amemiya
Copy link
Author

Thank you for creating a minimal reproduction repository!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants