is TapLinx IOS SDK incompatible with Xcode 16?

[dario_sec]

Followed instruction on UG10045 released

19 August 2024

on Xcode 16 released

16 September 2024

Added also a step missing in the document:

Build Settings -> Swift Compiler -Search Paths + $(PROJECT_DIR)/TapLinxLibrary

import TapLinxLibrary returns

Compiled module was created by a different version of the compiler '5.10.0.13'; rebuild 'TapLinxLibrary' and try again:

[STRIPPED]/TapLinxLibrary/TapLinxLibrary.swiftmodule/arm64-apple-ios.swiftmodule

Cleaned Build / removed DerivedData directory and then returns:

Cannot load module 'TapLinxLibrary' built with SDK 'iphoneos17.5' when using SDK 'iphoneos18.0': [STRIPPED]/TapLinxLibrary/TapLinxLibrary.swiftmodule/arm64-apple-ios.swiftmodule

Could you please confirm compatibility with Xcode 16?

[ukcas]

Dear users of TapLinx iOS,

For compiling the library we are usin:

• swift-driver version: 1.115.1 Apple Swift version 6.0.3 (swiftlang-6.0.3.1.10 clang-1600.0.30.1)
• Target: arm64-apple-macosx15.0

Xcode Version - Version 16.2 (16C5032a)

Our Library is compatible with Xcode 16.2. We are able to integrate TapLinx Library into a swift project which runs on latest Xcode.

We try to be compatible with latest tools and environment on every TapLinx release.

Best regards,

TapLinx team

[dario_sec]

Thank you for your answer.

Are you referring to new release (2025-02-19) or previous one?

Currently trying to download new release of 

TapLinx Software Development Kit (SDK)

returns 404.

Regards,

Dario

[ukcas]

Dear dario_sec,

There are Limitations on including device specific library in iOS applications:

Using device (iOS) specific library has some limitations. The limitations include:

1. SwiftUI preview
2. simulator based debugging
3. workflows.

TapLinx SDK is such a library which supports only physical devices not simulator. Since the NFC tag reading cannot be done through simulator, it is disabled.

SwiftUI preview works with simulator features and TapLinx library supports only physical device execution we are facing issue while previewing the UI. 

For preview of UI, library can be temporarily disabled if possible:

In the first screenshort  “let manager = TLLibraryManager.shared()”  is commented under  “initializeLibraryManager()” method and we can preview the UI without any error.

  

[ukcas]

Hello Dario,

It may be related to the same topic, but not necessarily. Please give it a try with solution in this thread:

https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/Taplinx-iOS-app-reading-Desfire-EV2/m-p/20143... 

Best regards,

TapLinx team

[dario_sec]

Thank you for your support,

I think solution you reported doesn't fix compatibility problem with Xcode 16.

We tried Xcode 15 and compatibility problem had gone away, but library stills doesn't work.

SwiftUI needs to build preview on x86-64 and library seems to work only for arm, so there are problems .

We decided to write our own library, really challenging (but also really interesting). 

As suggested in thread you reported it would be great if you update and improve document also with a working example.

Regards,

Dario

[KellyLi]

Hello @dario_sec 

The application note does not specify a specific version of Xcode, which means that Xcode 16 is also supported.

[dario_sec]

Thank you for your answer.

Do you have any clues why Xcode is suggesting this in the error?

"rebuild 'TapLinxLibrary' and try again" (cannot rebulid without library source code)

Regards,

Dario

[alv_Developer1]

Hi,

I am facing same issue with Xcode version 15.0 and Swift 5, did you manage to solve this?

Could you write your own library?, I wonder if low level NFC access methods are complicated or not on iOS withouth the SDK...

Regards

Alvaro

[dario_sec]

Hi Alvaro,

we tried also installing <16 Xcode but we  wasted a lot of time without any success.

My personal opinion is that this library should be totally refactored: it seems ported from other languages and it is really big. 

Yes you can write your own library using interfaces exposed by Apple CoreNFC we are completing all authentication types, we wrote around 1000 code rows, but still working on it.

It would be nice to share library but as you probably know it is not possible due to NDA.

The positive aspect is truly getting to know the product.

[alv_Developer1]

Hi Dario,

Thanks for your response :), yes it does not seem very compatible with Swift and Xcode, I think we'll wait to see if they fix this bug soon.