Not quite so. The same error occurs for me using tensorflow==2.20.0 and tensorflow-metal==1.2.0 in a Python 3.10 venv running on an M2 Max MBP.