Unless there is some special requiremnets on bbox and maxResolution values (which is not clearly documented) this can happen in getKey function in GoogleDisk.py
grid can have volues
(0.7022093750000402, 1.2695687499997277)
and for tile.y = 0 one will get
int(1.2695687499997277 - 1 - 0)
that leads to 0 but apparently should be 1 becuase there are two rows of tiles. For tile.y = 1
int(1.2695687499997277 - 1 - 1)
leads again to 0 that causes the previous file is overwritten.
Unless there is some special requiremnets on bbox and maxResolution values (which is not clearly documented) this can happen in getKey function in GoogleDisk.py
grid can have volues (0.7022093750000402, 1.2695687499997277) and for tile.y = 0 one will get int(1.2695687499997277 - 1 - 0) that leads to 0 but apparently should be 1 becuase there are two rows of tiles. For tile.y = 1 int(1.2695687499997277 - 1 - 1) leads again to 0 that causes the previous file is overwritten.
For most cases this could be solution.
But if grid[1].is_integer() the current formula is correct.