Edge extensions -- chrome.identity API is not a good UX
I am developing an Edge extension that connects to a Google account. So far, I've managed to connect using `chrome.identity.launchWebAuthFlow()`, but the user experience is not good -- I am forced to reconnect every hour to retrieve a new access token. In Chrome this is not a problem because it supports `chrome.identity.getAuthToken()`, which handles token refresh automatically. Is there a solution where the user doesn't have to reconnect their Google account every hour?What's new on Microsoft Partner Center for Edge Add-on Developers?
*Updated on 8th April 2022 to include new updates on Publish API, which is live now! Microsoft is happy to announce updates to https://aka.ms/MicrosoftPartnerCenter based on your feedback. These changes streamline the process of submitting a Microsoft Edge extension for review at the https://aka.ms/MSEAddons. Microsoft Edge Add-ons Publish API is now live! With this addition, you can integrate APIs directly into your build pipeline and deploy packages and publish updated versions without visiting the Partner Center. To learn more, you can check the below documentations: https://aka.ms/Using_MSFTEdgeAddons_API https://aka.ms/MSFTEdgeAddons_API_Reference Microsoft Partner Center breadcrumbs: The breadcrumbs feature has been added to the Microsoft Partner Center interface. Developers can now follow their exact path while navigating Partner Center. This allows developers to: Maintain awareness of their location within Microsoft Partner Center Click on any breadcrumb to navigate back to the selected page Task Menu: The Task Menu on Microsoft Partner Center has been revamped. The Overview section of the Microsoft Edge segment lists all your extensions which are either In the Store or In draft. Clicking on an extension from this list takes you to the Extension overview page. This page includes task menu on the left showing all the sections of the selected extension – Package, Availability, Properties, Store listings, and Analytics. This enables easy navigation between the extension package upload page and other pages. It also provides a transparent view of all the sections that developers need to complete when creating a new extension. Save & Continue / Publish: The Save & Continue option has been added to the top-right corner of the extension submission workflow panel. This enables developers to add the necessary details then save and continue to the next step with one click. The Publish button is blurred to indicate that the option is not yet available. Once you have completed all the details necessary to submit your add-on for review, the Publish option becomes active. This change is also helpful when updating extensions, as you may directly publish your updates from any page. Extension overview: The Extension overview panel remains the same and the status changes from grey to green next to each section that is updated. Go to https://aka.ms/MicrosoftPartnerCenter and upload/update your extension package to try out the new changes! Share your feedback and questions on the newly available updates with us in the comments below or through the https://aka.ms/MSFT_EdgeAddons_Support documentation.
Unable to publish extension
Hi, I have created an extension named "Chipotle" and I thought of publishing it. I have an account on partner center. While I try uploading my .zip file, it takes a whole lot of time but never completes and when I close browser and see, I can see its uploaded in draft state. Its been 10 days, it never give me an option to proceed further. I have attached a screen shot of same. Please help me on this. Regards, Ethen321Edge Stable crashing on extension function chrome.identity.launchWebAuthFlow
I've developed an Edge extension which allows users to login with their Google account. I use the https://developer.chrome.com/docs/extensions/reference/identity/#method-launchWebAuthFlow function for that and everything works fine. Problem is when you synchronize the Edge browser and the extension gets automatically installed, for some reason Edge crashes as soon as the launchWebAuthFlow function is called. I analyzed the Edge dump and it's the msedge.dll crashing. It works fine using Edge Beta instead. Below is the crash dump:
