At this time, Fidesmo’s app for iPhone has a critical bug in that it will not present you with a “connect services” button once you scan your Apex. To get around this problem, you will need to manually deploy applications.
Once you can your Apex, you should see a screen that says “No connected services” like this;
Hey, for anyone wanting OTP’s on iPhones, this app: Token2 Companion seems to work with the U2F applet, sith the FIDO2 it seems to have troubles connecting. (Since there is no VivoKey OTP app on iPhone)
turn on debug mode in the fidesmo app and it will tell you (its d7d13e65), but i don’t know what the removal service id might be… we use “destroy” across the board but it could just as easily be “muffins”… no idea what fidesmo might have used.
Sorry, too little information, my fault.
I managed to install this applet to my apex flex implant. And now I can’t remove it, as there’s no “destroy” button.
And why don’t it have destroy button? What can be the problem?
Should I try “delete” in manual delivery service? Or do I have any other options to destroy the applet?
Thank you for your reply.
So the way Fidesmo works is they have an application ID and a service ID. There’s no specific installation service and no specific removal or destroy service, they are all just services. You can configure each service to do a specific thing, and each service can have its own set of requirements and permissions. The only reason VivoKey applications have a destroy button in the Fidesmo app is that we named our removal service “destroy”.
Likely, the ability to install the Go Nordic app was an oversight of permissions. I guess it’s not supposed to be able to be installed on stuff yet. Because of that, my hunch is that whatever service has been defined to remove or destroy the applet either doesn’t exist yet or has permissions that stop it from being visible to you.