Noticed that you're running into this while running tests. gvarandas-shop and I found that this only occurs in test suites with targets that don't have a test host. Moving our test from a test target that had no test host to one that did resulted in the test passing.
I can't explain why that is, but that's what we ended up going with.