Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Currently in PROD I noticed the blockstack logo appearing twice in the safari connect sign in window #629

Closed
timstackblock opened this issue Oct 15, 2020 · 5 comments · Fixed by #675
Assignees
Labels
bug Functionality broken bug-p3 Non-critical functionality broken for many users, or there are clear workarounds

Comments

@timstackblock
Copy link
Contributor

noticed the blockstack logo appearing twice in the safari connect sign in window

Screen Shot 2020-10-15 at 9 38 13 AM

@timstackblock timstackblock added bug Functionality broken bug-p3 Non-critical functionality broken for many users, or there are clear workarounds labels Oct 15, 2020
@markmhendrickson
Copy link
Collaborator

I'm seeing this as well, notably in Safari but not Chrome

@markmhendrickson
Copy link
Collaborator

markmhendrickson commented Nov 4, 2020

@timstackblock recently saw this in Chrome and Safari

@timstackblock
Copy link
Contributor Author

timstackblock commented Nov 5, 2020

This is happening in Chrome, Safari & FF now, when the user attempts to sign in using the latest build https://pr-637.testnet-demo.stacks.engineering/

FIREFOX

Screen Shot 2020-11-05 at 2 14 55 PM

SAFARI
Screen Shot 2020-11-05 at 2 14 39 PM

CHROME
Screen Shot 2020-11-05 at 2 14 18 PM

@timstackblock
Copy link
Contributor Author

Still broken

Screen Shot 2020-11-18 at 8 43 50 AM

@markmhendrickson
Copy link
Collaborator

@timstackblock to retest with this PR's build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality broken bug-p3 Non-critical functionality broken for many users, or there are clear workarounds
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants