hypertrons-crx icon indicating copy to clipboard operation
hypertrons-crx copied to clipboard
verified publisher icon hypertrons

[Bug] Edge deployment failed

Open wangyantong2000 opened this issue 1 year ago • 9 comments

Version

1.9.16

Current Behavior

In the action, it can be seen that edge deployment has failed. Need to investigate edge deployment. GPT's response is that this error code indicates that the resource (API or endpoint) you are attempting to access has been deleted or is no longer available. In other words, the deployed API or service endpoint is outdated or obsolete. Image

wangyantong2000 avatar Jan 20 '25 14:01 wangyantong2000

Image The previous OSgraph URL used in the current online version seems to have expired. The latest version of CRX has been successfully launched on Chrome, and Edge has manually uploaded it.

wangyantong2000 avatar Jan 20 '25 14:01 wangyantong2000

After reviewing the official Microsoft documentation, it is stated that both v1.1 and v1 versions of the Update REST API are supported as of September 6, 2024. However, support for v1 will end on December 31, 2024. Our project is currently utilizing the v1 version, and it is now necessary to update to v1.1.

Xsy41 avatar Feb 13 '25 11:02 Xsy41

After reviewing the official Microsoft documentation, it is stated that both v1.1 and v1 versions of the Update REST API are supported as of September 6, 2024. However, support for v1 will end on December 31, 2024. Our project is currently utilizing the v1 version, and it is now necessary to update to v1.1.

Okay, you try to deal with it.

wangyantong2000 avatar Feb 13 '25 11:02 wangyantong2000

The latest API key has been updated on Yuque. It now includes the Client ID, API Key, and Product ID, all of which have been updated.

Xsy41 avatar Feb 13 '25 11:02 Xsy41

The latest API key has been updated on Yuque. It now includes the Client ID, API Key, and Product ID, all of which have been updated.

Is there an error when trying to upload locally? Is it possible to go through？

wangyantong2000 avatar Feb 13 '25 11:02 wangyantong2000

Is there an error when trying to upload locally? Is it possible to go through？

sure, it can pass!

Xsy41 avatar Feb 13 '25 11:02 Xsy41

Currently, the deployment script in the project uses the @flameohg/edge-addons-API library for edge publishing. The version used in the project is 1.0.1, and the current new version is 2.0.0. The usage of some APIs in the new version has changed. After upgrading the version locally, uploading extensions at local runtime will not generate any errors. But it will not be automatically published in the Edge store. Further investigation is needed to identify the root of the problem.@Xsy41

Image

wangyantong2000 avatar Feb 16 '25 07:02 wangyantong2000

I have already opened an issue in the Microsoft Edge Add-ons GitHub repository, and the investigation is ongoing!

  • https://github.com/microsoft/MicrosoftEdge-Extensions/issues/273

Xsy41 avatar Feb 18 '25 05:02 Xsy41

I have already opened an issue in the Microsoft Edge Add-ons GitHub repository, and the investigation is ongoing!

Thank you for following up.

wangyantong2000 avatar Feb 18 '25 05:02 wangyantong2000