Hi Sang,

We have reproduced the issue you reported and are currently analyzing the root cause and possible solutions. In the meantime, we recommend installing the pre-upgrade version to load the application.

I will update you here as soon as there is any progress.

Regards,
Angie

Hi,

same error here, using Edge too (latest Windows update brought 129.x to 130.x).

Best,

m.

Hi

The problem is that new Edge 130 sends full URL as a parameter without double dot character.

URL:

cloudlauncher://http://server/application/

is now being forwarded as:

"C:\Users\user\AppData\Local\CloudAppLauncher_V2\AppLauncher_V2.exe" -u "cloudlauncher://http//server/application/"

instead of:

"C:\Users\user\AppData\Local\CloudAppLauncher_V2\AppLauncher_V2.exe" -u "cloudlauncher://http://server/application/"

It looks like MS Edge bug but Appeon could you please patch it? It seems easy. Just slightly change the URL parser.

cloudlauncher://https//xxxx.xxxx.xxx/XXX/

this custom protocol "cloudlauncher" not worked

custom protocol not worked in chrome version 130.0.6723.59 

Windows Edge Update : 버전 130.0.2849.46 (공식 빌드) (64비트) Update

this Edge Browser update, after not worked "cloudlauncher" custom protocol.

ㅠ.ㅠ my customers critical issues, no use power client applications.

Hi

We have found if the user has the application installed then they are fine running it from the Windows R cloudlauncher...

But if this is a new user then they don't have it installed on their machine then the Windows R workaround won't work.

Regards

Rob

$PowerBuilder Install Dir\PowerBuilder 22.0\Pstools\html\en\js\cloudapplauncher.js 

this file modify, deployed file not modify!!