Closed josh150 closed 2 years ago
Sorry for the delay here. I haven't had a chance to use SPM a lot, so there could be issues there. Is a change needed?
I haven't looked into it any further since the original post. I created a fork and applied that naming update as a workaround. Not sure if that is a fix you can apply for everyone. It definitely feels like a bug within SPM itself.
I ran into this while trying to use Thread Sanitizer with my app tests. It also happens if you open the package directly, add the tests to the dynamic scheme, and enable Thread Sanitizer.
Seems like it could be a bug with SPM itself.
Update: Was able to work around by forking and then setting the "Resolver" target to
.dynamic
and referencing that instead of "Resolver-Dynamic".