search

drmohundro / SWXMLHash

Simple XML parsing in Swift
MIT License
1.41k stars 205 forks source link

error: No such module 'SWXMLHash' #142

Closed orodri closed 7 years ago

orodri commented 7 years ago

I cloned the repository and tried running the playground however I get the following error:

Playground execution failed: error: SWXMLHashPlayground.playground:6:8: error: no such module 'SWXMLHash' import SWXMLHash ^

  • thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.3
    • frame #0: 0x0000000102bf03b0 SWXMLHashPlaygroundexecutePlayground frame #1: 0x0000000103701b5c CoreFoundationCFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK + 12 frame #2: 0x00000001036e6e54 CoreFoundation__CFRunLoopDoBlocks + 356 frame #3: 0x00000001036e65ee CoreFoundation__CFRunLoopRun + 894 frame #4: 0x00000001036e6016 CoreFoundationCFRunLoopRunSpecific + 406 frame #5: 0x0000000108b16a24 GraphicsServicesGSEventRunModal + 62 frame #6: 0x0000000104268134 UIKitUIApplicationMain + 159 frame #7: 0x0000000102bef6d9 SWXMLHashPlaygroundmain + 201 frame #8: 0x0000000106ca465d libdyld.dylib`start + 1
drmohundro commented 7 years ago

It looks like it is still working on my side, though I did have a tiny syntax error in the Playground code that I just corrected in master. Which version of Xcode are you using?

orodri commented 7 years ago

Xcode 8.3.3

Forgive me,

I was neglecting to open the Playground from within the Workspace. I thought opening the Playground by itself would work for some reason.

drmohundro commented 7 years ago

Ah, gotcha. That makes sense. Thanks for the update!

jeeva-s commented 9 months ago

hii im facing this issue in xcode Version 15.2 (15C500b) only in vs code but in xcode its working f9. How to solve this ?

drmohundro commented 9 months ago

Hi @jeeva-s, I suspect this is a slightly different problem as this issue was related to the Swift Playground. Regarding debugging, though, I suspect that the VS Code approach is using the Swift command line tools behind the scenes, though I'm not positive. Could you open a new issue and drop the details there along with the VS Code extension you're using? Also, I'd guess the extension has logs that show any command line output... those would probably help with diagnosing as well. Thanks!