Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

appSyntax.json Warning message? #4849

Closed
GreatScott000 opened this issue Apr 5, 2019 · 11 comments
Closed

appSyntax.json Warning message? #4849

GreatScott000 opened this issue Apr 5, 2019 · 11 comments

Comments

@GreatScott000
Copy link

@GreatScott000 GreatScott000 commented Apr 5, 2019

All of a sudden today I have this warning message when I start VS Code. Where is this coming from?

It seems to only come up if I have app.json (1 or more as I have 6 extensions in my workspace), close VS Code with app.json open (unmodified) in the editor and then re-open VS Code. It also has appeared when I do a build (Ctrl+Shift+B) with an app.json open.

FYI, VS Code 1.33 was installed today.

String is not a URI: URI with a scheme is expected.

{
"resource": "/c:/Users/todd.scott/.vscode/extensions/ms-dynamics-smb.al-3.0.115791/syntaxes/appSyntax.json",
"owner": "generated_diagnostic_collection_name#0",
"severity": 4,
"message": "String is not a URI: URI with a scheme is expected.",
"startLineNumber": 2,
"startColumn": 11,
"endLineNumber": 2,
"endColumn": 44
}

VS Code Information

Version: 1.33.0 (user setup)
Commit: 0dd516dd412d42323fc3464531b1c715d51c4c1a
Date: 2019-04-04T15:14:28.026Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

AL Language Information

Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 3.0.115791
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al

@JohanStenberg100

This comment has been minimized.

Copy link
Contributor

@JohanStenberg100 JohanStenberg100 commented Apr 5, 2019

Hi @GreatScott000, thanks for filing this issue. This seems to be a VS Code issue, but we will further investigate and determine how to proceed.

@konysh

This comment has been minimized.

Copy link

@konysh konysh commented Apr 8, 2019

I had the same problem when I had 2 launch specifications. When I removed one of them it works. Just tried.

@TheDenSter

This comment has been minimized.

Copy link
Contributor

@TheDenSter TheDenSter commented Apr 12, 2019

Same issue here
image
Freshly updated Docker image, freshly updated navcontainerhelper, and installed the vsix from the container.

F5 or Ctrl+F5 are not responding. It builds the app file, but it seems to just ignore the publish command. The 'compilation started' flashes across the output window and then it blacks out, and then nothing further happens.

VSCode info:
Version: 1.33.1 (system setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.14393

AL version (from the vsix in the container)
image

BC info:
14.0.29530.29573 + Application 31259 (GB Dynamics NAV 14.0)

@michielhageman

This comment has been minimized.

Copy link

@michielhageman michielhageman commented Apr 13, 2019

Same here guys. Try to publish my 'old' ;-) BC130 apps to a brand new BC140 instance.
AL version: 3.0.106655
BC version: platform 14.0.29530.0 + application 29537 (NL Dynamics NAV 14.0)

@davmac1

This comment has been minimized.

Copy link

@davmac1 davmac1 commented Apr 15, 2019

I am getting the same error with a new never published extension for NAV 2018 CU10 - AL 0.12.17720.
The id is a GUID, but the error implies it is expecting a web address.

@MajorBarf

This comment has been minimized.

Copy link

@MajorBarf MajorBarf commented Apr 16, 2019

Getting this error with an existing extension that was previously OK before VS Code 1.33.0 was installed. I'm publishing to a local database using Windows authentication. The error only appears if you open the app.json file so you can workaround by saving app.json, then restart VS Code and make your AL changes without touching app.json again.

Found that will still publish the extension despite this message but will not open the client (launch.json error) - which means that you can't use the debugger!!!

@GreatScott000

This comment has been minimized.

Copy link
Author

@GreatScott000 GreatScott000 commented May 21, 2019

Issue continues to occur on the lastest public versions of VS Code (1.34) and AL Extension 3.0.1.126610

@bbrown5962

This comment has been minimized.

Copy link

@bbrown5962 bbrown5962 commented Jun 6, 2019

I am using VS code 1.35 and the issue still seems to be happening.

@tinfister

This comment has been minimized.

Copy link

@tinfister tinfister commented Jun 7, 2019

Same here. Any info when will this be fixed?

@DEDhead

This comment has been minimized.

Copy link

@DEDhead DEDhead commented Jun 21, 2019

You can get around the issue by putting any valid URI in the "id" field in the appsyntax.json file. I simply copied the value from the "$schema" field into the "id" field and saved the file. The extension then builds without error, publishes and launches the browser.

@atoader

This comment has been minimized.

Copy link
Member

@atoader atoader commented Aug 9, 2019

This will be fixed for the Fall 2019 release.

@atoader atoader added this to the October 2019 milestone Aug 9, 2019
@atoader atoader closed this Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.