I did made a PCB and tried to run it but it failed to read data from RTC. Just to make sure where the problem is I took out working DS1302 module and replaced the IC with mine and it was not working after that, so clearly issue is within IC.
I suggest more systematic testing...
You have a known good chip and a known good board and known good software. You tested that out and I am assuming that that test was with the ESP32 such that GPIO and software is configured properly and you can keep it that way.
You have 4 suspect chips and a suspect board. One or more of your suspect chips did not work in your known good board and software (not sure that you tested all 4 of them).
Test the known good chip in the suspect board and the known good software. If that works, you can believe that the new board is ok. If it does not work, put the good chip back in the good board and if it fails, suspect that your new board has fried the chip....so you have to find out why. If the good chip still works in the good board with good software - the problem is in the 4 suspect chips.
You did not say where you got the chips and it is quite possible that they are not genuine DS->MAX->AN chips. Search on fake DS1302 and you will get the idea.
If they are not genuine, they may still work, but are out of tolerance. You may want to just get genuine chips or you may want to explore them a bit more.
If you want to explore....try them without the battery / bumping Vcc to 5V / increase the CE/RST values (same line different data sheet nomenclature). That sort of thing.
That's my thinking - hope it helps.
Good luck and let us know what you find out.
+
means "lead-free". Usually, that+
is on a separate, fourth row with maxim, though. \$\endgroup\$