[connect] Login fails on mobile

[friedger]

Using connect library on mobile (chrome and firefox on Android) fails to handle the pending sign in.

A tab with the auth response is opened, however, the onFinish function is not called. This works on desktop e.g. for http://coronatrackerv1.s3-website-us-east-1.amazonaws.com/

Possible work around, check manually for userSession.isPendingSignin() and call userSession.handlePendingSignIn()

[hstove]

Thanks for the report @friedger !

I need to do some investigating. I wouldn't be surprised if cross-origin postMessage has issues on mobile. Does the redirectURL param still work if the callback isn't fired? If not, then that's definitely a bug.

[friedger]

Does the redirectURL param still work if the callback isn't fired?

Not sure what you mean here. How could I check that?

[hstove]

See these docs: https://github.com/blockstack/ux/tree/master/packages/connect#authoptions

You can include a redirectTo option. If the callback fails, the user should be redirected to redirectTo with an authResponse param, just like how current blockstack.js works.

[markmhendrickson]

@hstove is this a matter of providing additional migration guidance rather than fixing a bug per se?

[ryanarndtcm]

This is coming in from a user in support who added to it above, but has not been given a response on next steps. this is impacting the coronatracker app.

Hi Blockstack support,

I was sent your way to see if we could resolve an issue we're having developing CoronaTracker (https://coronatracker.me/). A few days back, we filed #300 this issue, as we were having trouble signing in on mobile.

On Chrome iOS - we were unable to log in at all
On Safari iOS - we were only able to log in after several attempts

We don't believe this is something on our end, but if it is or you have any ideas of what it could be, please let me know. If this issue has been resolved - could you send the steps necessary to solve it?

[hstove]

Yes, the fix here is that you'll need to implement the usual userSession.handlePendingSignIn() flow inside of your app, on page load. It's possible we could have Connect do this automatically, but I'm not 100% sure that's the best idea. I would appreciate feedback on that idea, but in the meantime, I'd suggest implementing that manually in your app to get it fixed ASAP.

[SomeMoosery]

So I'm still relatively new to Blockstack - are we saying that on mobile we'll have to handle Blockstack auth the "traditional" way where it opens an entirely new window etc? Or, is there a way to use both Connect and handlePendingSignIn() flow in tandem for mobile so that the users have the same experience on mobile or desktop?

[njordhov]

the fix here is that you'll need to implement the usual userSession.handlePendingSignIn() flow inside of your app, on page load.

Still got feedback that the issue remained with Connect even in an app that explicitly called handlePendingSignIn at loading time. Can this issue possibly be explained by handlePendingSignIn being called more than once?

[hstove]

So I'm still relatively new to Blockstack - are we saying that on mobile we'll have to handle Blockstack auth the "traditional" way where it opens an entirely new window etc? Or, is there a way to use both Connect and handlePendingSignIn() flow in tandem for mobile so that the users have the same experience on mobile or desktop?

@SomeMoosery, yes, you'll still have to handle it the 'traditional way' on most mobile browsers. This is because mobile browsers don't support the cross-origin messaging that we do between the original app and the popup. We still have a fallback that supports redirect-based auth, like how it used to work.

Still got feedback that the issue remained with Connect even in an app that explicitly called handlePendingSignIn at loading time. Can this issue possibly be explained by handlePendingSignIn being called more than once?

@njordhov do you have an example?

[njordhov]

Can this issue possibly be explained by handlePendingSignIn being called more than once?

@njordhov do you have an example?

The mobile login failure is NOT explained by an app calling handlePendingSignIn more than once.

The CoronaTracker app uses my react-blockstack package, which sets up a handlePendingSignIn callback before Connect is initialized. I suspected this could cause a conflict, but the CoronaTracker devs tested out this hypothesis by disabling the react-blockstack initialization, and it made no difference, Connect login still failed on mobile without react-blockstack initialization, just as it does in apps that doesn't use the react-blockstack package.

BTW: Is handlePendingSignIn actually supporting more than one callback at a time? If not, perhaps it should, so there can be multiple subscription to the authentication state change.

[njordhov]

Has the Connect team been able to replicate the problem of login failing on mobile? I hear login still fails on mobile when using Banter.

[muneebm]

Mobile login is not working even if you have redirectTo param in AuthOptions.
I think it's because didSendMessageBack in finalizeAuthResponse below could be set to true even if the source.postMessage is not successful.
https://github.com/blockstack/ux/blob/f1921a7b109afb6c149e5f67df33ef52867cab96/packages/app/src/common/utils.ts#L53-L78

[hstove]

Good catch @muneebm . I have an idea for how I could fix that.

[timstackblock]

@friedger @muneebm @njordhov @SomeMoosery

Hey guys I ran through mobile connect login on Android Chrome and it seems that the issue has been resolved.

Please see the video in the link below and let me know if there is anything else needed or can we close this issue out?

http://somup.com/cYhIoXjrET

[SomeMoosery]

Interesting, especially since the link you followed is from an old build of the CoronaTracker app so wouldn't have been due to anything on our end. Unsure the status within Blockstack though :)

[muneebm]

@timstackblock
It works sometimes, but not always, I think.

xordrive:
https://xordrive.muneeb.now.sh/?p=stxconnect.id.blockstack_daa6bcc3-91c2-490e-b322-3db9c3fee4de

The demo app for the PR attached to this issue:
https://xordrive.muneeb.now.sh/?p=stxconnect.id.blockstack_3a24fc92-baaf-4ae9-af6d-5d207d5a5d6b

[ryanarndtcm]

@hstove @timstackblock sounds like its not working again

[timstackblock]

Let me take a look

[BlockSurvey]

Hi @markmhx and @hstove , Login is not working on mobile. I am attaching the authOptions of BlockSurvey below, take a look. Let me know, if anything I need to change. Thanks.

let authOptions = {
  redirectTo: '/dashboard',
  manifestPath: '/manifest.json',      
  sendToSignIn: false,
  userSession: this.userSession,
  appDetails: {
    name: 'BlockSurvey',
    icon: 'https://blocksurvey.io/assets/images/logo/blocksurvey-logo-login.svg'
  },
  finished: ({ userSession }) => {        
    window.location = "https://blocksurvey.io/dashboard";
  }
};

[hstove]

@BlockSurvey @muneebm We have newer docs for supporting the redirect fallback here: https://docs.blockstack.org/develop/connect/overview.html

[BlockSurvey]

@hstove , Thanks for your reply.

We have fallback also, attaching the code below. We observed that, if we use finished callback, redirect will not be considered. So redirect is not even happening, since below code is not getting executed. Thanks.

// BS Login Module
if (this.userSession.isSignInPending()) {

  // If it is in progress
  this.userSession.handlePendingSignIn()
    .then((userData) => {
      // Always redirect to dashboard
      window.location = <any>(Constants.DOMAIN_URL + "/dashboard");
    });
}

[dantrevino]

I'm redirecting after my handlePendingSignIn() and run into the same issue. My bigger issue is that on mobile, the app stays in the new popup window, rather than closing and going back to the original calling window.

site:
https://webby-daily.runkodapps.com/

video/demo:
https://photos.app.goo.gl/YmBtn3RaV6NfivqD9

    if (userSession.isUserSignedIn()) {
      this.setProfile();
    } else if (userSession.isSignInPending()) {
      userSession.handlePendingSignIn().then(() => {
        this.setProfile();
        // window.location = window.location.href.split("?")[0];
      });
    }
  ...