WiseJ site not reloading upon new build. And sessions expire with no notice.

Welcome to Wisej Support.
Questions, suggestions and plain old bugs - are all welcome here!
Answered
0
1

I have 2 new issues which seem to be related.  I am testing on an Android 7.0 (Galaxy S7) phone using Chrome standalone, and also a WebView in a native app. WiseJ version 1.5.48. The behavior is the same on both.  It does not matter if it is deployed on my dev or production machine, the behavior is on both.

 

  1.  When rebuilding / re-publishing my WiseJ app, if you were currently on the website, it used to be that it would detect the change and automatically reload the page.  This has stopped working in 1.5.48 or so. Now, the app simply becomes unresponsive, with client side code executing, but no server code.  And no “network is down, retry?” dialog comes up. The app just dies.
  2. If in Chrome or in the native app w/ WebView, if you minimize the WiseJ app for a sufficiently long time (longer than is necessary for a session timeout, 20-30 minutes), and reopen the app, WiseJ no longer displays a “Session expired” dialog, nor a “Network is down, retry?” dialog.   The server is simply unresponsive, but client code (like panning/zooming a Google map) still works.It’s pretty bad but in the case of Chrome, you can at least reload the URL. In the case of a PWA or native app, the app is fully dead and must be force-closed and reopened.
  • Andrew
    More details: I uninstalled both 2.0.11 and 1.5.48, rebooted, cleaned solution, cleaned ASP cache, and reinstalled 1.5.43 and rebuilt, tried it on a separate project, but the behavior still exists. On a separate dev computer, running 1.5.43, I do not have the problem. I never tried to install 2.0 on that machine. This leads me to believe it was a configuration problem from installing WiseJ 2.0 and then downgrading to 1.x again.
  • You must to post comments
Best Answer
1
0

Hi Andrew,

thanks for reporting this. It´s a side effect of a fix we introduced for a different problem.
It will be fixed in the next releases for 1.5 and 2.0.

As a workaround you can add this to default.html

Wisej.onExit = Wisej.onExit || function () {

  if (Wisej.Core.session.autoReload) {
    location.reload();
  }
  else {
    window.close();
  }
};

Best regards
Frank

  • Andrew
    Thank you Frank. I am surprised the bug remained after an uninstall/reinstall. For now I may publish the production site from the unaffected dev machine.
  • You must to post comments
0
0

This appears to be fixed in 1.5.49 (first issue). Haven’t confirmed that the 2nd issue is fixed yet. Thank you.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.