Yes I am. It is #1 on my todo list.

Interesting. Normally that library should have been created in your SDK. You should have a file called "libSwiftCompatibility56.dylib" in your SDK directory, and it is created by the 2nd step of the migration assistant. The code that creates it is the following:

% Migration assistant (step 2, PC).cmd

		echo void _swift_FORCE_LOAD_$_swiftCompatibility56^(void^){}> "%TEMP%\swiftCompatibility56stub.c"
		set LIPO_FLAGS=
		for %%a in (arm64 arm64e) do (
			"%*\Toolchain\clang.exe" -target %%a-apple-ios7.0 -o "%TEMP%\swiftCompatibility56stub.%%a.o" -c "%TEMP%\swiftCompatibility56stub.c"
			"%*\Toolchain\ar.exe" qs "%TEMP%\libswiftCompatibility56stub.%%a.a" "%TEMP%\swiftCompatibility56stub.%%a.o" > nul 2>&1
			set LIPO_FLAGS=!LIPO_FLAGS! -arch %%a "%TEMP%\libswiftCompatibility56stub.%%a.a"
		)
		"%*\Toolchain\lipo.exe" -create -output "%*\SDK\libswiftCompatibility56.a" !LIPO_FLAGS!
		del /f /q "%TEMP%\libswiftCompatibility56stub.*" > nul 2>&1
%

This means, I bet, that you migrated your SDK using an outdated assistant. Am I right ?

Glad to hear it worked. Actually Swift support still has a limitation, but you’re not affected : mixed language targets (i.e. mixing Swift and Objective-C code in the same framework) are not yet supported. This is what I’m working on at the moment.

The Facebook SDK is the prime example I can think of. But there’s still the possibility to build a project that uses it by linking against its precompiled frameworks.