Weird build bug when bundling "conflicting output resource" (SOLVED)

Questions
#1

Huh?

0 - StarOde
2018-01-13 09_59_11-Defold Editor 2.0 - StarOde.png1015Ă—129 6.37 KB

1 Like
#2

I got this a while ago when I had two of the same file in my project (unzipped a previous version into a folder). Unfortunately the error message doesn’t tell you the correct conflicting file paths . . .

2 Likes
#3

That looks like a fetch libraries or resource sync gone bad :frowning: Did you get an error message before this happened? Is it reproducible? Does it disappear if you restart the editor?

1 Like
#4

It happened because I had the dependency listed twice in the list (my deps list is quite long…) I had to delete the temp folders to get it to fully fix.

Might want duplicate checking somewhere when adding to the list / bundling to better warn although now it will be more obvious.

3 Likes
#5

Please report this on the Editor 2 issues page, or report it from within the editor itself: “Help” -> “Report issue”

2 Likes
#6

Thing is, this shouldn’t happen. We do check for exact duplicates in the dependencies list. And when “mounting” your dependent libraries into our view of available resources (what ends up in the assets tree), we explicitly check for each library if any of it’s resources would end up on a resource path already in use. If so, we skip the library entirely. What worries me is that the error seems to say you somehow ended up with two resources for the same path anyhow :confused: If this happens again, please re-report, and bonus points if you can repro it consistently :slight_smile:

3 Likes
#7

This happened to us frequently last week.
In an effort to be able to git_ignore game.project (because devs here want to have different settings in their game.project depending on what they do and we always forgot to change it back when commiting) we created a game_origin.project that was used as game.project when building on Jenkins.

This didn’t work as it seems like bob.jar read both files (I guess) and duplicates all resources paths. Thats my interpretation of it anyway.

Only bob did react on this.

1 Like
#8

@andreas.strangequest @Pkeod Aha, so this was when bundling only? I know the editor doesn’t really like multiple *.project, not a case we’ve considered properly.

#9

Not sure if exactly related, but if “name.png” and “name.atlas” are in the same root folder, this error will always occur.

2 Likes
#10

Thanks, it’s a known issue/by design. Not the same thing, but still pretty annoying :slight_smile:

2 Likes
#11

Or name.tilemap and name.atlas.

4 Likes