Closed ichoosetoaccept closed 5 months ago
I think this is just an issue of the latest renaming operation I did. Should work if you just rename Two to 2.
I think this is just an issue of the latest renaming operation I did. Should work if you just rename Two to 2.
Does this work for you, locally? If so, which "Two" did you change to a "2" to get tests to run? There are quite a few "TwoFHey"'s across the repo.
I'll be able to investigate myself later, but if you already got this to work, do let me know. Thanks!
Ok take a look now. I undid my changes from before. Swift doesn't like stuff to start with a number I guess.
That seems to have helped matters a bit but I still can't get the project to build successfully. and are my current issues. TwoFHeyTests.swift imports the "module" TwoFHey but that module does not seem to exist in any package collection known to my Xcode.
Do you have the same issue with the TwoFHeyTests.swift file? I'll deal with the account and signing cert issues once this import problem is solved.
Thanks!
Can you do a project clean and make sure the tests folder is in your workspace on the left?
Cleaning resolved the account and signing cert issues!
Now the only build-breaking issue remaining is with import TwoFHey:
The tests folder is there.
Thanks for your patience on this. This is now fixed.
I tried to get this to work locally but could not.
IMHO you should get the project in a state where I can successfully run the tests stored in /2fhey/2FHeyTests/TwoFHeyTests.swift right after cloning the repo locally and opening the .xcodeproj file in Xcode.
As it stands now I get this when trying to run the tests:
Xcode is also complaining about "No such module 'TwoFHey'" in the same file.