My App Interfering with Cisco Jabber

questions
21

But even using MessageBox does not normally add the min/max buttons to the message window. Something more is going on. :wink:

22

Cool - so then to answer earlier comments in the thread, yes you are “hooking” your own MESSAGE procedure.
So there’s good news, and bad news with that.
The bad news is that the “new” MESSAGE procedure you are using is just a Clarion procedure in your app tree. So there’s no reason for it to be interacting with Jabber, since, um, it’s just a bog standard procedure.

The good news though is that it’s much easier for you to debug, since, it’s just a procedure in the app. So you can do things like exclude code and experiment to narrow down the actual source - the line of code that causes Jabber to behave like it does.

One immediate test to try is running the MessageBox example on the problem machine to see if it exhibits the same issue.

cheers
Bruce

23

Hi Bruce,

Here are some results:

  1. CapesoftMessageBox\msgbox.app: This app DOES exhibit the same issue.
  2. CapesoftMessageBox\MesBox&HyperActive\abc.app: This app doesn’t exhibit the same issue.
  3. Blank new app with MessageBox added doesn’t exhibit the same issue.

The customer IT contact said the behaviour is the same as clicking text that is a phone number in any Microsoft Office 365 app (Word, Outlook etc). Doing this will open Jabber too.

Also upgrading to C11 didn’t resolve the issue.

Regards,
Trent

24

Excellent. So you have one app where it has the problem and one where it does not.
So you can compare them, and slowly move them closer to each other until you see the problem occur.
This will narrow down the root of the cause.

So compare the global settings in the 2 apps, and slowly adjust the settings so that the working one becomes a problem one.

Before looking at the MessageBox settings, start with the Manifest settings and see if both apps have the same manifest. Once that’s sync’d up move onto the MessageBox settings.

cheers
Bruce

25

Care to elaborate further on the ‘Manifest settings’ as both apps have the exact same global settings?

26

Global Properties,
Actions,
app Settings,
Application Manifest

27

Thank you. In regards to the app manifest:

  1. CapesoftMessageBox\msgbox.app: Does have a manifest set.
  2. CapesoftMessageBox\MesBox&HyperActive\abc.app: Doesn’t have a manifest set.

I’ve set the ‘abc.app’ app to have a manifest and have asked the customer to see if this app now exhibits the same behaviour. They are away until 6th of Oct so will have to wait until then for an answer.

28

The customer has said that both Capesoft MessageBox test apps are now exhibiting the same behaviour and causing the Cisco Jabber window to open. This is with both apps having a manifest generated in the app settings. When the manifest is not generated then the issue doesn’t happen.

The problem is that my app doesn’t have the manifest set in the exe app. The exe app does have a separate manifest file created by IngaSoftPlus EasyCam.

Also in a demo app I created with just a ‘Main (Frame)’ proc and MessageBox added with and without a manifest doesn’t cause the Jabber window to appear. Tried all the same template settings and global property settings but can’t get this demo app to behave the same way.

Anyone have any further recommendations?

29

SOLVED!

I removed CapeSoft MessageBox and replaced with my own ‘message’ window with a timeout (which is all we used it for) that doesn’t hook the builtin message function. Tested successfully with the customer.

Pretty simple to do. If anyone wants the code let me know.

Regards,
Trent

1 Like
30

It would still be nice to know what actually caused it, whether or not it was within MessageBox itself. Glad you got rid of the problem though.

31

Well this issue is back with the same customer.

The customer upgraded from Cisco Jabber v12.6.4.39721 to v14.0.0.55563 and suddenly my app is now interferring with Cisco Jabber again. Downgrading back to v12.6.4.39721 stops the issue from happening. At this point I think it’s a bug with Cisco Jabber.

I’ve advised the customer to submit a bug report to Cisco. Will keep this topic updated with the outcome for those interested.

Regards,
Trent

32

Have you ruled out the possibility that some kind of malware could be involved?

33

Hi Jeff,

I’ve asked the question and am waiting for their reply.

34

The customer doesn’t think it’s malware related. They have submitted a bug report to Cisco and are waiting for their reply.

35

Cisco have come back to the customer with this information:

It appears there may be a conflicting Hot Key between the two programs. It appears the default Jabber Hot Key is CTRL+SHIFT+J and something within kwiklook is triggering that.

MakeCallHotKey parameter: Specifies a key combination to define a keyboard shortcut in the client. The shortcut allows users to copy text from another application and paste it into the client. When you configure a key combination, it overwrites what another application does with that keyboard shortcut. More information can be found here: Parameters Reference Guide for Cisco Jabber 12.5 - Phone [Cisco Jabber for Windows] - Cisco

To my knowledge there is no Alert code in our app for CtrlShiftJ. The only Alerts we use are:

Alert(633) !AnyText
Alert(AltKeyPressed) ! WinEvent : These keys cause a program to crash on Windows 7 and Windows 10.
Alert(F10Key) !
Alert(CtrlF10) !
Alert(ShiftF10) !
Alert(CtrlShiftF9) !
Alert(CtrlShiftF10) !
Alert(AltSpace) !

I’ve done a search in all the apps for alert(CtrlShiftJ), alert(ShiftCtrltJ), alert(CtrlJ%, alert(ShiftJ% and alert(J% , all with 0 results.

What else in Clarion could cause the CtrlShiftJ keys to be pressed when a window or messagebox appears?

36

Also look for ALRT and KEY. That’s what is used in WINDOW declarations.

37

No matches on those either.