Setup fails on Mac with Loom 0.11-SNAPSHOT

[The-Fireplace]

When attempting to load/reload the project with IDEA on Mac, setup fails with the following error:

Could not determine the dependencies of task ':Fabric:configureClientLaunch'.
> Could not create task ':Fabric:extractNatives'.
   > Could not create task of type 'ExtractNativesTask'.
      > Could not resolve all files for configuration ':Fabric:minecraftNatives'.
         > Could not find java-objc-bridge-1.0.0-natives-osx.jar (ca.weblite:java-objc-bridge:1.0.0).
           Searched in the following locations:
               https://repo.maven.apache.org/maven2/ca/weblite/java-objc-bridge/1.0.0/java-objc-bridge-1.0.0-natives-osx.jar

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

This does not occur with a normal Fabric setup on the same machine. Tested by loading the Fabric Example Mod, which also uses Loom 0.11.

Workaround:
Switch back to Loom 0.10-SNAPSHOT.

[jaredlll08]

Can I see your full gradle log?

While I know that Fabric supports M1 Mac by default, I don't know if Forge or VanillaGradle supports it, so it is possible there is an error higher up causing issues

[The-Fireplace]

Absolutely!
By the way, this is a 2018 Mac mini, not a Mac with an M1. Let me know if you need any additional details.

Starting Gradle Daemon...
Gradle Daemon started in 1 s 446 ms

> Configure project :Common
SpongePowered Vanilla 'GRADLE' Toolset Version '0.2.1-SNAPSHOT'
Targeting Minecraft '1.18.2' on a 'JOINED' platform

> Configure project :Fabric
Fabric Loom: 0.11.32

> Configure project :Forge
WARNING: This project is configured to use the official obfuscation mappings provided by Mojang. These mapping fall under their associated license, you should be fully aware of this license. For the latest license text, refer below, or the reference copy here: https://github.com/MinecraftForge/MCPConfig/blob/master/Mojang.md, You can hide this warning by running the `hideOfficialWarningUntilChanged` task
WARNING: (c) 2020 Microsoft Corporation. These mappings are provided "as-is" and you bear the risk of using them. You may copy and use the mappings for development purposes, but you may not redistribute the mappings complete and unmodified. Microsoft makes no warranties, express or implied, with respect to the mappings provided here.  Use and modification of this document or the source code (in any form) of Minecraft: Java Edition is governed by the Minecraft End User License Agreement available at https://account.mojang.com/documents/minecraft_eula.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':Fabric:configureClientLaunch'.
> Could not create task ':Fabric:extractNatives'.
   > Could not create task of type 'ExtractNativesTask'.
      > Could not resolve all files for configuration ':Fabric:minecraftNatives'.
         > Could not find java-objc-bridge-1.0.0-natives-osx.jar (ca.weblite:java-objc-bridge:1.0.0).
           Searched in the following locations:
               https://repo.maven.apache.org/maven2/ca/weblite/java-objc-bridge/1.0.0/java-objc-bridge-1.0.0-natives-osx.jar

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 14s

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings

[jaredlll08]

So Just to confirm, using loom 0.10 can setup the project perfectly fine, but using 0.11 does not?

[The-Fireplace]

Correct

[jaredlll08]

Unfortunately not the answer you want to hear, but you may need to report this to https://github.com/FabricMC/fabric-loom since it seems to be a change that they made.

I do want to keep this open until we have more information about the issue, it could be as simple as loom injecting a repository in a way that isn't compatible with how we declare repositories on the template.

[The-Fireplace]

FabricMC/fabric-loom#621

[jaredlll08]

This has been fixed by FabricMC/fabric-loom#625