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?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
The diff for this file is empty.
Disabled the Chrome TikTok Pixel Helper, and now works fine again! So odd, but thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pretty unusual but this helped. thanks @Ionut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for finding the solution! I changed the plugin to only read & change site data when clicked and it's resolved my issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, lot.
Disable Tiktok pixel extension worked for me also. yeeahhhh 👍👍
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you... Even for me disabling the Tiktok pixel extension worked fine...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also facing the same issue.
Ctrl + shft + r didn't solve the issue for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
// 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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As of today, we also have this problem. Hard reloading or another browser (Firefox, Safari, Chrome) doesn't fix it. Very frustrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How did you eventually fix this then
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also getting this same error "Empty Diff".
Any ideas to root cause / fix?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Suddenly facing this right now. Don't even know why it happens. My colleagues could view the PR correctly but I can not
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I too faced the same issue , hard reloading(cmd+shift+R) the page worked for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Worked for me too @Bhanu Prakash Vejju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow. Thanks @Bhanu Prakash Vejju
Worked for me. Ctrl + shift + R on Linux
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We faced the same issue.
Is there any decision?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.