Artifactory 7.36.1 Cloud

JFrog Release Information


Released: 13 March, 2022

Cloud Only

Artifactory 7.36.1 is Available as a Cloud Version


Artifactory as Your Symbol Server

A Symbol Server stores the .PDB files and binaries for all your public builds. These are used to enable you to debug any crash or problem that is reported for one of your stored builds. Both Visual Studio and WinDBG know how to access Symbol Servers, and if the binary you are debugging is from a public build, the debugger will get the matching PDB file automatically.

From Artifactory 7.36.1, you can benefit from the following advanced Symbol Server features:

  • Publishing while indexing your Symbol packages to Artifactory from your NuGet Client v3 together with your NuGet packages or as separate Symbol packages

  • Resolving Symbol files (.pdb) from virtual and local repositories in the JFrog Platform

  • Resolving Symbol files from remote proxies. For example,

  • Debugging the Symbol files hosted on Artifactory using the Visual Studio debugger tool.

Note that prior to Artifactory 7.36.1, Symbol Server support was limited to setting Artifactory as a remote Proxy for Symbol files that were hosted as Generic packages in Artifactory.

Resolved Issues

JIRA Issue



Fixed an issue whereby, the term 'Federated' was mistakenly displayed in the context of the Summary Storage page and was not relevant to this display view.


Fixed an issue whereby, zero milliseconds were not being displayed in the Request log.


Fixed an issue whereby, Copying or moving artifacts to a project set with a limit quota, were blocked if the storage quota limit has been exceeded.


Fixed an issue whereby, clicking on the 'Test Mail' Button sent an Incorrect HTML response when a Base URL was configured.

Fixed an issue, whereby downloads from 'URL to File' on the packages subfolder level failed in the webUI.

Fixed an issue whereby, the Storage quota limit was not enforced when using copying or moving content.

Fixed an issue whereby, users failed to upload files to Azure Cloud due to a temp file write to an incorrect path in the filesystem where there is no user permission.