Sign in Faild (iPhone)

Bug Reports
1

Description of the issue:
Launching Scaniverse v5.1.0 and tapping “Sign in to get started” opens an in-app web view.
Selecting either “Sign in existing account” or “Create new account”, then “Sign in with Apple”, consistently returns “Sign in Failed.”
Reinstalling once enables sign-in, but all saved scans disappear.
Restoring the iPhone from backup recovers the scans, yet the sign-in error returns.
Calendar is already set to Gregorian (Western), so the known Japanese-calendar bug is not a factor.
Issue reproduces on iPhone 13 mini (iOS 16.7 Stable & iOS 26 Dev Beta).
iPad Pro M2 (iPadOS 26 Dev Beta) logs in successfully, suggesting a device-specific or keychain-related problem.

Date:
Exact start time unknown; first attempted login and observed failure mid-July 2025.

Device type & OS version:
• iPhone 13 mini — iOS 16.7 (Stable)
• iPhone 13 mini — iOS 26 Developer Beta
• iPad Pro M2 — iPadOS 26 Developer Beta (works)

App version:
Scaniverse v5.1.0

Reproduction Steps:

  1. Launch Scaniverse v5.1.0.
  2. Ensure Calendar = Gregorian (Settings ▸ General ▸ Language & Region ▸ Calendar).
  3. Tap “Sign in to get started.”
  4. Choose “Sign in existing account” or “Create new account.”
  5. Select “Sign in with Apple.”
  6. After Face ID / password, an alert “Sign in Failed” appears and login aborts.
  7. (Optional) Delete & reinstall Scaniverse → step 5 succeeds but all scans vanish.
  8. Restore device from backup and repeat steps 1-5 → failure reproduces, scans return.
  9. Perform steps 1-5 on iPad Pro M2 (iPadOS 26 Dev Beta) → login succeeds.

Expected Result:
Successful authentication with Apple ID on iPhone without data loss.

Actual Result:
Authentication fails; only workaround (reinstall) causes irreversible loss of local scans.

Additional Notes:
• Similar Apple/Google sign-in failures have been reported by other users since the Niantic Login migration, indicating a backend issue rather than device settings.
• I am a Japanese user and not fluent in English, so please excuse any language mistakes.
• Please advise on a safe recovery path that preserves local scan data or confirm when backend remediation will roll out.

IMG_0002
IMG_00021125×2436 90.3 KB

3

Hello,

Thanks for reaching out. Let me take a look at this and get back to you if I have any additional questions. Is your Apple login email the same as the one associated with your account or is it a different one? If it’s different, feel free to DM me if you don’t want to put it on the forum post

4

Hi Jesus,

Thanks for the quick reply!

Yes, my Apple login email is the same as the one linked to my Scaniverse account.
The same Apple login works fine on my iPad Pro M2, so the account itself seems OK, but the issue persists only on iPhone 13 mini.

I’m a Japanese user and not fluent in English, so please excuse any mistakes.

5

Hello,

Apologies for the delayed reply. Have you been able to login to your account since? We looked into the issue on our end but couldn’t replicate a login issue with iCloud. Were other apps also having any issues logging you in via iCloud on the iPhone 13 Mini or just Scaniverse?

6

Hi Jesus,

Thank you for your follow-up.

The issue still persists on my iPhone 13 mini:

• Login fails for both Sign in with Apple and Sign in with Google only in Scaniverse.
• Polycam and other 3D scanning apps work fine with Apple ID sign-in, so my Apple account is okay.
• If I reinstall Scaniverse, I can log in once, but all local scan data is deleted**.

Because of this, I’m stuck:

  • I cannot safely log in without losing my local scans.
  • I cannot export the raw capture data from the current app state without login.

I will attach a short video showing the login failure on my iPhone.

youtube

Could you confirm if there is any way to:

  1. Safely enable login without losing local scan data, or
  2. Export my raw capture data from the device before reinstalling?

Thank you for your continued support.