Hi @eskimo - indeed that was the issue! I am certain it would be appreciated by the community if in future XCode versions, the information you just gave was provided in the error description, as it would save a lot of time & uncertainty - many thanks for your help