swagger json upload returns error: expects title field

[michowl]

Recieving this message when uploading my json swagger def:

An error occured while converting swagger file to WADL file. Error: 'Swagger document does not include required title field'. Your API may not work with apps.

I would expect that the title it wants is in info.title which is where swashbuckle's default config placed it.

partial of swagger:

{
	"swagger":"2.0",
	"info":
	{
		"version":"v1",
		"title":"My API Title"
	},
	"host":"**removed**",
	"schemes":["https"],
	"paths":{
...[paths removed for brevity]...
	},
	"securityDefinitions":
	{
		"AAD":{
			"type":"oauth2",
			"flow":"implicit",
			"authorizationUrl":"**removed**",
			"scopes":{}
		}
	}
}

[SinanE]

Sorry for the inconvenience, we are investigating the issue. If you proceed uploading your file despite this warning, does your custom API work as expected?

Thanks.

[michowl]

Yes, the swagger works fine and is usable by both PowerApps and Flow.

[mcorning]

i started seeing this error on friday (never before then, and i've been using PowerApps continuously for months) and only after i upgraded PowerApps Studio to 2.0.592.

i was unable to use my new custom api after seeing this error. here's what happens when i load the connection in PowerApps Studio.

No wadlUrl is specified for this Api. This usually indicates there was an error when converting the Swagger associated with this api to a WADL file.

apiId: /providers/microsoft.powerapps/apis/shared_getgeocodedaddress.5f70024346a22042f4.5fe80ee8a2e1929382

Session ID: f7dbbf31-4919-03df-0259-88dfc10c8741

so it appears there's a relationship between the (missing?) title property and the wadlurl. btw, i have and have always had a title property in the info object of swagger.

[SinanE]

Was this swagger working fine before?

The issue with validation at the time of custom api creation might be hiding actual Swagger errors. We are working on fixing that currently to make sure validation is back in place.

Meanwhile, please feel free to send me a private message attaching your swagger json file and I can get that checked up.

[mcorning]

i would if i had your private email. <g/>

i sent everything to archana earlier today.

[SinanE]

The fix is live now. Custom api creation should only show actual swagger issues.

[mcorning]

i am testing things these days using the simple swagger for default azure functions as http triggers.

here is the bulk of the swagger (it still returns the infamous missing title field error).

{
  "swagger": "2.0",
  "info": {
    "version": "2.0.2",
    "title": "deletedToProtectTheGuilty"
  },
  "host": "deletedToProtectTheGuilty.azurewebsites.net",
  "schemes": [
    "https"
  ],
  "paths": {
    "/api/helloName": {
      "get": {
        "description": "Provides a BVT for setting up custom apis and using them in PowerApps.",
        "operationId": "SayHello",
        "parameters": [
          {
            "name": "code",
            "in": "query",
            "description": "code",
            "default": "aL6v06/7LM/rBQRk7uolCLUHJaQtLMyxNMs0NJL3ZVFRPM71w1UvMg==",
            "type": "string"
          },
          {
            "name": "Name",
            "in": "query",
            "required": true,
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Name",
            "schema": {
              "title": "Hello [Name].",
              "type": "string"
            }
          }
        }
      }
    }
  }
}

can you repro on your side?

^m

[SinanE]

We cannot repro the issue, your swagger should be working. Could you try in a prviate window or clear your browser cache and try again?

[mcorning]

interesting...i have not yet seen the error...but the browser is still rendering

"Parsing swagger file..."

i'll try everything again and see what happens.