ios13 | usefull information required for debugging on iOS

I had the same problem. It might something to do with my M1 MacBook. So I use this solution, and problem solved.

Running Cocoapods on Apple Silicon (M1)

Install this first,

sudo gem install ffi

Then repeat the pod init and install.

After some more researching I figured out how to make this work, in case anyone stumbles upon the same problem. I ended up reading this issue description (link) and made me think I should try and use a different code generator. My cmake configuration was correct however apparently there is a bug with using XCode as the code generator (in here -G"$GENERATOR_NAME" ). After I set GENERATOR_NAME=Ninja I managed to compile a version of the library that is for Mac Catalyst.

Somewhere in your codebase, potentially a xib file or a storyboard, you have a reference to calculateButtonLabel that isn't linked to anything. My best guess is that you used to have an IBOutlet linked to it that no longer exist.

The GitHub repo you linked doesn't contain a reference to calculateButtonLabel and it builds & runs fine in the simulator (Xcode 12.1).

I don't think using NFC Passkit allows you to behave like a Mifare DESfire Tag, this seems very limited to "Reward Card information" it just provides some extra info to a card reader that knows how to send Apple's Value Added Services Protocol over NFC (Not all card readers/POS terminals can do this)

If you look at the Apple Doc's

https://developer.apple.com/library/archive/documentation/UserExperience/Reference/PassKit_Bundle/Chapters/TopLevel.html#//apple_ref/doc/uid/TP40012026-CH2-DontLinkElementID_3

and

https://developer.apple.com/library/archive/documentation/UserExperience/Reference/PassKit_Bundle/Chapters/LowerLevel.html#//apple_ref/doc/uid/TP40012026-CH3-SW5

You get to specify

message, string, Required. The payload to be transmitted to the Apple Pay terminal. Must be 64 bytes or less. Messages longer than 64 bytes are truncated by the system.

encryptionPublicKey, string, Optional. The public encryption key used by the Value Added Services protocol. Use a Base64 encoded X.509 SubjectPublicKeyInfo structure containing a ECDH public key for group P256.

So Contactless bank cards conform the the NFC Forums Type 4 Specification, the Type 4 specification is low level and defines a method interact with a Higher level protocol beginning with the selection of an AID (Application ID), how you interact act with the card after the AID selection is up to each Application Specification.

So Banks, Visa, MasterCard, etc and the NDEF Standard all have their own AID numbers, so I guess that Apple also have an AID for their Value Added Services Protocol.

A Mifare DESFire tag is also a NFC Forums Type 4 Tag and can be programmed to respond to the NDEF AID and other custom AID's though I'm not sure it can be programmed to be able to respond to the AID used for Bank cards or to respond to Apple's Value Added Services Protocol.

So in General this Apple NFC feature allows you to provide some extra info to Apple Pay's Wallet App so it responds with some extra custom information to a NFC reader that conforms to Apple's Pay standards. So very restrictive in what it can do.

Whereas the Mifare DESFire tag is a much more flexible implementation of the lower level NFC standards.

If your buttons are working but are invisible it's very likely that you are using UIAppearance somewhere and that's causing your buttons to become the same color as the navigation bar.

You can certainly go on playing with Xcode 11 if that is what you feel like doing. But that's all you will be doing - playing. You won't be able to do anything with an app that you create that way. In particular, without Xcode 12, you cannot run the app on a device with iOS 14 on it, and you cannot submit the app to the App Store.

So when you say

use older Xcode version for developing, building and deploying

...you can just delete the word "deploying"; you won't be doing that (if the word "deploying" means what it usually means).

(And you cannot easily develop an app partly with Xcode 12 and partly with Xcode 11, as some of the things you do in Xcode 12 can make the project incompatible with Xcode 11.)

You can use if #available(iOS 14.0, *) if you want to adapt the iOS 14 code so it compiles on iOS 13.

Here is an adapted version of this answer to work on both iOS 13 and iOS 14:

1. Convert the mhist dictionaries into a List of the dictionaries.

It seems Apple does not give us a direct way to influence the max size of the dynamic fonts.

To avoid very small font sizes there is the minimumScaleFactor modifier like