Build Error After Updating SDK

RTC · ‎05-14-2025

After trying to update the SDK via SPM, I am getting a build error with cmark-gfm. This package seemed to be added as part of the ArcGIS Maps SDK for Swift Toolkit update along with the Swift Markdown package.

I have tried removing and reinstalling app packages and a few other thing but noting seems to work. If I revert back to SDK version 200.5, I do not have any issue, only from 200.6 and up.

Ting · ‎05-15-2025

It's a bit hard to tell what is the problem… might be an issue with Swift Package Manager. The 2 things I would suggest are:

- Can you try create a new app project with 200.6.0 toolkit and see if it compiles?

- If it compiles, can you try cleaning out the Derived Data folder, or the artifacts folder for the specific app project? So the Swift Packages would have a clean slate to begin with.

The package involved is a dependency of https://github.com/swiftlang/swift-markdown which we added during 200.6 release.

RTC · ‎05-15-2025

Yes, if I start with new project it works only when I try to update an existing project do I get the errors.

RyanOlson1

What version of Xcode are you using? If you start a clean project and add 200.5, then upgrade that project to 200.6 does it reproduce the issue? Do you have a reproducible case you can get to us?

RTC

I am using Xcode Version 16.3 (16E140). If I start with a blank project on 200.5 then update, it works. I will see if I can create a simple project that recreates the issue.

RTC

I was trying to create a new project but keep getting this error now and I can't seem to load any version of the SDK.

Ting

Thanks for reporting. We are seeing this issue and working on fixing it. For now you can add a dependency to the main branch. Sorry for the inconvenience!

RTC

Hello Ting,

I can't seem to add it no matter what I try. Is this something that will be resolved soon? I am stuck as my project now does not have any version of the dependency and I can get one to download via SPM.
What do you mean by "For now you can add a dependency to the main branch."

Ting

Yes, we are actively working on it. Due to a mistake, some commit history was messed up, and it appears to affect the tagged release.

A temporary workaround is to select "Branch" as Dependency Rule in SPM, and type in "main" to use the main branch to add the package. Again, sorry for the inconvenience - I'll let you know as soon as we fix it.

RTC

Thanks Ting!