App broken after migrating to new device

[Biepa]

Steps To Reproduce

I’m not sure if this can reproduced anytime. Just wanted to write about the issue I had

1. Had the app working on an iPhone.Bought a new one and migrated all my data with the iOS setup wizard. So apps are automatically installed and their data is transferred.
2. While a lot of apps worked fine after that. The Authenticator apps now just displays the logo on startup and hangs there forever.

Expected Result

App should either transfer the data and work. It worked fine with Raivo. Or should start clean without data.

Actual Result

App is hanging.

Screenshots or Videos

Additional Context

No response

Build Version

Don’t know how to see outside the app. The current one as of today.

Environment Details

From iPhone 11 to 13 mini.

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[frenkel]

Same problem here. Luckily I could work around this by disabling FaceID access for the app and then exporting all my codes. Reinstalling the app and importing got me up and running again.

[brent20]

Can confirm that this happened to me as well, I resolved it by deleting the app and reinstalling from the App Store.

[neverarockstar]

Same issue happened to me after a phone repair. Apple replaced the back panel and it's functionally a new device. After restoring my icloud backup, the app hung on the logo screen. I was able to get back in after erasing the phone and restoring from backup again, but a few days later the issue reappeared. I've once again been able to recover my codes by restoring from backup, but will be switching to a different 2FA app until this is sorted out.

iPhone 13 mini running iOS 18.0.1
App version 2024.6.1 (45)

Update: This seems to be related to FaceID. The app worked fine until I set up FaceID after the restore, but hung as soon as I did. Redownloading and importing seems to have solved the issue.

[brent20]

I’m a little disappointed in Bitwarden, not going to lie. My disappointment lies in the fact that this bug (and another bug I reported) are fixed, yet the last release was 4 months ago. I recognize that effort is being spent elsewhere, but there’s 4 months worth of merged changes that we’re all waiting to see released. If someone can speak to the delay, it would be appreciated. I recognize that this is all free- but the bugs have been fixed. A new version just needs to be released.

Thanks!