[Bug?] After adding a new device, logging back into the nns dapp gives a fetch error

[ByronBecker]

Device: iOS 16.2 (20C65)
Browser: Safari

Description: After adding a new device through internet identity, navigating to the nns dapp at nns.ic0.app throws the following error on initial page load.

[peterpeterparker]

Hi Byron,

• Do you face the issue in NNS-dapp or II? I'm confuse about the exact step that leads to the error
• You only face the issue with the new device correct? If yes, sounds like iOS 16.2 related, I read there was some issue (generally speaking) with Webauth with that new iOS release
• Can you provide a screenshot of the all the browser? (not a cropped image)

Thanks for the few details in advance

[peterpeterparker]

The details will for sure help debug. Meanwhile I found where the error is throw, the issue comes from the Service Worker (see this line of code) than cannot instiantiate the storage. I'll ping the related team.

[ByronBecker]

• Do you face the issue in NNS-dapp or II? I'm confuse about the exact step that leads to the error
  It happened in the NNS-dapp (no issues with II)

• Can you provide a screenshot of the all the browser? (not a cropped image)
  At the time I didn't know there was a developer console on iOS, so I didn't dig further - I'm sort of kicking myself that I didn't do that at the time.

The details will for sure help debug. Meanwhile I found where the error is throw, the issue comes from the Service Worker (see this line of code) than cannot instiantiate the storage. I'll ping the related team.

Awesome, glad you found the error and sorry for not responding earlier. To get around this, I ended up rotating my device keys (cleared from keychain, and set up a new device) and this fixed the issue. Of course, this is not an ideal solution.

Now that the issue is fixed on my side it's a bit hard to replicate, but I'll let you know if I run into it again.

[peterpeterparker]

Thanks for the feedback @ByronBecker. Happy to hear you found a workaround. Please let us know if you run into it again.

We tried to replicate yesterday and we did not succeed to reproduce it neither unfortunately.