I installed firebase-tools-instant-win.exe for my flutter app. it works fine after configuring it. However I can't use the
emulators:start --export-on-exit=./saved-data
to save the database locally because when I Ctrl+C, it doesn't shutdown gracefully. There is no message that it shutting down and saving just a ^V
I also get the message that there are multiple instances of the emulator running. I notice the port assigned moves every restart on the (emulator)
browser console: localhost:4000, then 4001 etc...
Related
I am starting a QGuiApplication (Qt 5.12) and using a remote desktop connection to a Windows 10 PC. Everything works fine while the remote desktop connection is open, but when I disconnect and let the application run during the week-end, I can see in the logs that it stops processing Qt events (mostly network related in my case). The last thing the logs show is an "activation change" event.
When I connect again after the weekend, the Qt event loop starts again (the logs show again "Activation Change event") and of course there is a huge amount of queued events and the application gets in a non responding state (I am logging the number of Qt events queue in the loop using qGlobalPostedEventsCount).
This used to work correctly but stopped working, I think due to an update of Windows on the machine (maybe same root-cause than this thread ?).
Is this the expected behavior for applications when the windows remote connection is terminated? Is there a known fix for this?
I have not managed to properly fix the issue. As a work-around, using Microsoft "Remote Desktop" application instead of using the "Remote Desktop Connection" application avoids the issue.
Our team is faced with a delimma where we need to at app-run time, detect (and then make an action) when a mobile device connection is made with Firebase. Our app needs to store value locally to SQL Lite when offline, and then push these cached values back up to the realtime-database in Firebase when the connection is restored. Presently this re-connection to Firebase is only happening with our App is shutdown and restarted.
It seems that (at least with typescript) everything is governed by the app.component.ts file. Is there a way to force the '.info/connected' to be true when the device network connection comes back .. and do this while our app is still running (memory on the mobile)?
For some reason our google containers sometimes restart which we cannot find the cause of , this is fine i guess if they start up quick again which is sadly not the case.
The issue seems to be that the persistant disk volume isn't unmounted quick enough and when the restarted container tries to mount it, it just get stuck and you have to kill it and start it manually.
Is it possible to configure the containers to wait for unmount before re-mounting persistant disks, what would be the correct solution to tackle this problem?
kubelet gke-xxx-xxx-xx Warning FailedMount
Unable to mount volumes for pod "xxx-xxx-xxx-hdki0_default(UUID)":
timeout expired waiting for volumes to attach/mount
for pod "xxx-xxx-xxx-hdki0"/"default".
list of unattached/unmounted volumes=[xxx-volume]
kubelet gke-xxx-xxx-xx
Warning FailedSync Error syncing pod, skipping:
timeout expired waiting for volumes to attach/mount for pod
"xxx-xxx-xxx-hdki0"/"default".
list of unattached/unmounted volumes=[xxx-volume]
I'm having problem with the Windows Phone emulator.
Last night, when i have finished my works, I wanted to close it, but it didn't shut down properly.
After 10-15 minutes I shut down my computer.
But now, when I'm trying to connect to the emulator again, I can't.
I've tried many things, but it still fails.
I open the Hyper-V Maganger, and I saw that my emulator state is still "Stopping".
What can i do?
How do you listen for firebase messages while the ios app is running in the background?
How can I check for new messages while the ios app is running in the background?
The Firebase SDK uses iOS's underlying sockets, so the library will report new messages as long as the OS keeps the socket open. This can depend on the configuration of your app. If it is configured to be able to run in the background and use the network, then your observers will continue to function just like when the app runs in the foreground. If you app is not set up as able to run in the background, then the OS typically keeps the socket open for a short time before closing it. In that case, your app will need to enter the foreground again before it can start receiving new messages.