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

[Question] SnapshotError handler #71

Open
rborn opened this issue Mar 29, 2019 · 5 comments
Open

[Question] SnapshotError handler #71

rborn opened this issue Mar 29, 2019 · 5 comments

Comments

@rborn
Copy link

rborn commented Mar 29, 2019

Hi,

I see you handle the onSnapshotError case but it's just a warning.
Is there any way to actually do anything in case this event occurs ?

Thanks

@rborn rborn changed the title SnapshotError handler [Question] SnapshotError handler Mar 29, 2019
@damonmaria
Copy link
Contributor

@rborn I'm not an expert but I'm pretty sure Firebase handles any network errors internally. So you won't be getting 'timeout' or 'disconnected' errors through this. All I've seen so far are errors about missing indexes.

@rborn
Copy link
Author

rborn commented Apr 1, 2019

@damonmaria or permissions.
Would be good though to be able to handle at least the available errors

@IjzerenHein
Copy link
Owner

@rborn My experience is the same as @damonmaria, I've only seen that handler being triggered on misconfiguration issues.

@rborn What kind of error handling would you looking for, an overridable method on Document/Collection?

@rborn
Copy link
Author

rborn commented Apr 1, 2019

@IjzerenHein yeah, something like that.
Indeed I only have this issue when the configuration changes, and I'm thinking that if in the future we need to change the configuration then we should be able to handle this app side.

@damonmaria
Copy link
Contributor

My experience is they are only messages that you should see during development. Maybe being overridable would be useful in that during dev it's a console warning, but otherwise (like during testing or in production) it could be an error reported back / show stopper.

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

3 participants