Upgrading cloud app launcher
1) If you have deployed a PowerServer/PowerClient project using a version older than Build 3397, manually delete the cloudapplauncher.js file from the Web Server (The file location is %webserver_path%\%applicationName%\js\cloudapplauncher.js, for example, C:\inetpub\wwwroot\salesdemo_cloud\js\cloudapplauncher.js).
2) Upload cloud app launcher to the server either manually (for PowerClient) or automatically (for PowerServer where deploying the project uploads the launcher).
-
Starting from Build 3397, the launcher file used for launching the PowerServer/PowerClient application is named as cloudapplauncher-2.1.0.js. This new file fixes the "PowerServer/PowerClient applications failed to launch after Chrome/Edge protocol change (since Chrome version 130)" issue.
-
If you've previously modified the cloudapplauncher.js file to use cookie validation, you need to make the same modification to the cloudapplauncher-2.1.0.js file.
-
Inform your end users that run the PowerServer/PowerClient-deployed application, if they fail to run the application, after opening the application's URL in the browser, please clear the browser cache by following these three steps: 1) Open Developer Tools (F12); 2) Right-Click the reload button; 3) Select "Empty Cache and Hard Reload".
Upgrading the PowerServer project
After applying Build 3452, for PowerServer projects to work correctly, you will need to upgrade all your existing PowerServer projects by following instructions in Upgrade the PowerServer project.
Note: The solution settings have not been changed in Build 3452 (compared to Build 3397), so there is no need to update the solution settings.
Upgrading the PowerClient project
After applying Build 3452, for PowerClient projects to work correctly, you will need to
1) Upload Cloud App Launcher and Runtime to the server;
2) Deploy the PowerClient projects again.
