iOS. NewNode proxy does not receive connections after returning app from background about newnode HOT 8 CLOSED

We tried to use generic http proxy (local tinyproxy instance) and we do not have this kind of errors.

We researched NN code (client.c), but haven't found any ways to reinitialize newnode.

@ghazel Can you, please, help us in dealing with this issue? It's very important for us to deal with it rapidly.

from newnode.

You are running tinyproxy on the iOS device itself, as part of your app?

from newnode.

Of couse not. We just tried to use some generic http proxy to prove that the issue is not in our proxy client code

from newnode.

This is the same issue as #96

from newnode.

Is there a workaround available? We can add some code to foreground/background event handlers to init/deinit newnode for iOS.

In essence, the app is unusable after returning from the locked screen. That's the usual case for our users: they checkout the app content, switch to something else, lock the screen, check the app again.

from newnode.

There is a fix in progress, but no work-around currently. (You could kill your app when backgrounded, but that might be too disruptive)

from newnode.

Fixed. Will be released shortly.

from newnode.

Released in 2.0.4

from newnode.