Fatal Error when updating to Jetpack 11.3

Yep same here, on all 3 different sites… Something is really broken with new jetpack

Fatal error: Uncaught Error: Call to undefined method Automattic\Jetpack\Connection\Error_Handler::check_api_response_for_errors() in /data01/virt50419/domeenid/www.mkuubis.ee/htdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php:44 Stack trace: #0 /data01/virt50419/domeenid/www.mkuubis.ee/htdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(462): Automattic\Jetpack\Connection\Client::remote_request(Array, ‘{“package_versi…’) #1 /data01/virt50419/domeenid/www.mkuubis.ee/htdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(102): Automattic\Jetpack\Connection\Client::wpcom_json_api_request_as_blog(‘/sites/77990108…’, ‘2’, Array, ‘{“package_versi…’, ‘wpcom’) #2 /data01/virt50419/domeenid/www.mkuubis.ee/htdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(63): Automattic\Jetpack\Connection\Package_Versi in /data01/virt50419/domeenid/www.mkuubis.ee/htdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php on line 44

Thanks for the report. From our investigation, this appears to be something that throws a fatal while the upgrade is in progress. Once upgraded, this error won’t appear.

Please let me know if you have any other questions or need anything else.

Thanks for the reply! From what you say, this fatal error won’t impact the upgrade, or operation after the upgrade. That’s good (though kind of strange that there’s a fatal error but no consequence). However, out of an abundance of caution, I won’t update Jetpack in my other sites until this is fixed.

Thanks again.

Basically, what’s happening is during the upgrade process itself, the files are changed. In this case, the old file is still in memory while the new files has been added and a function is calling the new code.

There’s not a fix for it, per se. The error is only thrown because something is doing something literally as the files are changing.

Thanks for letting me know. I hope you don’t mind, but I want to make sure I understand. Are you saying that we should expect the fatal error message when upgrading from version 11.2, and that future releases will always have that fatal error message when updating from version 11.2? So, we should go ahead and update, even thought we know that the fatal error message will occur? Of course, I know we shouldn’t expect the error in subsequent upgrades e.g. from 11.3 to 11.3.1.

As a software developer myself (now retired) I understand the complexities of doing upgrades, and I am thankful and appreciate of all your efforts. I won’t pretend to know all the obstacles you are facing, but I must say it seems strange that you couldn’t update the software so that it doesn’t tell users that a fatal error occurred during an upgrade, when there really is no problem. I understand what you’re saying about conflicts between the new and old software, but I would think that there are ways for the software to detect this problem, and not throw a fatal error.

However, my opinions don’t really matter. If you tell me it’s perfectly safe to upgrade despite the error message, then I’ll do it on all my sites.

Thanks so much for your response to my questions.