error: Unable to find module dependency: 'libcmark'

[jaygajjar-huma]

Please help prevent duplicate issues before submitting a new one:

• [x] I've searched other open/closed issues for duplicates before opening up this new issue.

Report

What did you do?

I am getting below error for xcode26 via cocoapods error: Unable to find module dependency: 'libcmark'

[itsthisjustin]

I definitely haven't tried opening this in xcode26 yet (haven't tried on any of my apps for that matter lol). Soooo if you figure out before I can take a look please update this issue. I imagine other apps will have the same error as there's nothing overly special about this one.

[MilkFoam-L]

I also encountered this problem, please solve it as soon as possible @itsthisjustin

[0xBa0]

same error +1

[carloscuba]

same error +1. It would be great if we could get this working on Xcode 26

[Best11111111111]

same error +1. It would be great if we could get this working on Xcode 26

[leson1106]

A temporary workaround is to set Explicitly Built Modules in Build Settings to No.

[ricardosvale]

same error +1

[lishanyu777]

same error +1, only set Explicitly Built Modules to No not work for me. The Down pod is depended by a remote pod.

[Cooper-Han]

same error +1

[MauricioChavesDias]

Same error +1.

Initially setting Explicitly Built Modules to No did not resolve my problem, so I had to also remove -ld_classic from the Other Linker Flags too.

[vvorlov]

It's fixed in https://github.com/johnxnguyen/Down/pull/312

[Roobt]

same error +1， Has anyone solved the problem?

[carloscuba]

Hey there, @Roobt . We were able to solve the problem by just updating our Podfile:

pod 'Down',
      git: 'https://github.com/vvorlov/Down.git'

This forked repo contains all the required changes.

[Roobt]

Hello，@carloscuba I also tried this method and cleaned up the entire project, but still reported 'Unable to find module dependency:' libcmark '

[carloscuba]

This is exactly what we did, @Roobt :

• Updated the Down pod reference (as mentioned on my previous comment)
• Upgraded from Cococapods 1.13.0 to 1.16.2 (not sure if this is required, but we did it anyway)
• Deintegrated the Pods: pod deintegrate + removed Podfile.lock (so we are ready for a "fresh install")
• Installed the Pods again: pod install

None of the other methods/alternatives worked for us, so make sure you don't have anything else on your Podfile (post_install directives) or any other mentioned Build Settings.

[Roobt]

This is exactly what we did, @Roobt :

• Updated the Down pod reference (as mentioned on my previous comment)
• Upgraded from Cococapods 1.13.0 to 1.16.2 (not sure if this is required, but we did it anyway)
• Deintegrated the Pods: pod deintegrate + removed Podfile.lock (so we are ready for a "fresh install")
• Installed the Pods again: pod install

None of the other methods/alternatives worked for us, so make sure you don't have anything else on your Podfile (post_install directives) or any other mentioned Build Settings.

I just tried all these steps once and still haven't solved my problem.