diff options
| author | Fabrice Di Meglio <fdimeglio@google.com> | 2014-02-20 14:41:51 -0800 |
|---|---|---|
| committer | Fabrice Di Meglio <fdimeglio@google.com> | 2014-02-20 16:21:14 -0800 |
| commit | 74309ea53a5a72430bafaa8cea4d82d4e24f61bd (patch) | |
| tree | 2b52da2b96af969339c4dc93dd7a93c6bb535581 /res/drawable-mdpi/lock_anim_1.png | |
| parent | e611b8590d8da69bb95e29a7faa5200a95b427f3 (diff) | |
| download | packages_apps_Settings-74309ea53a5a72430bafaa8cea4d82d4e24f61bd.zip packages_apps_Settings-74309ea53a5a72430bafaa8cea4d82d4e24f61bd.tar.gz packages_apps_Settings-74309ea53a5a72430bafaa8cea4d82d4e24f61bd.tar.bz2 | |
Fix bug #13058470 Cannot add account -- Settings app crashes
- revert back to an Activity instead of a fragment. This
is a straight reverse of the changes introduced for trying
to have a Fragment.
Basically ChooseAccountActivity was previously an Activity for
choosing an account type. If the list of account types was containing
only one item, then the ChooseAccountActivity was just a pass thru
and was falling back to the only account authority available.
In the current reported bug, this was happening by disabling the
Email app and thus having only the GoogleAuthenticator as an
Authority.
Then in the onCreate() the ChooseAccountFragment was seeing that
there was only one account authenticator and issuing a BACK button
press. Too bad, this was done into a non finished Fragment transaction
and leading to a crash.
All in all, we NEED to have an Activity and cannot use a Fragment
in that case.
Change-Id: I4a867a25fe9580929ec50a6775105adac1f88c52
Diffstat (limited to 'res/drawable-mdpi/lock_anim_1.png')
0 files changed, 0 insertions, 0 deletions