api
4 TopicsEdge Extension Publish/Upload API returns 500
I've just migrated from v1 to v1.1 of the Edge Extension Upload API. Since then I'm only receiving HTTP 500 responses from the API. All credentials are correct since I've also received some 4xx before that. The following is a curl req & res. All sensitive params are redacted. The exact same extension package gets distributed to the Chrome store. Nothing really changed in the extension package from v1 to v1.1. > POST /v1/products/.../submissions/draft/package HTTP/1.1 > Host: api.addons.microsoftedge.microsoft.com > User-Agent: curl/8.7.1 > Accept: */* > Authorization: ApiKey ... > X-ClientID: ... > Content-Type: application/zip > Content-Length: 345344 > * upload completely sent off: 345344 bytes < HTTP/1.1 500 Internal Server Error < Content-Length: 0 < Strict-Transport-Security: max-age=31536000; includeSubDomains < x-ms-middleware-request-id: ... < Request-Context: appId=... < Date: Tue, 04 Feb 2025 17:59:14 GMT58Views1like0CommentsGood News: Google is finally killing off Chrome apps, End support for NaCl, PNaCl, and PPAPI APIs
Google said Wednesday that it will begin to phase out traditional Chrome apps starting in June, and winding down slowly over two years’ time. Chrome extensions, though, will live on. This is good, because the new Chromium based Microsoft Edge isn't compatible with Chrome apps which are basically the same as Chromium extensions. so with this update, Microsoft won't be needing to add any compatibility for those apps. With this continued progress, we are expanding upon our earlier announcement and will begin phasing out support for Chrome Apps across all operating systems as follows: March 2020: Chrome Web Store will stop accepting new Chrome Apps. Developers will be able to update existing Chrome Apps through June 2022. June 2020: End support for Chrome Apps on Windows, Mac, and Linux. Customers who have Chrome Enterprise and Chrome Education Upgrade will have access to a policy to extend support through December 2020. December 2020: End support for Chrome Apps on Windows, Mac, and Linux. June 2021: End support for NaCl, PNaCl, and PPAPI APIs. June 2021: End support for Chrome Apps on Chrome OS. Customers who have Chrome Enterprise and Chrome Education Upgrade will have access to a policy to extend support through June 2022. June 2022: End support for Chrome Apps on Chrome OS for all customers. Also end of support for NaCL, PNaCL and PPAPI, are all good news for everyone. They are all Google-specific technologies. most of the stuff built upon them only require Google chrome browser. removing them also removes that restriction and makes everyone happy. Cheers everyone! Source5.6KViews4likes4CommentsWhich one is better? Skia API as the graphics API or OpenGL ES
I'm looking for pros and cons of each API, because Edge Canary version 83.0.467.0 has a new flag called: Skia API for compositing If enabled, the display compositor will use Skia as the graphics API instead of OpenGL ES. – Windows #enable-skia-renderer and I want to know what are the benefits of Skia API over OpenGL ES if i turn it on?Solved67KViews0likes5Comments