Latest update breaks Jetpack

Could you try to log in to your site via FTP or CPanel, and delete the existing Jetpack plugin folder, and reinstall the plugin manually as explained here:
http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation

You’ll find the Jetpack plugin folder here:

wp-content
   plugins
     jetpack - DELETE THIS FOLDER

If you’re not sure how to do this, you can ask your hosting company for help. They should also have documentation explaining how to edit or remove files from your site using FTP or a File Manager in your admin panel.

Let me know how it goes.

Does the problem appear again when you install a fresh version of Jetpack?

Thanks for giving that a try. We’ll try to reproduce on our end, and I’ll let you know as soon as we find a solution.

In the meantime, 4.2.2 should work; you can download it here:
https://downloads.wordpress.org/plugin/jetpack.4.2.2.zip

Would you mind telling me more about your site setup, so I can try to reproduce the conditions in which you experienced the error? Do you use a single WordPress installation, or a Multisite network? Do you use any caching plugins or services? Where is your site hosted?

Thanks!

This might be a caching issue, as the error refers to a file that was updated, but doesn’t seem to be updated in your installation of Jetpack.

Would you mind trying to install Jetpack 4.3 again, and then replace the contents of the class.jetpack-admin.php file by this:
https://raw.githubusercontent.com/Automattic/jetpack/master/class.jetpack-admin.php

You can find this file at the root of the Jetpack plugin directory.

Let me know how it goes.

Sorry to hear that!

Do you happen to remember what Jetpack modules were active on your site?

Thanks for bearing with me through this! Would you be willing to do one more test? It’d be nice if you could install Jetpack 4.2.2, then deactivate your active modules, and then update to 4.3? Does that change anything?

Thanks for giving it a try. We’ll keep running some test on our end, and I’ll keep you updated. For now, I’m afraid I can only suggest that you keep using 4.2.2.

Sorry for all the trouble!

Since I can’t seem to reproduce the issue on any of my sites, would you be willing to contact us via this contact form, and mention this thread? I’d like to run some tests on your site directly, if that’s okay with you; it might help us get to the root of the problem faster.

Thanks a lot!