Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug] Onboarding - Blank screen after tapping Sign in, Sign in #2713

Closed
grigoryk opened this issue May 22, 2019 · 2 comments
Closed

[Bug] Onboarding - Blank screen after tapping Sign in, Sign in #2713

grigoryk opened this issue May 22, 2019 · 2 comments
Labels
🐞 bug Crashes, Something isn't working, ..

Comments

@grigoryk
Copy link
Contributor

grigoryk commented May 22, 2019

In the logs, I'm seeing the following:

FirefoxAccountStateMachine  D  Processing event Init for state Start. Next state is Start
                         D  Got invalid event Authenticate for state Start.
                         D  Ran 'Init' side-effects for state Start, got successive event AccountNotFound
                         D  Processing event AccountNotFound for state Start. Next state is NotAuthenticated
            AppServices  I  Using fxaclient_ffi_lib_name: fenix
          fxaclient_ffi  D  fxa_new
              GeckoView  W  No GeckoSession attached to this GeckoView instance. Call setSession to attach a GeckoSession to this instance.

Seems like state events are not being processed in the right order.

Steps to reproduce

With a fresh Fenix install, click "Sign in" in the onboarding flow, then "sign in" again.

Expected behavior

FxA sign-in page.

Actual behavior

Blank screen. Going back, and tapping "sign in" again fixes the problem.

Device information

  • Android device: ?
  • Fenix version: ?

┆Issue is synchronized with this Jira Task

@grigoryk grigoryk added 🐞 bug Crashes, Something isn't working, .. Feature:FxA labels May 22, 2019
@grigoryk
Copy link
Contributor Author

Makes perfect sense that trying this flow again fixes the problem. At that point we're already in the 'AccountNotFound' state, and process the 'Authenticate' event correctly.

@grigoryk
Copy link
Contributor Author

grigoryk commented May 22, 2019

The simplest thing to do here is at the application level - we need to make sure accountManager is initialized before we try interacting with it.

Good thing about this is that we need to do this anyway for the onboarding flow: it should check our signed-in status, and adjust the UI accordingly; which means registering for account change events with the accountManager.

grigoryk pushed a commit to grigoryk/fenix that referenced this issue May 22, 2019
…pter items accordingly

we're ensuring that it has been initialized.

I wonder if we could just make background services load eagerly (they're lazy init now), instead.
boek pushed a commit to grigoryk/fenix that referenced this issue May 22, 2019
…pter items accordingly

we're ensuring that it has been initialized.

I wonder if we could just make background services load eagerly (they're lazy init now), instead.
boek pushed a commit to grigoryk/fenix that referenced this issue May 22, 2019
…pter items accordingly

we're ensuring that it has been initialized.

I wonder if we could just make background services load eagerly (they're lazy init now), instead.
boek pushed a commit to grigoryk/fenix that referenced this issue May 23, 2019
…pter items accordingly

we're ensuring that it has been initialized.

I wonder if we could just make background services load eagerly (they're lazy init now), instead.
@boek boek closed this as completed in f4f35bd May 23, 2019
@data-sync-user data-sync-user changed the title [Bug] Onboarding - Blank screen after tapping Sign in, Sign in FNX2-18217 ⁃ [Bug] Onboarding - Blank screen after tapping Sign in, Sign in Aug 5, 2020
@data-sync-user data-sync-user changed the title FNX2-18217 ⁃ [Bug] Onboarding - Blank screen after tapping Sign in, Sign in FNX3-16527 ⁃ [Bug] Onboarding - Blank screen after tapping Sign in, Sign in Aug 11, 2020
@kbrosnan kbrosnan changed the title FNX3-16527 ⁃ [Bug] Onboarding - Blank screen after tapping Sign in, Sign in [Bug] Onboarding - Blank screen after tapping Sign in, Sign in Aug 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐞 bug Crashes, Something isn't working, ..
Projects
None yet
Development

No branches or pull requests

3 participants