Azure / api-management-developer-portal

Developer portal provided by the Azure API Management service.
MIT License
489 stars 319 forks source link

Error when trying to edit API Management Service Developer Portal. We get the error when navigating to edit the portal "Oops, something went wrong. We are unable to complete your operation this time. Please try again." #1136

Closed PerMBlomqvist closed 3 years ago

PerMBlomqvist commented 3 years ago

Bug description

Error when trying to edit API Management Service Developer Portal. We get the error when navigating to edit the portal "Oops, something went wrong. We are unable to complete your operation this time. Please try again."

This worked fine for several weeks but started failing consistently recently (past 1-2 weeks).

Failure happens every time and we have tried various users with Admin and Owner rights.

Reproduction steps

1: In Azure API Management Service. Navigate to Portal Overview. 2: Click Developer Portal button/link. 3: This open up another browser tab and attempts to open the Portal Authoring/Edit UI. We can see the floating toolbars but then get the spinner and the "Oops, something went wrong....." message.

Getting these errors in Chrome Dev tools: Uncaught (in promise) TypeError: permalinkResolver.getHyperlinkFromContract is not a function at exports.PermalinkResolver. (paperbits.js:2) at Generator.next () at paperbits.js:2 at new Promise () at __awaiter (paperbits.js:2) at exports.PermalinkResolver.getHyperlinkFromContract (paperbits.js:2) at exports.ButtonModelBinder. (paperbits.js:2) at Generator.next () at paperbits.js:2 at new Promise ()

APIM error

Expected behavior

System should open dev portal in edit mode.

A clear and concise description of what you expected to happen.

Is your portal managed or self-hosted?

Managed

API Management service name

https://prod-safe-affinity-apimanagement.management.azure-api.net

Environment

Windows 10, Chrome.

Additional context

Add any other context about the problem here, including screenshots. See screen shot with Chrome Devtools turned on.

azaslonov commented 3 years ago

Hi @PerMBlomqvist, yeah, this is known issue, it was fixed already, the release is coming some time next week.