Tranquil IT Forum

Hello,

I'm using a WAPT 2.4.0 agent on Windows 11, with
a WAPT console (version 2.4.0.14058)
and a WAPT server (version 2.4.0)

. I'm experiencing package update problems (when I click "Launch package update") for no apparent reason; there are no logs on the console, only the error message. I've reinstalled the console, but that hasn't fixed the problem.

Sincerely, Thomas.

That's strange, it crashes during the package upload.

Does this happen every time?

Hello Thomas,

are you getting the same error when you run the update with a recently downloaded update_package from the store (i.e., downloading the tis-chrome package from the store to get the latest update_package)?

Website developers modify their sites from time to time, and sometimes it's necessary to update the update_package function.

Regards,

Denis

I just tried with three example packages:
- In Adobe, the error message appears instantly when I click "Upload selected packages."
- In Teams, it appears after the "Downloading:" message (even though I cleaned the %TEMP% folder).
- In Chrome, whether it's the Linux or Windows version, I get the same error message.

What's surprising is that you haven't offered any new versions of these packages to potentially fix these update problems.

However, I was able to update Firefox on Windows, so I think the issue stems from these packages and not from my console.

Sincerely.

Chrome is displaying a different message than before; it's trying to access the API, so it's using the old package (the API is no longer working).

For Teams, it uses "os.rename," which has been removed from our internal package, so you're using the version from 8 months ago.

With the update package, you don't benefit from the new setup.py file we provide.

For Adobe Reader, the upload to the server failed.

Hello Thomas,

thomas789 wrote: ↑Dec 11, 2023 - 5:34 PM ...
What's surprising is that you haven't offered me any new versions of these packages to potentially fix these update problems.
...

If you have updated the package locally to such a recent version, the console will not offer the one from our store. However, you can retrieve it by disabling "newer version only" or by accessing the store's webpage.

You can then check the differences in the update_package() functions

Sincerely,

Denis