waitForElementVisible and waitForElementNotVisible is returning same result in callback function.

[SDETQATestAutomation]

waitForElementVisible

√ Element <//button[@id='#####']> was visible after 22 milliseconds.
{"value":true,"status":0}

waitForElementNotVisible

 × Timed out while waiting for element <//button[@id='####']> to not be visible for 60000 milliseconds. - expected "not visible" but got: "visible" (60042ms)
    at World.<anonymous> (C:\GartnerWorkspace\cpp_framework\cppworkspace\tests\stepdefs\workspace.js:89:19) 

{"value":true,"status":0}
    × failed
      Timed out while waiting for element <//button[@id='RA_STUDIO']> to not be visible for 60000 milliseconds. - expected "not visible" but got: "visible" (60042ms)
          at World.<anonymous> (C:\GartnerWorkspace\cpp_framework\cppworkspace\tests\stepdefs\workspace.js:89:19)    
          at processTicksAndRejections (internal/process/task_queues.js:95:5)

If waitForElementVisible is returning result {"value":true,"status":0}, then for same element waitForElementNotVisible should return {"value":false,"status":0}