Skip to content
Back

Swift SDK 13.2.2: Still getting ServiceContextModule linker errors

  • 0
  • 3
  • Apple
zkqrxy
20 Oct, 2025, 15:10

Hey team - I'm still getting ServiceContextModule linker errors even after updating to SDK 13.2.2.

Error:

  • Undefined symbol: static ServiceContextModule.ServiceContext.current.getter
  • Undefined symbol: static ServiceContextModule.ServiceContext.topLevel.getter
  • Linker command failed with exit code 1

Environment:

  • SDK Version: 13.2.2 (exact version via SPM)
  • Xcode: 16.2
  • Platform: iOS 17.0+
  • Installation: Swift Package Manager

What I've tried: ✅ Updated to 13.2.2 after seeing PR #45 was merged ✅ Removed all packages and re-added fresh ✅ Reset package caches (File → Packages → Reset Package Caches) ✅ Resolved package versions ✅ Cleaned DerivedData multiple times ✅ Verified no duplicate files in compile sources ✅ No manual references to AsyncHTTPClient or ServiceContext in my code

The issue persists. Is there something else needed for 13.2.2 to work, or is the fix incomplete?

Happy to provide more details if needed! 🙂 thank

TL;DR
Users experiencing linker errors with the Swift SDK 13.2.2 after trying various versions. Attempts at cleaning and updating did not resolve the issue across different versions. User is asked to provide a minimal test project with the Appwrite SDK for further investigation.
20 Oct, 2025, 16:01

<@520707786305306626> hi can you mention the last version that works by downgrading?

20 Oct, 2025, 17:11

Thanks for responding!

Honest answer: I'm not sure ANY version worked cleanly for me. Here's what happened:

Timeline:

  • Started with 13.2.1 → Got ServiceContextModule errors
  • Tried 13.1.0 → Still got linker errors (different ones)
  • Tried 13.0.0 → Had issues
  • Updated to 13.2.2 after seeing your PR #45 → Same ServiceContextModule errors persist

The confusing part: We did a "nuclear clean" multiple times (deleted DerivedData, reset SPM caches, removed/re-added packages) but the ServiceContext linker errors kept appearing across versions.

Is it possible there's a platform-specific issue? I'm on:

  • Xcode 26.0.1
  • macOS Sequoia 15.6.1
  • Building for iOS 17.0+ target

Would it help if I created a minimal test project with just Appwrite SDK to isolate the issue?

20 Oct, 2025, 17:12

Thanks for the detailed answer

This is the first time we are hearing about this error and since no version has worked for you I think something might be off in your usage. Please do share a reproducible example 🙏

1
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more