mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #1849] Uncaught FirebaseError: Firebase: No Firebase App '[DEFAULT]' has been created - call Firebase App.initializeApp() #591
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#591
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sawa-ko on GitHub (Oct 3, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1849
Describe the bug
Apparently it is an error with the firebase configuration, I don't know if this has anything to do with it but I think it is the reason why the request history is not always complete, there are always missing entries.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No console errors on firebase.
Screenshots

Desktop (please complete the following information):
Additional context
I do not know if this is the case with other browsers.
@liyasthomas commented on GitHub (Oct 3, 2021):
Hi @kaname-png, thanks for reporting this issue. We're aware of this error - but it doesn't seems to have any effect on the app's functionalities. If you think "History entries" aren't working properly - please mention how to reproduce that particular behaviour and we'll take a look into it.
Regarding this error - it seems like a race condition caused while initiating Firebase App configuration. Hopefully it'll be resolved in latest dependencies bump.
@sawa-ko commented on GitHub (Oct 4, 2021):
Hi @liyasthomas
Reply to the topic about the missing items from the request history, I do nothing, they just disappear, but there is something that does appear, the message appears that if I want to confirm that I want to synchronize the history of repetitions, after that items disappear from the history, to ask me the same thing again some time later and the same thing happens. Taking into account that I have not deleted cache, cookies or closed session when making new requests.
@liyasthomas commented on GitHub (Oct 4, 2021):
I am afraid I didn't fully understand what you mean by "I want to synchronize the history of repetitions". Please provide steps to reproduce this issue or a screenshot would be helpful.
Btw, if you turn off Syncing History from the Settings page, deleting History entries won't affect the cloud sync, also no new entries will be added to the cloud, instead, all entries will be only available in local storage only.
@sawa-ko commented on GitHub (Oct 4, 2021):
I mean I get a notification saying that message. "Do you want to synchronize the request history?"
@liyasthomas commented on GitHub (Oct 4, 2021):
This happens when your local storage has entries that don't match with that of the last synced cloud history.
Choose yes to upload the latest (un-synced) local changes to the cloud, once it completes sync - you won't be asked again to sync history.
@sawa-ko commented on GitHub (Oct 4, 2021):
That's the problem, when I hit "yes" everything seems to be fine, but then hours later the message reappears and then some history items disappear.
@liyasthomas commented on GitHub (Oct 4, 2021):
Have your History entries set to be synced in the Settings page?
@sawa-ko commented on GitHub (Oct 4, 2021):
Yes, I always have it that way, that's why I wonder why hoppscotch asks me that question again if I supposedly already have it activated.
@liyasthomas commented on GitHub (Oct 4, 2021):
Noted. We'll look into this.