Error when testing a build (SOLVED)

totebo · July 16, 2020, 10:41am

After a colleague has downloaded the project and trying to test the build (command+b) they get this error:

    java.util.concurrent.ExecutionException: clojure.lang.ExceptionInfo: unable to resolve build target from value {:FileResource "/main/screens/gameworld/atlases/game.atlas"} {:property "game_atlas", :resource-reference {:FileResource "/main/screens/gameworld/atlases/game.atlas"}}
    clojure.lang.ExceptionInfo: unable to resolve build target from value {:FileResource "/main/screens/gameworld/atlases/game.atlas"}

It happens on both their laptops (windows and mac) so it’s likely I’ve messed something up. Curiously it works fine for me. We’ve confirmed we’re on the exact same version of the game.

Any idea what could cause this? I’ve searched the forum but not found a similar error.

Edit: I found this in the source (hurrah for visible source!). But what does it mean?

    ;; If this fails, it is likely because the collection of
    ;; resource-property-build-targets supplied to this
    ;; function does not include a resource that is referenced
    ;; by one of the properties. This typically means that
    ;; you've forgotten to connect a dependent build target to
    ;; an array input in the graph.
    (throw (ex-info (str "unable to resolve build target from value "
                         (pr-str clj-value))
                    {:property (:id go-prop)
                     :resource-reference clj-value}))))

github.com

defold/defold/blob/869a87718757bdb7bfd6ed078047fa7bfb451de9/editor/src/clj/editor/properties.clj#L660


     seen-dep-build-resource-paths #{}]
(if-some [go-prop (first go-props-with-source-resources)]
  (do
    (assert (go-prop? go-prop))
    (let [clj-value (:clj-value go-prop)


          dep-build-target
          (when (resource/resource? clj-value)
            (or (build-targets-by-source-proj-path (resource/proj-path clj-value))


                ;; If this fails, it is likely because the collection of
                ;; resource-property-build-targets supplied to this
                ;; function does not include a resource that is referenced
                ;; by one of the properties. This typically means that
                ;; you've forgotten to connect a dependent build target to
                ;; an array input in the graph.
                (throw (ex-info (str "unable to resolve build target from value "
                                     (pr-str clj-value))
                                {:property (:id go-prop)
                                 :resource-reference clj-value}))))

Mathias_Westerdahl · July 16, 2020, 11:01am

Does your colleague have this file?

totebo · July 16, 2020, 12:19pm

Yes, the file is there. When it’s opened there is a “Render error” with all the .pngs marked as missing. They do exist in the file structure, so there is an issue somewhere else. I’ve recently batch edited files (search and replace) so it might have something to do with that. Digging deeper.

Edit 1: Okay, that’s a strange one. It turns out the issue was with upper/lower case. The .png files were in a folder that showed as “sugarlands” on my Mac. On everyone else’s computer (including browsing the Github repository) the folder was called “sugarLands”.

After renaming the folder first to “sugarlands_test” and committing, then to “sugarlands” and committing, it all works.

Explain that one, if you can!?

Edit 2: It turns out that Github doesn’t respect folder name case. So if a folder is renamed from “UpperCase” to “uppercase” it doesn’t change the folder name in the file structure. This one was new to me.

Erik_Angelin · July 16, 2020, 2:41pm

Added this as an issue here: https://github.com/defold/defold/issues/5019
@totebo If you have anything more to add, please do

totebo · July 16, 2020, 2:54pm

Thanks! I think I’ve said my peace. It does seem like a file system/Github issue rather than Defold, though.