This is probably a bug in tensorflow-metal 0.2.0. The same error occurred in the environment where tensorflow-metal 0.2.0 was installed. If you install tensorflow-metal 0.1.2 as shown below, the error will no longer occur. pip install tensorflow-metal==0.1.2