作者如何排解 Xiaomi 15 上 ChatGPT Android 登入卡在載入畫面的問題

By garry-kun (Garry P. Tarroza)

Tested: November 1, 2026
Device: Xiaomi 15
Related GitHub issue: openai/codex #38717

If your ChatGPT Android app gets stuck on an endless loading spinner when signing in, especially if you have multiple Google accounts on your phone, this guide might help.

I experienced this myself. I tried reinstalling ChatGPT, switching internet connections, checking WebView, and changing browser settings. Nothing worked.

What finally fixed it was something I hadn't initially considered: the number of Google accounts configured on my phone.

Here's exactly what happened, how I investigated it, and how you can try the same workaround.

1. The Problem

Everything started after I logged out of the ChatGPT Android app.

When I tried signing back in, the authentication screen would open, but the login button remained stuck on a loading spinner.

I also tried Log in another way, expecting the alternative email login to work.

Instead, that screen also showed a loading indicator on the Continue button, even without an email address entered.

There was no error message explaining what went wrong.

The app simply wouldn't complete authentication.

Symptoms I experienced:

Google sign-in stuck loading indefinitely.

Google account selection wouldn't complete.

Alternative email login also became stuck.

No meaningful error message.

Reinstalling the app didn't resolve the problem.

Screenshot 1: Google sign-in interface stuck loading.

Screenshot 2: Alternative email login with the Continue button stuck loading.

1. What I Tried Before Finding the Fix

I initially suspected a corrupted app installation, network problem, or Android browser authentication issue.

Here are the troubleshooting steps I went through.

Troubleshooting attempt

Result

Uninstalled and reinstalled ChatGPT

Didn't work

Switched between WiFi and mobile data

Didn't work

Tried opening ChatGPT through the browser and returning to the app

Didn't work

Installed Android System WebView

Didn't work

Confirmed the stable WebView implementation was selected

Didn't work

Checked Chrome as the default browser and cleared its cache

Didn't work

Restarted the phone and retried

Didn't work

Tried alternative login methods

Still stuck loading

My device showed Android System WebView version 156.0.8078.47 as its selected implementation.

At this point, I suspected the problem wasn't simply my internet connection or a missing WebView update.

I began looking for other users experiencing similar issues.

1. The GitHub Issue That Matched My Problem

I found an existing report in OpenAI's Codex GitHub repository:

Issue #38717: Login freezes with multiple Google accounts due to Credential Manager TransactionTooLargeException

The issue was originally opened on August 15, 2026, by GitHub user Kitsunetic.

The original report documented a device with six Google accounts where both Google sign-in and email login became unresponsive.

The author also captured Android logs showing an exception:

android.os.TransactionTooLargeException

Other users subsequently reported similar behavior on Samsung devices with multiple Google accounts.

One particularly interesting finding was that ChatGPT could authenticate successfully inside Samsung Secure Folder, which had fewer Google accounts configured than the main Android profile.

That gave me an idea.

Instead of repeatedly reinstalling ChatGPT, I could test whether a separate Android environment would behave differently.

1. First Successful Test: Xiaomi Second Space

Xiaomi phones have a feature called Second Space.

It allows you to create a separate Android environment with its own applications, accounts, and settings.

I decided to use it to isolate the authentication problem without removing any accounts from my primary phone environment.

How to try it on Xiaomi

Open your phone's Settings.

Navigate to Additional settings → Second space. You can also search for Second Space in Settings.

Enable Second Space and complete the setup process.

Configure one Google account in the new environment.

Open or install ChatGPT inside Second Space.

Attempt to sign in normally.

The precise menu names may differ between HyperOS versions.

My result

ChatGPT signed in immediately.

No endless spinner. No repeated authentication attempts.

The same phone that couldn't sign in through Main Space successfully authenticated through Second Space.

This was an important clue.

My original Main Space had nine Google accounts configured, while Second Space had only one.

However, this test alone couldn't prove that account count was responsible. Second Space also had separate application data and settings.

I needed to test the original environment.

1. The Fix That Worked: Reducing Google Accounts

After successfully signing in through Second Space, I returned to my Xiaomi's Main Space.

At the time, I had nine Google accounts registered on the phone.

I decided to temporarily remove six secondary accounts, leaving three.

How to remove Google accounts on Xiaomi

Before starting: Make sure you know your account passwords and can complete any two-factor authentication requirements. Also check that important data is synchronized or backed up.

Open Settings.

Find Accounts & sync, Manage accounts, or the equivalent account management option.

Select Google.

Choose a secondary Google account you can temporarily remove.

Look for Remove account. On some Xiaomi versions, this appears under a More menu at the bottom of the account synchronization screen.

Confirm the removal.

Repeat only as needed, then reopen ChatGPT and test login.

Do not confuse removing an account from your phone with permanently deleting a Google account.

Removing it from the device signs it out and removes associated locally synchronized data. The Google account itself continues to exist and can be added back.

What I did

I removed all six secondary accounts in one go.

That reduced my account count from nine to three.

