Issue with MediaUpload component

Hi @rishishah

My understanding is that you have developed a plugin with a MediaUpload component from the @wordpress/block-editor package in your custom Gutenberg block.

Regarding the error, it’s possible that the issue is arising due to a conflict between the custom block’s MediaUpload component and a component in the Jetpack plugin. This conflict might occur if there are identically named components, or if there’s some overlap in the way events are handled or hooks are used.

We need more information here. You said your plugin is working fine on the WP VIP server. Is this alongside Jetpack?

When you say you only face the issue when you activate Jetpack from an archive downloaded from WP.org, that implies that the version of Jetpack in both cases differs? Is that correct? Also, can you check what Jetpack modules are active when the error occurs?

Any additional information you can provide here should help our development team assist you.

Hello @ihenetudan

Thank you for your response.!

Here are my answers to your questions:

1) We need more information here. You said your plugin is working fine on the WP VIP server. Is this alongside Jetpack?
Ans: On the VIP server, we have not added additional Jetpack plugin because the VIP server provides it by default.

2) When you say you only face the issue when you activate Jetpack from an archive downloaded from WP.org, that implies that the version of Jetpack in both cases differs? Is that correct? Also, can you check what Jetpack modules are active when the error occurs?

Ans: We don’t activate any module yet on the?Jetpack plugin, our plugin crashes by default settings of the Jetpack plugin. Also, we tried with three versions lower of the Jetpack plugin, but we still got an error.

Please let me know if you need any other information from my side.

Thanks.

This does indeed seem like a conflict between the Jetpack blocks and the blocks registered in your plugin. As mentioned in the error, this may happen when you have mismatching versions of React.

Does your plugin rely on specific WordPress packages, such as @wordpress/element? If so, could you check that it relies on recent versions of each package?

If that doesn’t help, could you post a link to your plugin, either here on the plugin directory or on GitHub, so we could take a closer look at it with you?

Thank you!

Hello @rishishah,

Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!