Hey there, @ArjoNagelhout - looks like this issue is a duplicate of one reported here: Xcode Warning
See response there.
