Post not yet marked as solved
But what is it that your app actually sells?
A subscription that gets the users access to the price monitoring? Or do you give that away and then sell the ticket?
Post not yet marked as solved
If you mean can you communicate with the mobile phone SIM card, I believe not.
You can use CoreNFC to exchange arbitrary APDUs with a JavaCard applet via NFC, though.
Post not yet marked as solved
The FIDO 2 specification does suggest that authenticators may support short exchanges via ISO7816-4 chaining.It indicates that if a request is sent to the authenticator with the short length, that the authenticator MUST respond short.It indicates that if a long request is sent the authenticator must respond with extended length APDUs. It's not clear whether an authenticator which supports only short APDUs and chaining is compliant.
Post not yet marked as solved
MiFare Classic 4K? If it's MiFARE Classic they didn't build support for that (at least as yet).
Post not yet marked as solved
No, at least not up to this point.Only Wallet/PassKit/Apple Pay have a way to do Host Card Emulation as of now.There's not an API for third party developers to do HCE.
For those looking for examples of communicating with complex applets on a card, no different from javacard applet flows, look at:https://github.com/AndyQ/NFCPassportReader
Post not yet marked as solved
I'm able to do so.At what stage are you getting a failure.You would communicate with the applet using the NFCISO7816Tag.You need to declare your AID in the app manifest.Where are you having trouble? How far do you get? What error are you experiencing?
Post not yet marked as solved
I'd do what ever I needed to reduce friction. Perhaps enhace the system with a flag for "special" accounts to bypass 2FA. If the reviewer doesn't get stuck on 2FA then that shouldn't be a problem.This potentially opens the door to the app having functionality they were unable to review, but I would think a 2FA authentication step wouldn't be something significant enough for them to make noise about in that respect.
Post not yet marked as solved
I notice the search engine optimization on their main website also includes such gems as:"We make cleaning dirty! Find a **** cleaner near you today. Our kiki agents clean houses, windows and our kiki agents will even wash the dog. Download the kiki app today."I think the developer just needs to understand that this is never ever getting approved in the App Store.
Post not yet marked as solved
I have an idea of what might fix it:Remove all references to bikinis (or any clothing for that matter) and any references to gender of service provider. How are those relevant to cleaning services?Also, remove the provider's profile picture until after the customer is committed to the appointment. Showing the photograph before the customer has committed to booking the service creates opportunities for discrimination based upon the appearance of the provider and this is unlikely to be something that they will allow.Notice that in Uber's app, you don't get to see the pictures of the drivers before they're already on the way to pick you up. This prevents you self-selecting your driver on the basis of their race, appearance, gender, etc.
Have you tried listing both AIDs?It has been stated that certain AIDs are protected / blocked (essentially the ones you'd need to speak with broadly deployed payment cards' EMV payment applets).In case they have for some reason protected the AID of the card manager, you might try changing the card manager instance AID. That's often a proprietary card-type specific function, and in some cases can only be done during prepersonalization, but you may have luck that way.
Post not yet marked as solved
Yes, I just verified. It's in the 2019 Core NFC Enhancements video at time point 9:00."However, for the time being, reading payment cards will not be supported."Presumably they want to encourage Apple Pay as the only kind of payment handling the phone engages in.
Post not yet marked as solved
I thought the video presentation mentioned that known payment card AIDs would be ignored/banned?
Along with iOS 13 Beta 5, the CryptoKit developers have posted a documentation update that addresses this:https://developer.apple.com/documentation/cryptokit/storing_cryptokit_keys_in_the_keychainAbout 25% into the document, they note:"Keys that you store in the Secure Enclave expose a raw representation as well, but in this case the data isn’t the raw key. Instead, the Secure Enclave exports an encrypted block that only the same Secure Enclave can later use to restore the key."So, as I suspected, the .data represents a wrapped object with the real private key (and presumably use / authorization policy) encrypted by a wrapping key unique to the individual hardware secure element.
Post not yet marked as solved
I've always assumed this lag come from some multi-party release notes review process.Someone has to pick what things get included versus concealed, etc.
