nrf Connect SDK 2.0.0 no more installabale in nrf Connect for Desktop

[Jones_swDev]

We are currently starting a project with a nordic chip. We want to work with the newest SDK (2.x.x). We saw the new SDK 2.0.0 in the nrf Connect for Desktop Toolchain Manager a few weeks ago. But now we didn't see it anymore. We tried on a few differen Pc's. We all have the newest version of the nrf Desktop ( v3.11.1) an the newest Version of the Toolchain Manager (v1.1.3).

Is there an issue with the newest SDK, that it was locked for use at the moment?

[Karl Ylvisaker]

Hello,

That is very strange indeed - v2.0.0 has not been removed from the Toolchain Manager. Did you see this on machines where you newly installed the nRF Connect SDK desktop application?
Could you share with me your system report? You can generate one from Toolchain Manager -> About -> Create system report.

Best regards,
Karl

[Jones_swDev]

Fullscreen nrfconnect-system-report-2022-07-18T08-44-57.984Z.txt Download

# nRFConnect System Report - 2022-07-18T08-44-57.984Z

- System:     LENOVO 20NKS16Q00
- BIOS:       LENOVO LENOVO - 1140
- CPU:        1 x AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx 2.3 GHz 8 cores (4 physical)
- Memory:     10.7 GB free of 21.9 GB total
- Filesystem: C: (NTFS) 399.1 GB 52.2% used

- OS:         Microsoft Windows 10 Enterprise (10.0.19044) Windows ia32

- Versions
    - kernel: 10.0.19044
    - git: 2.29.1.windows.1
    - node: 14.16.0
    - python: 
    - python3: 
    - nrf-device-lib-js: 0.4.11
    - nrf-device-lib: 0.11.8
    - nrfjprog DLL: 10.15.4
    - JLink: JLink_V7.58b

- Connected devices:

[Karl Ylvisaker]

Thank you for providing the information.
The only thing that sticks out to me is that it finds no python or python3 instance in your path.
Could you confirm that this behavior was seen on multiple PCs with new installations of nRF Connect SDK for desktop? Are they all located in Germany?

We have had issues previously with corporate firewalls blocking the Toolchain Managers access to the source. Could you possibly try this on another network, or with the firewalls disabled for the nRF Connect SDK for desktop application, to see if this could be the root cause of the issue?

Best regards,
Karl

[Jones_swDev]

I don't know why python has now version in this document. In Visual Studio Code, there is no problem with the 1.9.1. At my colleagues Pc there is python found corectly. So the issue is not coming from there.
The Thing is, we allready saw the 2..0.0 version in the toolchain mangaer ago, so i would assume, that the network is not the problem here. We both could also update the toolchain manager at the end of last week....

[Karl Ylvisaker]

Jones_swDev said:

I don't know why python has now version in this document. In Visual Studio Code, there is no problem with the 1.9.1. At my colleagues Pc there is python found corectly. So the issue is not coming from there.

I am not sure why it is not found ether, but I concur that this likely does not have anything to do with the issue we are debugging in this ticket - I just thought I should mention it, but if v1.9.1 functions as normal there is no issue with this.

Jones_swDev said:

The Thing is, we allready saw the 2..0.0 version in the toolchain mangaer ago, so i would assume, that the network is not the problem here. We both could also update the toolchain manager at the end of last week....

The network requirements, criterias, or conditions might have been changed by your IT department without you knowing it.

Karl Ylvisaker said:

Could you possibly try this on another network, or with the firewalls disabled for the nRF Connect SDK for desktop application, to see if this could be the root cause of the issue?

Could you give this a try, and see if you then are able to see the v2.0.0?

Additionally, could you confirm that all the PCs you have seen this issue on are on the same network / location, and that they were all new installations of the nRF Connect SDK desktop application?

Best regards,
Karl