You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser version: Mobile Safari. (Agent string "Mozilla/5.0 (iPad; CPU OS 13_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148")
Firebase SDK version: 7.16.0 (also present on 7.17.1 )
Firebase Product: firestore
[REQUIRED] Describe the problem
We have a multi page Cordova app which uses Firestore with persistence enabled. It issue happens when users navigate about a few pages and then put the app in the background and toggle their wifi on and off. Then when users bring the app to the foreground firebase finds itself in some inconsistent state and cannot be used until users reload the page.
And this #2755
Even though all PRs in @schmidt-sebastian comment in the link above have been merged we're still experiencing the issue.
Steps to reproduce:
With our production app we can consistently recreate it with the following steps:
Open the app and navigate around a few screens.
This seems to be important as we could not recreate it while being on the same screen. However it is not important which few screens we navigate to as we could reproduce the same error navigating between any two screens. I will add that that before leaving each of the screens (before runtime is destroyed) we destroy firebase app to release resources and then reinitialise it on the following screen.
Put app to background
Go to settings and toggle wifi off back on
Resume the app
Observe firestore errors in console and none of firebase features work.
Debug enabled log output shows starts at the time just before app is put to background, then toggling wifi on and off in the settings and ends after the app has been resumed:
If the issue is already being addressed on some other ticket/tracker, please let us know.
As this is our production app you would understand our keenness to get to the bottom of it
Thanks!
EDIT:
This only seems to happen with persistence enabled.
Also it seems older iOS versions are not affected. Tested on iOS 12.4.1 with no issues.
The text was updated successfully, but these errors were encountered:
I have actually seen this locally as well. "The database connection is closing" is however thrown at a strange layer in our code, and so the work I have done to recover from IndexedDB errors doesn't help here. I need to see if I can figure out how to change our recovery logic to apply here as well.
[REQUIRED] Describe your environment
iOS 13.6
"Mozilla/5.0 (iPad; CPU OS 13_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148"
)7.16.0
(also present on7.17.1
)firestore
[REQUIRED] Describe the problem
We have a multi page Cordova app which uses Firestore with persistence enabled. It issue happens when users navigate about a few pages and then put the app in the background and toggle their wifi on and off. Then when users bring the app to the foreground firebase finds itself in some inconsistent state and cannot be used until users reload the page.
This could potentially be related to :
#2710
And this
#2755
Even though all PRs in @schmidt-sebastian comment in the link above have been merged we're still experiencing the issue.
Steps to reproduce:
With our production app we can consistently recreate it with the following steps:
This seems to be important as we could not recreate it while being on the same screen. However it is not important which few screens we navigate to as we could reproduce the same error navigating between any two screens. I will add that that before leaving each of the screens (before runtime is destroyed) we destroy firebase app to release resources and then reinitialise it on the following screen.
Debug enabled log output shows starts at the time just before app is put to background, then toggling wifi on and off in the settings and ends after the app has been resumed:
If the issue is already being addressed on some other ticket/tracker, please let us know.
As this is our production app you would understand our keenness to get to the bottom of it
Thanks!
EDIT:
This only seems to happen with persistence enabled.
Also it seems older iOS versions are not affected. Tested on iOS 12.4.1 with no issues.
The text was updated successfully, but these errors were encountered: