Session Status Popup bug on 8.3.5

Ignition
,
1

Hello all!

I'm having an annoying problem with the Session Status Popup that I can't get rid of from my project. Even though the X appears, it's unclickable, and it's present on every Perspective page in mobile-only mode:

WhatsApp Image 2026-04-27 at 09.49.10
WhatsApp Image 2026-04-27 at 09.49.10739×1600 108 KB

The problem only appeared on this third project after upgrading from 8.3.4 to 8.3.5.
I have two other projects with the same version, and they have no issues.
I've tried searching online for solutions, but to no avail.

  • How can I disable and hide this annoying popup? :sweat_smile:

Thanks!

2

A few ideas:

  1. It looks like you've partially dragged the popup out of the viewport, and this could be affecting how clicks/taps are used.
  2. You should be able to drag the page "down" to force a refresh and remove the popup.
  3. Restarting your session should also reset your state.

I can't explain how you managed to enter this state, as I don't recall that popup allowing for dragging. It is supposed to operate as a modal, and so any clicks outside of its boundaries should have the same effect as if you had clicked the X. That being said, the X should work as expected.

3

I don't think it's a simple drag & drop because when I restart GW and the app, the popup remains. (I also restored older GW backups, but the popup remains there. Even refreshing the page doesn't go away. X still doesn't work.)

Any other ideas on how I can fix this problem?

Thx

4

Are you using the native mobile application, or just a browser on your device?

5

I'm using both.. buth the result doesn't change.

6

Are you making use of custom components in any way? What about making use of Markdown components to inject JavaScript?

I ask because there is neither a system.perspective function nor a SDK Java call which would open that panel, and our implementation clearly initializes that UI piece as

@observable
appModalOpen: boolean = false;

This all suggests that the panel is being opened by JavaScript. My main suspicion is direct access of the internal MobX store, which could be managed through your own implementations of custom components, or injection through a Markdown.

This same potential cause would also explain why you're not able to "close" the panel. Whatever code is opening the modal is invoked immediately on close, resulting in the appearance of no action, when actually the panel is being closed and then immediately re-opened.