Skip to content

Publishing failed: Ambiguous match found #1633

@DanielGoehler

Description

@DanielGoehler

When I try to publish my Extension I get the error message Ambiguous match found.

[2018-02-19 20:31:06.63] Sending request to https://navfeb.westeurope.cloudapp.azure.com:7049/NAV/dev/apps?SchemaUpdateMode=synchronize
[2018-02-19 20:35:08.96] The request for path /NAV/dev/apps?SchemaUpdateMode=synchronize failed with code 422. Reason: Ambiguous match found.

The Pre-Compiler in VScode has no errors and creates the Extension. The event log of the Service Tier (Get-NavContainerEventLog) doesn't says anything.

What can I do to find out, what the problem is?

Metadata

Metadata

Assignees

Labels

input-neededinvestigateThe issue requires further investigation to determine if this is a product bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions