Xcode macOS app -Zero Metal services found

I'm using Xcode 12.5.1. When I follow a swift goose tutorial for Outline view and Treeview, I've followed it exactly. It fails with...

2021-09-04 09:32:44.832345-0700 treeview1[21236:868981] Metal API Validation Enabled

2021-09-04 09:32:44.851673-0700 treeview1[21236:868981] MTLIOAccelDevice bad MetalPluginClassName property (null)

2021-09-04 09:32:44.853029-0700 treeview1[21236:868981] +[MTLIOAccelDevice registerDevices]: Zero Metal services found

When I download swift goose's project code from GitHub, it works without any error.... The only thing I can think of is (1) When I set Xcode for a new project using macOS and app, I'm missing something, even though it basically looks all the same. (2) Something I'm missing in my Xcode set up due to the fact I've got the "free" Xcode verses developer? Something linking behind the scene's? Is there a difference?

  • O.K., this is amazing and I still don't believe it... My project continues to give the above output on the debug screen. But what solved the problem was on the StoryBoard I increased the size of the bottom window, rearranged the TableView and Buttons, then it worked????

  • I'm glad you could get it working! Still, it sounds like this is a bug, Feel free to report it on Feedback Assistant.

  • I have the same problem when I'm using the macOS 11.4 (20F71), Xcode 12.5.1 (12E507) or Xcode-beta 13.0, MacBook Pro (Retina, 13-inch, Mid 2014).

    But the same code work on macOS 10.14.6, Xcode 10.1 (10B61), MacBook Pro (Retina, 13-inch, Early 2015).

Add a Comment

Accepted Reply

Can you share the source code for your project? Also what Mac and OS version are you running your project on?

  • The Mac is a MacMini running an intel i7 with 32G ram. The OS version is Catalina 11.5.2. Xcode is 12.5.1. The tutorial video is on YouTube by "swift goose" at https://youtu.be/tG5GecFNmbQ. About the only thing I was unable to follow was when he set up Xcode create a new Xcode project. What I did was create a new Xcode project "Choose Template", macOS, and App then create project... I called it a different name, but otherwise the files and structure look identical. I've followed "swift goose's" video carefully four times now, and get the same results. It just doesn't display on the OutlineView window, and gives the above error. When I down load his code from "GitHub", it compiles and runs without the error. I've gone over pretty much everything on the StoryBoard, compiler settings, etc., etc., and they look the same. I'm going to try one more time creating a new project, but then copy/paste his files and use his StoryBoard, plists, etc.... I'd think maybe I have a corrupted Xcode environment, but then "swift gooses" code compiles and runs... ? I can tar ball and send my code to you if you want to give me an email or somewhere to send it too, but it might be a bit much to put here. (Your thoughts? Or should I just put it up here?, if it's an error on how Xcode is set, then just the code might not show the problem)... I'm a newbie to these forums and I don't know what's considered O.K. or not, or the amount of info? Thanks in advance - jrh69

  • No problem, could you upload your project to GitHub/gitlab/etc and paste the link here? Also please provide the link for the swift goose's working version on GitHub. Alternatively, you can file a bug report on feedback assistant and attach your project to that, then reply with the feedback ID. I would suggest the first option for now since this is potentially an easy fix, if we can see what is different between your project and the one that works.

  • Also the amount of info you posted is fine :) Typically we'd like to know what hardware, OS, and Xcode version you used, along with any errors you encounter and a link to the project.

Replies

Can you share the source code for your project? Also what Mac and OS version are you running your project on?

  • The Mac is a MacMini running an intel i7 with 32G ram. The OS version is Catalina 11.5.2. Xcode is 12.5.1. The tutorial video is on YouTube by "swift goose" at https://youtu.be/tG5GecFNmbQ. About the only thing I was unable to follow was when he set up Xcode create a new Xcode project. What I did was create a new Xcode project "Choose Template", macOS, and App then create project... I called it a different name, but otherwise the files and structure look identical. I've followed "swift goose's" video carefully four times now, and get the same results. It just doesn't display on the OutlineView window, and gives the above error. When I down load his code from "GitHub", it compiles and runs without the error. I've gone over pretty much everything on the StoryBoard, compiler settings, etc., etc., and they look the same. I'm going to try one more time creating a new project, but then copy/paste his files and use his StoryBoard, plists, etc.... I'd think maybe I have a corrupted Xcode environment, but then "swift gooses" code compiles and runs... ? I can tar ball and send my code to you if you want to give me an email or somewhere to send it too, but it might be a bit much to put here. (Your thoughts? Or should I just put it up here?, if it's an error on how Xcode is set, then just the code might not show the problem)... I'm a newbie to these forums and I don't know what's considered O.K. or not, or the amount of info? Thanks in advance - jrh69

  • No problem, could you upload your project to GitHub/gitlab/etc and paste the link here? Also please provide the link for the swift goose's working version on GitHub. Alternatively, you can file a bug report on feedback assistant and attach your project to that, then reply with the feedback ID. I would suggest the first option for now since this is potentially an easy fix, if we can see what is different between your project and the one that works.

  • Also the amount of info you posted is fine :) Typically we'd like to know what hardware, OS, and Xcode version you used, along with any errors you encounter and a link to the project.

Some more info...This is indeed a bug in Big Sur, but should be benign. It should be fixed in recent Monterey betas.