After this upgrade to II2.0, i was quite confusing how to use it , so i tried all my devices(iphone , pc, android) , and i didn’t know that I should recover in the first place, i just selected created identity or something.
when I realized that i need to recover first , then add new passkey way in order to bind with all my devices(like iphone account, Windows hello account, android finger print). Instead, all devices that i have are created new identities 2.0, and now i dont have any other accounts of apple, windows hello, or gmails. The situation is I can’t unregister those new Identity 2.0 that i mistakenly created which already bound with my all device or accounts, and i have no other way to access my neuron at all. (I can’t apply any other gmails or apple acounts)
it’s REALLY upsetting , i don’t know how to access my neuron now ! Help PLZ! T.T
After you’ve successfully upgraded your identity on any particular device, you can add a passkey for each other device:
Go to id.ai and sign in with your upgraded identity.
Go to Access and recovery.
Click Add new in the Access methods section.
Choose Continue with passkey.
Choose Continue on another device.
Follow the instructions on the screen.
Repeat the above for each device to create passkeys for each of them.
Some passkeys are synced and thus already available between multiple devices e.g. iCloud (iPhone, Mac, ..) or Google Passwords (Android, Chrome browser, ..).
The list of access methods will show for each passkey where they’re stored and available e.g. “Stored in your Apple account and synced across your Apple devices.”.
Alternatively, you can also go through the upgrade flow multiple times (on every device) and enter the same identity name each time.
Lastly, I would recommend to set-up a recovery phrase if you haven’t already to avoid losing access when you lose/break any account(s)/device(s) that hold your passkeys.
If you have any more support needs, please create a support ticket so we properly keep track of your support case (this link can be found in the footer at id.ai).
Please do not share any recovery phrases with anyone, including support, developers or other people that might seem trustworthy. Official support will never ask for your recovery phrase.
I agree the user interface is different, but to be honest it’s not that bad. It’s just new and different. It’s works fine once you learn how to use it.
Most cycle burn would be from application canisters e.g. Caffeine generated application canisters I’d assume.
Internet Identity itself is on a fiduciary subnet and thus doesn’t count towards the cycle burn as far as I’m aware, neither would it have burned that many cycles since users only interact with it when they need to (re)authenticate.
Anyhow, let’s try to stay on-topic, discussing other topics in this thread like the cycled burn rate isn’t helping the user that created this thread.
I don’t know what the migration problems are, but if people are complaining, they clearly have some.
However, II 2.0 is currently the critical thing for adoption and should be implemented as soon as possible. If someone disagrees with this, they don’t understand UX and how much the user number in 1.0 killed it.
If I may, we have seen exactly this a few times by now, instead of upgrade ppl create new. And ofc WinHello and the rest prompted to enter pass, users did and thus a new id was created with the old auth so when logging into NNS no neuron no stake. Panic set in until reading the linked FAQ and using the TOOL to recover the old id numbers and upgrade them set everything back to normal, loggging into NNS all was ok.
for people who use II everyday… and had already upgraded account when this was warned about a long time ago. It’s not problem.
For people who only log in once in a blue moon to check on things. The UI needs work. not a lot of work, a few small changes would make certain things more clear.
Sometimes when i login with 2.0 I accidentally choose the wrong ID. because it’s in the upper right which is not a place peoples eyes go when they look at a website. Just a simple thing like putting that in the center of the screen, with (Upgraded from XXXXX). Would have prevented a lot of these issue.
A few minor tweaks would certainly be helpful. But we simply cannot return to the user number, let it perish, burn and disappear somewhere in the darkest valley.