nRF Programmer Infinite Loading Loop

[CSC-Sendance]

Since several weeks, the NRF Connect for Deskotp's programmer application (v3.0.4) is stuck in an infinite loading loop, as was the toolchain manager previously ( see https://github.com/NordicSemiconductor/pc-nrfconnect-toolchain-manager/pull/183 ).

Operating system: Windows 11 Pro (22H2)

I have described the exact issue on Github but without response, see https://github.com/NordicSemiconductor/pc-nrfconnect-programmer/issues/329 

It seems bootstrap fails to load the application context, as described to be fixed in the toolchainmanager (see https://github.com/NordicSemiconductor/pc-nrfconnect-toolchain-manager/commit/951116bfc9a57f0bc49fa6d683585f049c0ec58b).

Other solutions tried:

- reinstalling programmer and connect

- execute as administrator

- execute in Windows 7 compatibility mode

I'd appreciate any workaround suggestions or, even better, a patch. 

[Øyvind]

Hello, 

I'm not able to reproduce on mine or a colleagues computer. I will forward to our developers to have a look at the github issue that you have registered and get back to you.

Kind regards,
Øyvind

[CSC-Sendance]

Thanks for the rapid response. I also just tested with the Bluetooth Low Energy App (4.0.1), Direct Test Mode (2.0.3) and Getting Started Assistant (v2.1.0) and see the same behavior as with the programmer (also confirmed by the chrome console output that you can see with ctrl+shift+I).

[Øyvind]

There is a known bug where the use of special characters in username i.e. C:\Users\<user>\AppData\Local\Programs\nrfconnect  The SW team informs me that they are working on a fix, however, the current workaround is to create a new user without special characters. 

Can you confirm that this is the case on your side?

[CSC-Sendance]

I can confirm this, while not being a very nice solution, works. Maybe an option for a workaround for the future would be to allow system-wide installations instead of user-specific ones.  Thanks for your help!

[Øyvind]

Yes, the team is aware and working on a better solution. Thanks for confirming the workaround. 

Kind regards,

Øyvind