Using the same file fixture in two different test cases produces a different file in the second one

[gkatsanos]

// first test case, passes
  it("uploading files should show the file names and no errors in the fileUpload component if valid", () => {
    cy.fixture("buggy.jpg").as("fileToBeUploaded")
    cy.get("[data-test=file-upload-button]").should("be.visible")
    cy.get("input[type=file]").selectFile("@fileToBeUploaded", { force: true })
    cy.get(".file-names").should("have.length", 1)
    cy.get(".file-names").contains("buggy.jpg")
    // cy.get("[data-test=remove-file-button]").click()
  })
// different file name, passes
  it("uploading files with invalid file types should show an error message", () => {
    cy.fixture("invalid.log").as("invalidFileToBeUploaded")
    cy.get(`[data-test="file-upload-button"]`).should("be.visible")
    cy.get("input[type=file]").selectFile("@invalidFileToBeUploaded", {
      force: true,
    })
    cy.get(".file-names").should("have.length", 1)
    cy.get(".has-error").should("be.visible")
  })
// same file name as first test, inspected in debugger and file information seems to be empty. 
  it("should include a the extra properties in the request body", () => {
    cy.fixture("buggy.jpg").as("newfileToBeUploaded")
    cy.get("[data-test=file-upload-button]").should("be.visible")
    cy.get("input[type=file]").selectFile("@newfileToBeUploaded", {
      force: true,
    })
    cy.submitForm(true)
    cy.wait("@request").then((interception) => {
      const { payload } = JSON.parse(interception.request.body)
      expect(payload.requestData.structuredFields).to.have.all.keys(
        "deliveryLocation",
        "deliveryTime",
        "quantity",
        "surfaceTreatment"
      )
      expect(payload.requestData.attachments).to.have.length(1)
    })
  })

1st test case step debugger in code :

2nd test case :

and 3rd and weird one: