I don't understand why you would need to set this in order to use HTML5 localstorage.
If for some reason you need to construct a full URL for something, you can get the port # using a System call.
(Not that that makes this a non-issue - the option is still useful for debugging your JS/CSS.)
As well, I think if you use HTML5 localstorage, you are missing much of the benefit of Rhodes. Why not use Rhom?
I need to use localstorage because I have an existing webapp that I do not want to re-write.
The browser saves the localstorage in a file using the url of the website of the app to build the file name, and the url includes the port number.
So, for a rhomobile app you get a different localstorage hive for each different random port number given by rhodes, that's why you need a fixed port number.
I do encounter the same thing, unless I force stop the application via Settings in android and also via the tab
button where all active apps are listed.
I can smell some bug that at some point when the application is restarting, the server port previously bound to
the local server was still bound or inaccessible. Thus rebinding to it when the app is restarted would fail
and as consequence rhomobile would try to bind to a different port. I am just suspecting that the port wasn't
freed or the local server instance isn't shutdown, thus creating another local server. Just a hunch, but its
the only possible reason that I could think of.
Hi, may I hope a fix for this issue, or should I replace all my localstorage code to use rho db api instead?