Macros cannot be expanded when using cache

Thanks for reporting this @JaroVoltix. We added it to the list of issues to look into.

Hi. I ran into this issue as well and I wonder if it will be addressed soon. I started using Mockable, https://github.com/Kolos65/Mockable.git, and if I cache this dependency I cannot expand the macros.

I also found a defect which is more serious, not sure if it is Tuist or Mockable, but when I use Mockable in a SPM package to create mocks, and try to import the Mock generated classes from the SPM module in another target (main app for example) the classes are not found, even if they are generated with public access control. I will try to make a project sample and create another issue.

met this issue too, it is quite annoying by choosing between the macro expansion and binary cache @pepicrft do we have some conclusion for this?

I haven’t been able to looked into it yet. My hunch is that it’s a bug in Xcode’s editor when the Swift Macro is provided as a compiled executable (to confirm). If that’s the case, I’ll have to file a radar and provide an example project for Apple to look into the issue.

@mihaicris-adoreme could it be that you are missing the MOCKING compiler directive that that macro requires? We are using it in Tuist, and we haven’t encountered any issue.

We have the same problem and had to pause macro integration as we prefer to use cache. @pepicrft were you able to see if it was a problem with the xcode editor?

Hi, @JaroVoltix. I’m Dosu, and I’m helping the tuist team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that Swift macros fail to expand in Xcode when using Tuist cache, with the “Expand macro” option disappearing after caching.
• The problem occurs on macOS 14.1, Tuist 4.3.4, and Xcode 15.2.
• Other users have confirmed the issue and expressed frustration over the trade-off between macro expansion and binary caching.
• A maintainer suspects this might be an Xcode editor bug related to macros as compiled executables and is considering filing a radar with Apple.
• The issue is still under investigation with no resolution so far.

What’s Next:

• Please let me know if this issue is still relevant with the latest version of Tuist by commenting here to keep the discussion open.
• Otherwise, I will automatically close this issue in 7 days.

Thanks for your understanding and contribution!

This is still relevant with Tuist 4.78.0.