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.
Hi! Thanks for the response!
I've tried to list all AIDs, but without success.
But thanks with the advice on changing applet manager AID, I will give it a try!
the solution you suggested works well!
We changed the Card Manager AID with the GPPro:
gp2 -rename-isd 112233445566
Then after adding "112233445566" to the Info.plist the app was able to do the select, i.e., "00a4040006112233445566" and the card responded with 0x9000 and the select data! So we were able to initiate the secure channel with the card manager.
We still didn't test the whole procedure of the applet upload as we haven't it implemented yet but it seems this will work!
Good to know that you managed to make it work with ISO7816 tag.
I am also exploring to handle a java based applet.
Do you mind sharing more details about what kind off application is that and what all APDU's you managed to execute?
It will be great, if you can share the code snippets or the same application.