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.

Sign up for GitHub

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

Jump to bottom

Bot Edit: Bot pin & cover photo do not center after panning on full map view #1662

Closed
mstidham opened this issue Dec 14, 2017 · 8 comments
Closed

Bot Edit: Bot pin & cover photo do not center after panning on full map view #1662

mstidham opened this issue Dec 14, 2017 · 8 comments
Assignees
@aksonov
Labels
BUG Code/Feature contains a known/confirmed bug HIGH PRIORITY
Milestone
Sprint #21.1 | De...

Comments

@mstidham
Copy link

mstidham commented Dec 14, 2017 •
edited by zavreb
Loading

Title: Bot pin & cover photo do not center after panning on full map view

QA TEMPLATE Input
Device Type: iPhone 7 Plus
iOS: 11.1.2
tr Version: 1.65.0
Environment Staging
Codepush: Staging-Pavel "uber panning #4"
Internet Connection Type: WiFi
Users affected? Miranda
User handle:
Bypass handle?: @TestyTester
Location access type? While using
Does this issue occur on other environments? Production
Time issue occurred (UTC)

Observed Result:

Bot pin & cover photo do not center on bot profile after user pans away from bot location and taps on the bot pin

Expected Result:

Bot pin should center when user returns to bot profile. Cover photo should also be centered.

Steps to reproduce:

  1. Edit a bot
  2. Tap on full map view
  3. Pan until bot pin is on the far side of screen (not centered)
  4. Tap on bot pin
  5. Tap on bot pin again to see non-centered cover image

Related Screenshots/Video Links:

image
@zavreb zavreb added 1.64.0 BUG Code/Feature contains a known/confirmed bug and removed 1.64.0 labels Dec 14, 2017
@zavreb zavreb added this to the Sprint #21.1 | Dec 8 - Dec 20 milestone Dec 14, 2017
@zavreb
Copy link

zavreb commented Dec 14, 2017

This bug is also present on 1.65.0 prod. (It's not a new bug)

@aksonov aksonov self-assigned this Dec 14, 2017
aksonov pushed a commit that referenced this issue Dec 14, 2017
Addresses #1662
bb7a14b
@aksonov
Copy link
Contributor

aksonov commented Dec 14, 2017

Please check my latest codepush

@aksonov aksonov mentioned this issue Dec 14, 2017
Merged
@mstidham
Copy link
Author

Codepush Verified Staging-Pavel

southerneer pushed a commit that referenced this issue Dec 14, 2017
@aksonov @southerneer
Addresses #1662 (#1666)
39f9d0a
@zavreb
Copy link

zavreb commented Dec 14, 2017

Codepush Verified Staging-Pavel

@mstidham
Copy link
Author

Verified on Staging 1.65.1

1 similar comment
@zavreb
Copy link

zavreb commented Dec 16, 2017

Verified on Staging 1.65.1

@mstidham
Copy link
Author

Verified on Prod Version 1.65.1

@zavreb
Copy link

zavreb commented Dec 19, 2017

Verified on Prod 1.65.1

@zavreb zavreb closed this as completed Dec 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aksonov aksonov

Labels
BUG Code/Feature contains a known/confirmed bug HIGH PRIORITY
Projects
None yet
Milestone
Sprint #21.1 | Dec 8 - Dec 20
Development

No branches or pull requests
3 participants
@aksonov @zavreb @mstidham