Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pin position is not changed on iOS
See original GitHub issueChanging pin Positionat android target works fine, however changing the pin Positionwill not effect the pin location at map in iOS, it seems that the pin Positionbinding is not working for iOS ?! 😢
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Incorrect pin location on some maps
So, the pin for my home address is always placed wrongly. The option to refine (move) the pin does not work for the...
Read more >iPhone custom pin position issue - mapkit
The problem is that custom pins are not centered right - custom pin pointing to a location near original. The question is how...
Read more >How To Pin Location On iPhone (Apple & Google Maps)
If you're looking for a way to easily pin locations on your iPhone, then this video is for you! In this video, we'll...
Read more >How to Change Your Pickup Location | Uber Rider App
Changing your location is easy. Get to where you want to go by tapping Edit to enter a new address or dragging your...
Read more >Pin & manage your trips in Google Maps - Android
To get a list of suggested trips, in the bottom bar, swipe up. Find the trip you want and, on the right, tap...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for reporting this, I will investigate and release a hotfix if this is really the case.
1.5.1.