If the UI path works, but Hammer/API does not, then it could definitely share the same underlying cause with the other issue you linked to.
Regarding that other issue, we have not yet started working on it, but it is on our internal board for our current release cycle with “must fix” priority, so we will work on it soon. I think your best bet is to wait for that fix.