Describe the problem
I am developing an app for KaiOS, a fork of the old Firefox OS, for which apps are based on HTML5 + JS. When compiling and running on device, Firebase Cloud Messaging stops working. I receive an error as follows. I believe the issue is due to the fact that on device the app is served in the browser via a file:// based URL scheme rather than a http:// based scheme.
DOMException: A request was placed against a transaction which is currently not active, or which is finished.
In my research, I have found that Cordova, Expo, and other file:// based environments have had issues around the use of IndexDB not being supported, which FCM seems to rely on. I can confirm that KaiOS does have full support for IndexDB, however the above issue persists.
Note: I am aware that this is very similar to my other issue I logged: #3027 however it is for a different Firebase product so I wanted to document both.
Describe your environment
Describe the problem I am developing an app for KaiOS, a fork of the old Firefox OS, for which apps are based on HTML5 + JS. When compiling and running on device, Firebase Cloud Messaging stops working. I receive an error as follows. I believe the issue is due to the fact that on device the app is served in the browser via a file:// based URL scheme rather than a http:// based scheme.
In my research, I have found that Cordova, Expo, and other file:// based environments have had issues around the use of IndexDB not being supported, which FCM seems to rely on. I can confirm that KaiOS does have full support for IndexDB, however the above issue persists.
Relevant Code:
Note: I am aware that this is very similar to my other issue I logged: #3027 however it is for a different Firebase product so I wanted to document both.