Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (7)

Resolved Chrome Update 130.0.6723.59, PowerClient Application Not worked.

  1. Issue
0
Votes
Undo
  1. Sang Chul Song
    Sang Chul Song
  2. PowerBuilder
  3. Friday, 18 October 2024 01:00 AM UTC

 

PowerBuilder : Version 2022 R3, 3356

Use PowerClient Deploy

Chrome : Chrome Version 버전 130.0.6723.59(공식 빌드) (64비트)

 

Chrome for Update this Version, after failed this message

"cloudapplauncher.js:61 WebSocket connection to 'ws://127.0.0.1:26571/https://xxx.xxx.xxx/XXX/' failed: "

PowerClient Application Not worked.

 

Attachments (1)
2024-10-18_09-56-14.png 2024-10-18_09-56-14.png
After install of 2025 beta I can't access PB 2022 ...
Any idea to develop a similar window in Powerbuild...
Responses (7)
Sang Chul Song
Sang Chul Song Accepted Answer Pending Moderation
  1. Wednesday, 30 October 2024 06:04 AM UTC
  2. PowerBuilder
  3. # 1

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

 

this file modify, deployed file not modify!!

Comment
Angie Liu@Appeon
  1. Angie Liu@Appeon
  2. Monday, 11 November 2024 03:21 AM UTC
Hi Sang,

Good news that PowerBuilder 2022 R3 MR (build 3397) is available for download. The issue you reported has been fixed in this release. Please download and install it to verify the issue you reported and let us know if any problems. You can get the installer from our Downloads portal at https://account.appeon.com/download (login required).

We welcome all feedback from you!

Regards,
Angie
  1. Helpful
There are no comments made yet.
Tomas Beran
Tomas Beran Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 13:16 PM UTC
  2. PowerBuilder
  3. # 2

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.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 21 October 2024 19:06 PM UTC
Yes, we are working on a fix. But in meantime please follow this KB article: https://www.appeon.com/developers/get-help/knowledgebase/4613
  1. Helpful 3
Tomas Beran
  1. Tomas Beran
  2. Tuesday, 22 October 2024 12:08 PM UTC
Thank you.

I can confirm that solution #2 works well

  1. Helpful 2
There are no comments made yet.
Rob Stevens
Rob Stevens Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 02:03 AM UTC
  2. PowerBuilder
  3. # 3

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

Comment
Andreas Mykonios
  1. Andreas Mykonios
  2. Monday, 21 October 2024 07:29 AM UTC
Hi.

I guess that for those new users the cloud launcher isn't installed... Probably this may be your issue...

Andreas.
  1. Helpful
Rob Stevens
  1. Rob Stevens
  2. Monday, 21 October 2024 08:47 AM UTC
Yes, correct. However, we have found that a new user can still download and install the cloud app launcher from the website. They can then install that and then create a desktop shortcut to run the cloudlauncher to download and install the application. So we have a workaround.
  1. Helpful 1
There are no comments made yet.
Sang Chul Song
Sang Chul Song Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 01:16 AM UTC
  2. PowerBuilder
  3. # 4

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.

Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Sunday, 20 October 2024 21:34 PM UTC
  2. PowerBuilder
  3. # 5

Hi,

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

Best,

m.

Comment
Angie Liu@Appeon
  1. Angie Liu@Appeon
  2. Monday, 21 October 2024 02:42 AM UTC
Hi Marco;



Yes, Edge and Chrom have the same problem. Before the official solution comes out, we recommend:

1. Use Firefox browser to load the application

2. Use Win + R to run this command: cloudlauncher:// + your application URL name



Regards

Angie
  1. Helpful
There are no comments made yet.
Angie Liu@Appeon
Angie Liu@Appeon Accepted Answer Pending Moderation
  1. Friday, 18 October 2024 09:36 AM UTC
  2. PowerBuilder
  3. # 6 
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
Comment
Angie Liu@Appeon
  1. Angie Liu@Appeon
  2. Friday, 18 October 2024 10:17 AM UTC
Hi Sang,



Recommend a temporary workaround solution:

Win + R

Run this command:

cloudlauncher:// + your application URL name

Example:

cloudlauncher://https://demo.appeon.com/sales/



Regards

Angie
  1. Helpful 2
Sang Chul Song
  1. Sang Chul Song
  2. Monday, 21 October 2024 01:18 AM UTC
yes worked this customer protocol,

Edge update, Chrome update, use this browsers not working PowerClient URL application.
  1. Helpful
There are no comments made yet.
Sang Chul Song
Sang Chul Song Accepted Answer Pending Moderation
  1. Friday, 18 October 2024 04:20 AM UTC
  2. PowerBuilder
  3. # 7

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

this custom protocol "cloudlauncher" not worked

custom protocol not worked in chrome version 130.0.6723.59 

 
Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.