No luck getting Source Link to work with Cloud hosted Bitbucket

Our code is stored on Bitbucket’s hosted platform. We’re attempting to debug private NuGet packages that we are the author of.

For the package that I’m testing, I’ve set the following in its .csproj:

  <PropertyGroup>
    <ContinuousIntegrationBuild>true</ContinuousIntegrationBuild>
    <EmbedUntrackedSources>true</EmbedUntrackedSources>
    <IncludeSymbols>True</IncludeSymbols>
    <PublishRepositoryUrl>true</PublishRepositoryUrl>
    <SymbolPackageFormat>snupkg</SymbolPackageFormat>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.SourceLink.Bitbucket.Git" Version="1.1.1">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
  </ItemGroup>

On the consuming end, I’ve ensured that symbols are loading as well unchecked Enable Just My Code and checked all options for Enable Source Link support and Enable source server support.

I’m attempting to access the code for a call in the callstack that lives in the nuget package. When I do so, it’s getting a 404 when it attempts to access the file using http://api.bitbucket.org. When I try to access the file outside of the API via https://bitbucket.org, the path that it’s using works.

It would appear to be some sort of authentication issue, but I’m not certain how to troubleshoot that, as I don’t know which credentials are being passed into the API, nor am I ever prompted for credentials. We are using Bitbucket with 2FA and SSH, as is required to utilize their CI pipelines anymore.

Can you provide guidance on where to go from here?

[tmat]

@chuckries Authentication issue.

[mdemler]

I didn’t check with them, but I believe it’s all internal to them, so they’re avoiding the HTTPS overhead in their pipeline environment. All other public access is over HTTPS.