-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Nearby: My position does not move #2062
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
Comments
Hmm, thanks @nicolas-raoul , I should have forget implement this during refactoring nearby activity to fragment. |
Eeep. Gotta put this in the hotfix then. Thanks for reporting this! |
Anyone working on this or should I take it up? |
@Divyanshu2132 Feel free to work on it, it is yours, thanks! 🙂 |
Ah, @neslihanturan are you working on it? |
I think it's fine for @Divyanshu2132 to work on it. I just assigned @neslihanturan at the start as the person responsible for it, but if a volunteer wants to do it I am sure she won't mind. ;) |
Hi @Divyanshu2132 , thanks for taking this up, can you please share your progress? Since this is not a very beginner friendly task you can share your progress with us (cause I know related code is kinda confusing, me and @ashishkumar0207 worked on those area recently, and there are some uncertainties). if you decide to switch to another issue, please notify me as soon as possible so that I can claim the issue. |
Yes sure I'll notify you if I'll switch to another issue |
@neslihanturan can you help me to reproduce this |
Can you share a gif showing it is working for you? You can use Android studio record and mock location apps for fake move. I never recognized this issue either, maybe @nicolas can help for repriducing |
And are you sure your master is up to date? We just included 2.9.0 to master and Nicolas mentioned this issue happens on 2.9.0. can you also share what you see on your about page as software version |
I just managed to reproduce the problem with today's 2.9.0.118. It was difficult:
Nes, I send you my logcat by email as it contains some confidential information (WiFi network names), the log starts when the wikidata items are loaded successfully (at around 15:45 I would say), then after like 30 seconds I realized the point was not moving. |
I still have the app running in that stuck position, if you want me to try something quickly, just ask. |
@nicolas if you moved the map focus with your fingers, map thinks that you are discovering around and does not update map focus according to your location to not interrupting your discovering. If search this area button is visible, it is intended not to follow your location. Is this your case? |
Yes my master is updated |
One extra thing is also happening |
I see @nicolas-raoul . @Divyanshu2132 can I take this issue up please? I have some assumptions but I am not sure if they will work or not. So this PR may require several revisions. |
Sure sidewise I will also look into the code if I found something |
Hi @nicolas-raoul , I have been testing this issue for while, I couldn't reproduce a not tracking situation so far. But some user may feel this is a bug, To fix this issue I have some suggestions: Second one seems like a better idea to me. What do you say @nicolas-raoul ? |
My PR is up for related solution |
Second solution sounds better, actually I thought it was the intended behavior for the start :-) |
Steps to reproduce:
Expected: The dot moves with you
Actually: The dot does not move
If it is working for you, then please comment below, thanks!
Commons app version:
2.9.0
The text was updated successfully, but these errors were encountered: