Local SDK: Failed to load. Will try over internet
Closed this issue · 10 comments
Hello,
I am behind a cooperate proxy and therefore need to load the SDK locally like explained here https://github.com/SAP/ui5-language-assistant/tree/master/examples/sap-ui5-web-server.
I got 2 SDKs running under http://localhost:3000
. (Following UI5 versions are hosted: ["/1.71.61","/1.120.4"])
When I go to http://localhost:3000/1.71.61/
I reach the SAP Website hosted locally.
I added the SAPUI5 Web Server setting for the extension, but I am unable to get it to work, I am getting the following error:
{
"label": "@ui5-language-assistant/context",
"level": "info",
"localUrl": "http://localhost:3000/1.71.61/",
"message": "Failed to load. Will try over internet.",
"time": "2024-02-13T09:07:17.759Z"
}
Complete trace after manifest initialization:
{
"DEFAULT_UI5_VERSION": "1.71.61",
"label": "@ui5-language-assistant/context",
"level": "error",
"message": "Could not read version mapping, fallback to default version",
"time": "2024-02-13T09:07:17.621Z",
"url": "https://ui5.sap.com/version.json"
}
{
"label": "@ui5-language-assistant/context",
"level": "warn",
"message": "Could not read version information. Error: Version info request has failed (https://ui5.sap.com/1.120.4/resources/sap-ui-version.json)",
"time": "2024-02-13T09:07:17.636Z",
"url": "https://ui5.sap.com/1.120.4/resources/sap-ui-version.json"
}
{
"framework": "SAPUI5",
"label": "@ui5-language-assistant/context",
"level": "info",
"message": "The following framework/version has been detected",
"time": "2024-02-13T09:07:17.639Z",
"version": "1.71.61"
}
{
"cacheFolder": "c:\\Users\\<REDACTED>\\AppData\\Roaming\\Code\\User\\globalStorage\\saposs.vscode-ui5-language-assistant\\ui5-resources-cache\\SAPUI5\\1.71.61",
"label": "@ui5-language-assistant/context",
"level": "info",
"message": "Caching UI5 resources in",
"time": "2024-02-13T09:07:17.640Z"
}
{
"framework": "SAPUI5",
"label": "@ui5-language-assistant/context",
"level": "info",
"message": "building UI5 semantic Model for framework/version",
"time": "2024-02-13T09:07:17.640Z",
"version": "1.71.61"
}
{
"label": "@ui5-language-assistant/context",
"level": "info",
"localUrl": "http://localhost:3000/1.71.61/",
"message": "Failed to load. Will try over internet.",
"time": "2024-02-13T09:07:17.685Z"
}
{
"label": "@ui5-language-assistant/context",
"level": "warn",
"message": "Could not read version information. Error: Version info request has failed (https://ui5.sap.com/1.71.61/resources/sap-ui-version.json)",
"time": "2024-02-13T09:07:17.699Z",
"url": "https://ui5.sap.com/1.71.61/resources/sap-ui-version.json"
}
{
"label": "@ui5-language-assistant/context",
"level": "info",
"localUrl": "http://localhost:3000/1.71.61/",
"message": "Failed to load. Will try over internet.",
"time": "2024-02-13T09:07:17.759Z"
}
@RuckertSolutions
Thanks for reporting.
Can you please cross check if "minUI5Version"
of manifest.json
file have similar versions. For instance:
"minUI5Version": "1.120.4"
or
"minUI5Version": "1.71.61"
Hi, thanks for the quick response.
In the manifest.json I have "minUI5Version": "1.120.4" defined (under sap.ui5.dependencies).
I tried serving both "1.71.61" (default extension version) and "1.120.4" (my min version) and each one alone, but with the same result.
For minUI5Version I tried both versions as well (it always tries to load 1.71.61 from local though, not 1.120.4).
@RuckertSolutions
can you please also cross check if you have user settings maintained.
Refer to this documentation Search for "2. Offline work"
Yes, I added the UI5LanguageAssistant.SAPUI5WebServer setting for it to use a local SDK.
settings.json: "UI5LanguageAssistant.SAPUI5WebServer": "http://localhost:3000/",
Teams or Discord? I will be off this afternoon though; will you be available tomorrow morning? Und vielen Dank fuer die Hilfe :)
Tomorrow morning - Teams. Es gibt nichts zu danken. :)
@RuckertSolutions can you please cross check is there is any proxy settings.
For details check this documentation.
If HTTP_PROXY
or HTTPS _PROXY
is set, can you remove it or try this work around
As we did not hear back from you, I'm closing this issue. Please feel free to reopen if the issue still occurs despite following the recommendations in the previous comment