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.

Sign up for GitHub

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

Jump to bottom

timestampsInSnapshots error when adding the useTimestampsInSnapshots prop #39

Open
KennethAshley opened this issue Feb 7, 2019 · 0 comments
Open

timestampsInSnapshots error when adding the useTimestampsInSnapshots prop #39

KennethAshley opened this issue Feb 7, 2019 · 0 comments

Comments

@KennethAshley
Copy link

  • react-firestore ^0.10.3

When adding the useTimestampsInSnapshots prop to the FirestoreProvider I receive the following error:

image

This seems as though its just a warning so i'm not sure why it looks like an error.

Thanks for all your hard work!
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
80b4010 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
cecf2f7 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
@tomsun tomsun mentioned this issue Mar 4, 2019
Merged
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
6eb5e1e 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
ec64eb7 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
5847866 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 4, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
2103896 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
tomsun added a commit to tomsun/react-firestore that referenced this issue Mar 11, 2019
@tomsun
Only set timestampsInSnapshots when explicitly requested via prop
2a44eea 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
green-arrow#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
green-arrow pushed a commit that referenced this issue Apr 6, 2019
@tomsun @green-arrow
fix(Firebase): Only set timestampsInSnapshots when explicitly set (#42)
e75e03d 
As of firebase@5.8.x timestampsInSnapshots is true implicitly
#39

Furthermore: calling settings() multiple times is not supported.
If your app interacts with Firestore prior to using <FirestoreProvider>,
FirestoreProvider's settings() call will get you into trouble:

Uncaught FirebaseError: Firestore has already been started
and its settings can no longer be changed. You can only call settings()
before calling any other methods on a Firestore object
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KennethAshley