Then I launched ChatGPT and attempted to log in again.

It worked. Immediately.

No further reinstallations or additional WebView changes were necessary.

For the first time since encountering the problem, I could authenticate inside my regular Main Space again.

1. My Test Results

Here's the complete comparison from my Xiaomi 15.

Environment

Google accounts

ChatGPT login

Main Space, before workaround

9

Failed

Second Space

1

Successful

Main Space, after removing 6 accounts

3

Successful

These results strongly suggest a relationship between the configured Google accounts and the authentication problem.

There are two important limitations, however.

First, I removed all six accounts at once. I didn't test whether the issue would disappear after removing just one, two, or three accounts.

Second, I didn't capture Android system logs.

Therefore, I cannot identify the exact account-count threshold or independently confirm the exception reported in GitHub issue #38717.

What I can confirm is that reducing my Main Space accounts from nine to three restored ChatGPT authentication.

1. How Other Users Can Try This

If you're experiencing the same endless loading problem, here's the order I'd recommend.

Step A: Try the normal troubleshooting first

Before removing any accounts:

Update ChatGPT and Google Chrome.

Set Chrome as your default browser.

Check Google Play Store and Google Play services for available updates.

Restart the phone.

Try your original ChatGPT sign-in method.

Test another network or browser if needed.

OpenAI provides additional instructions in its official sign-in troubleshooting guide.

If those steps work, there's no reason to change your Google accounts.

Step B: Test an isolated Android environment

If your phone supports Xiaomi Second Space, Samsung Secure Folder, or a separate Android user profile, try installing ChatGPT there.

Use only the Google account needed for authentication.

If login succeeds in that environment but fails in your normal profile, you've narrowed the problem down.

It doesn't automatically prove that account count is responsible, but it provides a useful comparison.

Step C: Temporarily reduce Google accounts

If the previous tests point toward an account-related issue, consider removing secondary Google accounts from your normal Android profile.

Unlike my experiment, you can try removing them gradually and checking ChatGPT after each change.

There is no confirmed universal threshold. Different devices may fail with different account counts, and some devices with many accounts may work normally.

Keep the account required for your ChatGPT login.

If authentication succeeds, you have found a workaround for your device.

Step D: Restore accounts if necessary

The original GitHub reporter stated that removed Google accounts could be added back after authentication.

I haven't personally tested whether restoring all nine accounts would preserve my ChatGPT session.

If you choose to re-add them, remember that the login problem could return after you sign out.

Until the underlying issue is resolved, avoid unnecessary sign-outs if you're affected.

1. Why Might Multiple Accounts Cause This?

Google's Android Credential Manager handles credential retrieval and account selection for supported sign-in flows.

Google's documentation describes a known TransactionTooLargeException involving multiple Google accounts and the GetGoogleIdOption credential request.

The documented problem can prevent the sign-in dialog from appearing.

Google states that the known issue was fixed in Google Play services version 24.40.XX and later. However, GitHub issue #38717 contains reports of comparable failures on newer versions.

Technical reference: Android Credential Manager troubleshooting documentation

One possibility is that the credential selection process fails while transferring or preparing account information.

The app may then remain stuck on its loading state instead of displaying an error or allowing another authentication method.

But this remains a hypothesis for my Xiaomi 15.

I have not proven whether the underlying fault is in Android, Google Play Services, HyperOS, or ChatGPT's authentication integration.

1. What Developers Could Improve

Even if the initial failure originates outside the ChatGPT application, the app shouldn't leave users stuck indefinitely.

Ideally, authentication should:

Detect when the credential selector fails or becomes unavailable.

Stop the loading indicator after a reasonable timeout.

Display an actionable error message.

Provide a working alternative authentication path.

Allow users to retry without reinstalling the entire application.

This would make the experience more resilient even when Android authentication components encounter problems.

1. Final Thoughts

I spent a significant amount of time troubleshooting what initially looked like an ordinary login problem.

Reinstalling the app didn't help. Switching internet connections didn't help. Updating or configuring WebView didn't help.

What eventually solved it was changing the authentication environment.

First, ChatGPT worked with one Google account inside Xiaomi Second Space.

Then it worked inside my original Main Space after I reduced the Google account count from nine to three.

If your ChatGPT Android app gets stuck on login and you have several Google accounts configured, this is one workaround worth investigating.

It isn't a guaranteed fix, and it shouldn't require users to remove accounts just to access an application. But until a permanent solution is available, these steps may help others experiencing the same issue.

References

OpenAI Codex GitHub issue #38717

Google's Credential Manager troubleshooting guide

OpenAI's official ChatGPT sign-in troubleshooting guide

Google's instructions for adding and removing Android accounts

If you experience the same issue, consider sharing your device model, Android version, number of Google accounts, and which troubleshooting steps worked.

Additional reproducible results could help narrow down the actual cause.

Original Xiaomi 15 testing and documentation by garry-kun (Garry P. Tarroza), November 1, 2026.

This is an independent user investigation, not an official OpenAI or Google fix.