Upgrading the PowerServer project
After applying Build 3409, for PowerServer projects to work correctly, you will need to
1) Open the %AppwebAPI_Home%\UserExtensions\Logging\Logging.xml file and modify the following line:
<PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.21.0" />
to
<PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.22.0" />
2) Upgrade all your existing PowerServer projects by following instructions in Upgrade the PowerServer project.
Note: The solution settings have not been changed in Build 3409 (compared to Build 3382), so there is no need to update the solution settings.
3) If you have deployed a PowerServer project using any previous version, 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).
Note:
(1) Starting from this release, the launcher file used for launching the PowerServer 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.
(2) 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.
(3) Inform your end users that run the PowerServer-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 PowerClient project
After applying Build 3409, for PowerClient projects to work correctly, you will need to
1) Upload Cloud App Launcher and Runtime to the server;
2) Deploy the PowerClent projects again.
3) If you have deployed a PowerServer project using any previous version, 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).
Note:
(1) Starting from this release, the launcher file used for launching the PowerServer 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.
(2) 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.
(3) Inform your end users that run the PowerServer-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".
For PowerServer 2020 or earlier
PowerServer 2022 R3 is a brand new product, totally different from PowerServer 2020 or earlier, therefore:
PowerServer 2020 or earlier cannot be upgraded to PowerServer 2022 R3; and applications deployed with PowerServer 2020 or earlier cannot work with PowerServer 2022 R3.
