Skip to main content
Graduate
October 18, 2025
Solved

"An error occurred while synchronizing metadata." on VS Code MacOS 26 Aarch64

  • October 18, 2025
  • 15 replies
  • 2643 views

Just upgraded to the latest version of STM32Cube for VS Code extension (3.6.4) and now the extension stopped to work. I've tried reinstalling the extension pack several times. Every time after the bundle was installed an error show up saying "An error occurred while synchronizing metadata. Please try run "STM32Cube: Install prerequisite bundle" and "STM32Cube: Synchronize pack list". Or work offline."
Running "STM32Cube: Install prerequisite bundle" from the VS Code command palette will result in a message saying "No STM32Cube bundle to install", subsequently running "STM32Cube: Synchronize pack list" will return the original metadata synchronization error.

I checked my HOME/Library/"Application Support"/stmcube/ directory, the bundle/ folder seems to contain what I expected, things like cmake, gnu-gdb-for-stm32 or the stink-gdbserver, etc. However, the packs/ folder is empty, not sure if that's the problem. 

I checked the output log of STM32Cube Core and found the following:

```
[Info] 'cube pack sync' exited with signal null [1]
[Error] Failed to synchronize PDSC metadata: Syncing metadata information /Users/poshengcheng/Library/Application Support/stm32cube/packs
Snapshot is already up to date
Syncing online metadata information /Users/poshengcheng/Library/Application Support/stm32cube/packs
Error during metadata sync: Error: Unexpected close tag
Line: 4
Column: 117
Char: >
```
Additionally, after I selected a MCU device in "Setup STM32Cube Project(s)", downloading the supporting packs for the specified device always fails. The following message is from the output log of STM32Cube CMake Build:
```
2025-10-17 22:58:45.028 [Info] Pack STMicroelectronics.stm32l4xx_dfp.1.1.0 (1/1)


2025-10-17 22:58:48.060 [Info] Unable to install pack STMicroelectronics.stm32l4xx_dfp.1.1.0

2025-10-17 22:58:48.061 [Info] Error during installation: Error: Could not fetch content of pack-URL: https://developer.st.com/st-pack-server/api/v1/pack/STMicroelectronics.stm32l4xx_dfp.1.1.0.pack, got: 503 - Service Unavailable

2025-10-17 22:58:48.069 [Info] 'cube pack install STMicroelectronics.stm32l4xx_dfp.1.1.0' exited with signal null [1]
2025-10-17 22:58:48.071 [Error] Failed to download pack 'STMicroelectronics.stm32l4xx_dfp.1.1.0'. Please check your setup and try again (via command line 'cube pack install <pack_id>' or via command palette 'STM32Cube: Restore STM32Cube CMake projects configuration')
```
So far I've only been able to build the project but attempts to debug have failed since the stm32cube doesn't seem to be able to setup the project with the selected device. 
    This topic has been closed for replies.
    Best answer by Julien D

    All,

    Fyi the infrastructure has been fixed, cube pack sync should be ok now.

    Apologies for the inconvenience.

    15 replies

    ST Employee
    October 20, 2025

    All,

    We acknowledge the issue, technical Teams are analyzing it. 

    No bundles nor packs were published late last friday, neither during the weekend. 

    We will post here any further information.

    Visitor II
    October 20, 2025

    I thought there was something wrong with my configuration.

    Because I just started learning to write stm32 with vscode

    I hope the environment can become more mature and stable, otherwise it will be too difficult to troubleshoot errors when learning.

    ST Employee
    October 20, 2025

    @zhuxiaodics6be assured that maturity and stability is in our Team's mindset, wherever it comes to software or infrastructure.

    The issue has been localized, still working on the fix.

    Julien DAnswer
    ST Employee
    October 20, 2025

    All,

    Fyi the infrastructure has been fixed, cube pack sync should be ok now.

    Apologies for the inconvenience.

    Visitor II
    October 20, 2025

    it's back to be working, thanks.

    peter

    Graduate
    October 20, 2025

    The error message is gone!