Fix #1007 - Call save-device-info method at application launch #1008
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @cagryInside! How about putting the timestamp as a field too so we can query on it? |
cagryInside
force-pushed
the
issue1007new
branch
from
30aa695 to
627e111
Compare
@barbeau good idea. Just added and updated the commit:
|
|
Thanks @cagryInside! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Calling the
saveDeviceInfomethod in the app launch. Previously, we were calling this method on every transition event and it was causing duplicate ~device-information` records on Firebase. Now, we only call once when the app is started. The new data looks like this on Firebase: