Apps-android-commons: Nearby map is not loading

Created on 20 Jun 2019  路  9Comments  路  Source: commons-app/apps-android-commons

When I go to app -> click Nearby -> click the "+" button -> select camera icon -> take the picture and successfully proceed with upload, the map appears for a short while and then disappears (switching to Contributions and back to Nearby doesn't help). Instead, I see just the blue "loading screen", which keeps on running.
The "solution" is to kill the app and open again (sometimes I have to do it several times) until the app load the map again.
Another option is to be really quick and pick the second item in the short time frame when the map appears (which is about 5sec), but this can be done just once (then, after another round of taking picture and uploading the map doesn't appear at all and I need to restart the app).

bug high priority nearby

All 9 comments

Thanks for the feedback! Does it happen all the time? What Android version and app version are you using? Thanks!

Hi Nicolas,
yes, it happens all the time.
Version 2.10.2 @ Android 9

Hi @xkomczax , thanks for reporting this. The next time this happens, could you please go to Settings > Send Log File , and send us the email containing your logs? This would help us debug your problem.

Thanks so much!

Hi, I just send the email with the log file.

Thanks @xkomczax !

I managed to reproduce this issue - it only happens if I go to Contributions and then go back to the Nearby tab (staying in Nearby does not cause it). @neslihanturan , Nearby seems to think that I am moving around the map, therefore it does not update.

My logs below:

2019-06-24 19:11:21,206     [DEBUG] [file-logging-thread-1] [MainActivity] : Nearby tab selected
2019-06-24 19:11:21,213     [DEBUG] [file-logging-thread-1] [MainActivity] : Contributions activity list sheet menu item is visible
2019-06-24 19:11:21,214     [DEBUG] [file-logging-thread-1] [NearbyFragment] : On nearby tab selected
2019-06-24 19:11:21,214     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Refreshing nearby places
2019-06-24 19:11:21,215     [DEBUG] [file-logging-thread-1] [NearbyController] : Loading attractions near lat/lng: (-27.4530712,153.0405582)
2019-06-24 19:11:21,221     [DEBUG] [file-logging-thread-1] [ContributionsListAdapter] : Cursor position is 0
2019-06-24 19:11:21,223     [DEBUG] [file-logging-thread-1] [ContributionsListAdapter] : Cursor position is 0
2019-06-24 19:11:21,226     [DEBUG] [file-logging-thread-1] [ContributionsListAdapter] : Cursor position is 0
2019-06-24 19:11:21,229     [DEBUG] [file-logging-thread-1] [ContributionsListAdapter] : Cursor position is 0
2019-06-24 19:11:21,235     [DEBUG] [file-logging-thread-1] [NearbyPlaces] : 15 results at radius: 1.000000
2019-06-24 19:11:21,264     [DEBUG] [file-logging-thread-1] [NearbyPlaces] : 31 results at radius: 1.618000
2019-06-24 19:11:21,349     [DEBUG] [file-logging-thread-1] [NearbyPlaces] : 125 results at radius: 2.617924
2019-06-24 19:11:21,350     [DEBUG] [file-logging-thread-1] [NearbyController] : Sorting places by distance...
2019-06-24 19:11:21,351     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Populating nearby places
2019-06-24 19:11:21,360     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Map fragment already exists, just update the map and list
2019-06-24 19:11:21,361     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Do not update the map, user is not seeing current location marker means they are checking around and moving on map
2019-06-24 19:11:24,437     [DEBUG] [file-logging-thread-1] [WikidataEditService] : Wikidata edit was tagged successfully
2019-06-24 19:11:26,224     [DEBUG] [file-logging-thread-1] [LocationServiceManager] : on location changed
2019-06-24 19:11:26,226     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Refreshing nearby places
2019-06-24 19:11:26,228     [DEBUG] [file-logging-thread-1] [NearbyFragment] : Do not update the map, user is not seeing current location marker means they are checking around and moving on map

Thanks for the logs @misaochan . But I think this should be solved by #2969 .

Thanks @neslihanturan . How far is #2969 from being ready for testing?

As I mentioned on Zulip, I stuck at some point. I don't understand why my current approach is not working but today I will try other approaches randomly, to see if one of them will work or not. Because there is no point of insisting on current approach. So my optimistic prediction would be Friday @misaochan

Nearby has been refactored and I have verified that this does not exist on latest commits. Feel free to re-open this if someone faces this again :)

Was this page helpful?
0 / 5 - 0 ratings