none
Swagger Editor (for Logic Apps Custom Connector) seems to be broken (just displays a blank grey page) RRS feed

  • Question

  • Hi.  I used the Swagger editor as recently as 1 or 2 weeks ago and it worked fine, however today it is just showing a blank grey page.  To rule out browser cache/cookies issues I have tried using Chrome Incognito mode and I still get the same result.  

    How can we get this fixed?  I would like to raise a Support case but can't as we don't have a Support agreement.  Thanks

    Monday, October 21, 2019 4:34 AM

Answers

  • Hello David,

    We apologize for the inconvenience you have encountered. Can you send an email to AzCommunity[at]Microsoft[dot]com along with the link to this Thread.

    UPDATE:

    Hello,

    PG has confirmed that there was an issue in Logic App Custom Connector for which the fix is ready and the deployment will roll-out to all the regions over the course of a week.

    Apologies for the inconvenience caused. 

    Monday, October 21, 2019 7:44 AM
    Moderator

All replies

  • Hello David,

    We apologize for the inconvenience you have encountered. Can you send an email to AzCommunity[at]Microsoft[dot]com along with the link to this Thread.

    UPDATE:

    Hello,

    PG has confirmed that there was an issue in Logic App Custom Connector for which the fix is ready and the deployment will roll-out to all the regions over the course of a week.

    Apologies for the inconvenience caused. 

    Monday, October 21, 2019 7:44 AM
    Moderator
  • OK, thank you Ketan.  I've sent the email as directed.

    Regards, David

    Monday, October 21, 2019 11:10 PM
  • +1

    Just started happening to me today. I was changing actions, and I deleted an action, then created a new action.

    After hitting 'update connector', I saw an error on my new action:

    looks like an issue with the body:

    

    So I select 'edit' on the body, and I get a blank frame on the right-hand side.

    And if I click 'swagger editor', it shows completely grey: 

    I can't access swagger editor from any where in the 'definition' tab.

    And to add, I can create a new connector and encounter the same issue.


    Greg Ramsey Microsoft MVP - ConfigMgr Dell, Inc. www.twitter.com/ramseyg


    Wednesday, October 23, 2019 7:11 PM
  • The same thing is happening to me. Swagger editor will not open. I did open a ticket (waiting for response).

    Another few issues:

    1. Definitions that previously were considered valid are showing errors. Downloading the definition has odd double entries for paths that weren't there previously.

    2. Schema will not accept the "type: boolean" which previously worked. If you change a schema property from string to boolean it won't even save and shows an error on the top of the screen:

    {"code":"","Message":"PUT https://logic-apim-eastus2.management.azure-api.net:3443/apis/f054f4524c874f62b0a33a9e635ebeb4?import=true&protocols=https&protocols=http&path=apim/f054f4524c874f62b0a33a9e635ebeb4&api-version=2014-02-14 failed with BadRequest, content={\"error\":{\"code\":\"ValidationError\",\"message\":\"One or more fields contain incorrect values:\&


    Friday, October 25, 2019 12:43 AM
  • Hello JassenT,

    Updated my last post.

    Friday, October 25, 2019 5:47 AM
    Moderator
  • Thank you for the update. Hopefully this fixes the multiple problems:

    1. Valid openapi isn't be accepted (boolean and date-time types cause validation errors).
    2. The swagger editor isn't working.
    3. Cannot edit parameter/body in the portal if app shows validation errors.
    4. Previously working definitions, when downloaded, are corrupted (duplicate paths).

    For reference, here is a valid openapi definition that is showing as invalid:

    {
      "swagger" : "2.0",
      "info" : {
        "version" : "3junk",
        "title" : "Broken API",
        "description" : "Broken API Functions"
      },
      "host" : "broken.com",
      "basePath" : "/",
      "schemes" : [ "https" ],
      "produces" : [ "application/json" ],
      "paths" : {
        "/api/private/counter/update" : {
          "post" : {
            "tags" : [ "Broken" ],
            "operationId" : "CounterUpdate",
            "summary" : "Update entry in the counter table",
            "description" : "This is my description",
            "parameters" : [ {
              "name" : "body",
              "in" : "body",
              "required" : true,
              "schema" : {
                "$ref" : "#/definitions/BrokenObject"
              }
            } ],
            "responses" : {
              "200" : {
                "description" : "Success",
                "schema" : {
                  "$ref" : "#/definitions/BrokenObject"
                }
              },
              "400" : {
                "description" : "Bad Request",
                "schema" : {
                  "type" : "string"
                }
              }
            }
          }
        }
      },
      "definitions" : {
        "BrokenObject" : {
          "type" : "object",
          "properties" : {
            "id" : {
              "type" : "integer",
              "format" : "int32",
              "description" : "Integer and string work fine!!!",
              "title" : "Id",
              "x-ms-summary" : "id",
              "x-ms-visibility" : "important"
            },
            "added" : {
              "type" : "string",
              "format" : "date-time",
              "description" : "DATE-TIME CAUSES ERROR",
              "title" : "Added",
              "x-ms-summary" : "added",
              "x-ms-visibility" : "important"
            },
            "isDeleted" : {
              "type" : "boolean",
              "title" : "Is Deleted",
              "description" : "BOOLEAN CAUSES ERROR",
              "x-ms-summary" : "isdeleted",
              "x-ms-visibility" : "important"
            }
          }
        }
      },
      "securityDefinitions" : {
        "Api Key" : {
          "type" : "apiKey",
          "in" : "header",
          "name" : "x-functions-key"
        }
      },
      "security" : [ {
        "Api Key" : [ ]
      } ]
    }

    Friday, October 25, 2019 10:11 AM
  • Hello Jasssen,

    Yes it would fix all the above mentioned issue. Please monitor and let us know the results.

    As mentioned above , the deployment is ready to roll-out and will take a week to be available in all the regions.

    Friday, October 25, 2019 10:21 AM
    Moderator
  • Thank you for this update. Is this posted anywhere in the Azure portal? I checked Service issues, Planned maintenance and Health advisories which are all empty for EAST and EAST 2. The only issue listed is titled "authentication issues with azure MFA - RCA."
    Friday, October 25, 2019 1:05 PM
  • Thanks for the updates. How are we able to determine when a region is updated? Or do we just need to keep checking our connector to see if the swagger switch works?

    Greg Ramsey Microsoft MVP - ConfigMgr Dell, Inc. www.twitter.com/ramseyg

    Friday, October 25, 2019 1:20 PM
  • The Swagger editor is working again for me in East2. 

    Also, I opened a ticket with Azure Support on 10/24...The first response was 11/4. I referred them to this thread.

    Jassen 

    Wednesday, November 6, 2019 12:42 PM