nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pull Requests showing empty diffs

Stefan Kleist

Lately Pull-Request-View is showing files as "empty diff" on the left while correctly reporting the number of added / removed lines in the files tree.

Same problem in "old" Pull Request view.

Is this a known Bitbucket Bug? Is there a workaround to get the correct diff?

Accepted answers

All comments

pbazeliuk

We faced the same issue.
Is there any decision?

Kennedy Odife_qbw3bm

Suddenly facing this right now. Don't even know why it happens. My colleagues could view the PR correctly but I can not

Bhanu Prakash Vejju

I too faced the same issue , hard reloading(cmd+shift+R) the page worked for me.

pradipta_3jyf9l

Worked for me too @Bhanu Prakash Vejju

Juanma_lfmehd

It was failing me with Chrome, too. But with Firefox I was going fine.

I also checked that when I went to see a commit from the PR, the display worked correctly again when I came back.

Kennedy Odife_qbw3bm

Wow. Thanks @Bhanu Prakash Vejju
Worked for me. Ctrl + shift + R on Linux

John Moore_33ikdb

I am also getting this same error "Empty Diff".

Any ideas to root cause / fix?

Screen Shot 2020-06-07 at 1.51.48 PM.png

Anthony Duhaime

I am also facing the same issue.

Ctrl + shft + r didn't solve the issue for me.

zswanson

Ditto - this is happening repeatedly. We can sometimes decline the PR and try again but now we're seeing it over and over on the same changes.

zswanson

The other half of this problem is that bitbucket won't allow me to merge the PR. The commits are there, and shows the diff on the commit, but the PR interface is broken.

Robbe

As of today, we also have this problem. Hard reloading or another browser (Firefox, Safari, Chrome) doesn't fix it. Very frustrating.

Nurudeen Akindele

How did you eventually fix this then

zswanson

Deleting the bad PR and re-creating it works for me when this happens.

Simon Travancas

For anyone who has this problem in the future and ends up here, one possible cause (and what happened in my case), is that the PR has whitespace-only diff in the file, and my "PR Viewing Preferences" were set to not show whitespace changes. Changing it to show whitespace changes fixed the problem

djordje.milojevic

This doesn't seem to be the fix, the file i have issue with is .gitkeep which is empty by default, and no matter what it always stays there with the empty diff.

Ionut_m5qj65

I've started to have this problem too since today.

In my case I couldn't see the diff in any pull request, even older pull requests that were already merged.

In my case I saw that I can't see the diff as long as I have the "TikTok Pixel Helper" browser extension is enabled.

I'm not sure why it stopped working today, because I've installed that extension a few months ago.

As long as I keep that extension disabled I can se the diff.

So check your browser extensions, maybe there are other that can break displaying the diff.

Edited:

As @natashabates suggests below another solution is to set "This can read and change site data" to "When you click the extension" for the "TikTok Pixel Helper" extension.

Tammy Keefer

Same. Disabling the TikTok Pixel Helper extension solved my problem. So thank you! If that extension isn't your problem, I was also able to see the diffs if I was in an incognito window.

nick.mcphedran

Amazing thanks @Ionut - I would never have worked that out. But I was having the exact same issue - everything worked fine yesterday but today I was just getting:

Empty diff

The diff for this file is empty.

Disabled the Chrome TikTok Pixel Helper, and now works fine again! So odd, but thank you!

Sajid Iqbal_f9y7tu

Pretty unusual but this helped. thanks @Ionut

Maleesha Gunasekara

once you have this issue try to commit from the source control in the Visual Studio code then you will have to add a new or same commit message and do the push from the source control, it works for me

ankitagrawal01

// Checkout the PR branch

git checkout <pr branch>

// Checkout the affected file from base branch

git checkout origin/master -- <file path>

git commit -m "Removed empty file diff"

git push

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud