Cannot Parse Debug Map when trying to build?

[elsoqo]

Hello,

One of us is having a strange issue building to iOS, and I’m hoping someone can help us out.  

We both have the same versions of Corona and Xcode, but I myself can build just fine.  But they are getting this error whenever they try building:

“ERROR: Builder Failed, cannot parse the debug map for *insert directory for project on computer* : is a directory.”

I’ve tried looking up anyone else who’s had these issues, but they all seemed to be related to Xcode projects… we have just been using Corona’s latest daily build for building.  Any help is appreciated.

[rob]

Who is “we” and they?

What version of Corona are you using?

Are you doing Simulator Builds or Xcode/Enterprise builds?

Can you paste the entire build message?

I’ve never seen that message before.

Rob

[elsoqo]

Sorry it took a while to reply, but they were having issues with their computer… was hoping that was part of the issue they’re having, unfortunately they are still running into it after having it fixed.

To answer the questions: 

‘We’ as in me and the person I work with who typically handles building/publishing.  And ‘they’ as in the not me version of that.

Like I said, we’re using the latest daily build, so we’re both using build 3086.  And again, we are just doing Corona builds… when I’ve looked up resolutions to this issue I’ve only seen people who’ve experienced this in Xcode, so the solution had been to take certain steps within Xcode… typically from what I’ve seen, people who’ve encountered this issue resolved it by cleaning the project in Xcode.    

[elsoqo]

Here’s the messages we’re getting when building (all blacked out parts are just the directory/appname bits)

https://www.dropbox.com/s/ggcky65z4r1rlvu/new10.png?dl=0

https://www.dropbox.com/s/zggjciq4gmfgry9/new11.png?dl=0

[rob]

I appreciate the screen shots, but it probably would have been more helpful to not have blacked out the paths. Sometimes the issue might be related to a weird character in the the path somewhere. Copy and pasting text from the console would have been preferable to the screen shots, so that we could copy and paste in conversations with our engineers.

I’ll see what they can make out of this error.

Rob

[rob]

Do you by any chance have two copies of your app in the same directory?

Are you by any chance writing your build to your project directory?

Does anything in this post ring a bell?  https://stackoverflow.com/questions/36268340/xcode-cannot-parse-the-debug-map-for-is-a-directory

Perhaps what would help is to post a complete console log of the build without any privacy edits. If you feel that the information there is confidential, then send an email to support AT coronalabs.com with that information.

Also, we would like for you to open up a terminal window, do a cd command to your project folder and run an: 

ls -lR 

command and send that output as well.

Thanks

Rob

[rob]

Who is “we” and they?

What version of Corona are you using?

Are you doing Simulator Builds or Xcode/Enterprise builds?

Can you paste the entire build message?

I’ve never seen that message before.

Rob

[elsoqo]

Sorry it took a while to reply, but they were having issues with their computer… was hoping that was part of the issue they’re having, unfortunately they are still running into it after having it fixed.

To answer the questions: 

‘We’ as in me and the person I work with who typically handles building/publishing.  And ‘they’ as in the not me version of that.

Like I said, we’re using the latest daily build, so we’re both using build 3086.  And again, we are just doing Corona builds… when I’ve looked up resolutions to this issue I’ve only seen people who’ve experienced this in Xcode, so the solution had been to take certain steps within Xcode… typically from what I’ve seen, people who’ve encountered this issue resolved it by cleaning the project in Xcode.    

[elsoqo]

Here’s the messages we’re getting when building (all blacked out parts are just the directory/appname bits)

https://www.dropbox.com/s/ggcky65z4r1rlvu/new10.png?dl=0

https://www.dropbox.com/s/zggjciq4gmfgry9/new11.png?dl=0

[rob]

I appreciate the screen shots, but it probably would have been more helpful to not have blacked out the paths. Sometimes the issue might be related to a weird character in the the path somewhere. Copy and pasting text from the console would have been preferable to the screen shots, so that we could copy and paste in conversations with our engineers.

I’ll see what they can make out of this error.

Rob

[rob]

Do you by any chance have two copies of your app in the same directory?

Are you by any chance writing your build to your project directory?

Does anything in this post ring a bell?  https://stackoverflow.com/questions/36268340/xcode-cannot-parse-the-debug-map-for-is-a-directory

Perhaps what would help is to post a complete console log of the build without any privacy edits. If you feel that the information there is confidential, then send an email to support AT coronalabs.com with that information.

Also, we would like for you to open up a terminal window, do a cd command to your project folder and run an: 

ls -lR 

command and send that output as well.

Thanks

Rob