Nc21 tracks keeps loadings sign

[Tazzios]

I have 2 Nc setups one with 20 and one with 21. In the 20 the tracks were shown in the 21 the same tracks was not. I now just update my NC20 environment and now the tracks also won`t load there anymore.
For one site i use hanssonit vmware image the other on a regular shared hosting.

I hope i did not overlook an already existing issue.

[dasarne]

Same here.
I use the docker-image (nextcloud 21.0.0) with archlinux.
./occ maps:scan-photos and ./occ maps:scan-photos and even starting cron.php doesn't change this behavior.

[realmicu]

Exactly the same problem. I'm using official docker image with NC 21.0.0 (fpm) and maps 0.1.8.
Looking at browser console, it shows "Uncaught SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data". Apparently GPX files no longer get processed correctly.

[tacruc]

Can you paste the received tracks data. Somewhere in the browsers network monitor should be a get request for tracks.

[Tazzios]

Not sure what you are looking for but this is the only thing with track in the firefox console
Uncaught SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data jQuery 2 addTrackMap tracksController.js:294 getTracks tracksController.js:422 jQuery 7 getTracks tracksController.js:410 toggleTracks tracksController.js:153 restoreOptions script.js:284 jQuery 7 restoreOptions script.js:124 <anonymous> script.js:2139 jQuery 12 Webpack 6

other things maybe relevant
De bron van ‘https://xxx/apps/files/’ is geblokkeerd vanwege een niet-overeenkomend MIME-type (‘text/html’) (X-Content-Type-Options: nosniff).

Content Security Policy: De instellingen van de pagina blokkeerden het laden van een bron op inline (‘script-src’).

Handlebars is deprecated: please ship your own, this will be removed in Nextcloud 20

[realmicu]

@tacruc:
Using network monitor, here is what I get for 'GET apps/maps/tracks' request - response payload is:
[{"id":2376,"file_id":1272,"color":null,"metadata":"","etag":"fc4537e367f49430806250867d0011dc","mtime":1594306367,"file_name":"my_route_0000.gpx","file_path":"\/Routes\/Bike\/my_route_0000.gpx"},{"id":2423,"file_id":10164,"color":null,"metadata":"","etag":"cb5d8ec3266b962cdfc5ca2a24867463","mtime":1615465459,"file_name":"my_route_0001.gpx","file_path":"\/Routes\/Bike\/my_route_0001.gpx"}]
(above is just an example, I have more valid routes but they are all look similar - metatada is an empty string). I have verified in NC database that cache etags and files on disk indeed do match each other and all are accessible.
Photos also cannot be viewed in full window (thumbnails are shown correctly on the map though), but I think it has already been reported elsewhere.

[tacruc]

But it seams, that the json does not end correctly. Can you check, what's the end of the response. How long does the response take. Could it be a problem of php max execution time or could you additionally check if increasing the php memory limit helps?

[dasarne]

This is the call I grabbed for you (https://nc.xxx.xx/index.php/apps/maps/tracks)
json.txt

[roydenyates]

Is the metadata entry in the DB meant to be empty, because it is on my nextcloud which has the problem described here?

All the gpx tracks are present in the DB, but every metadata variable is missing.

[realmicu]

@tacruc:
php max execution time is set to NC default (3600 seconds), I've increased memory limit to 1G (was 512M), does not help at all.
Response time for 'GET tracks' is just under 1 second so it obviously does not hit the time limit.
Response header (as provided by Firefox Network console):

HTTP/1.1 200 OK
Server: nginx/1.19.3
Date: Mon, 29 Mar 2021 10:34:12 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 2726
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate
Content-Security-Policy: default-src 'none';base-uri 'none';manifest-src 'self';frame-ancestors 'none'
Feature-Policy: autoplay 'none';camera 'none';fullscreen 'none';geolocation 'none';microphone 'none';payment 'none'
Content-Encoding: gzip
Strict-Transport-Security: max-age=15768000; includeSubDomains;
Referrer-Policy: no-referrer
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: none, none
X-XSS-Protection: 1; mode=block

and for above header response payload is:
(content removed)
This is complete response as seen by browser network tool.

[Julianoe]

Hi! Just wanted to say I get the exact same bug. Nextcloud 21, Maps 0.1.8.
I get the infinite loading of tracks that never displays them.
I have recorded my tracks with the RunnerUp app on Android and they open properly on the other app GPX Viewer.

I get the similar error Uncaught SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data in the console.

I also grabbed the request from the network tab on my brower

[{"id":12,"file_id":531931,"color":null,"metadata":"","etag":"137943c34def42031ea6d3b34b52b1a8","mtime":1610313461,"file_name":"RunnerUp_2021-01-10-17-26-20_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-01-10-17-26-20_Running.gpx"},{"id":13,"file_id":532870,"color":null,"metadata":"","etag":"4060d4ddcd1b29ee49e3cfcaecf44483","mtime":1610994197,"file_name":"RunnerUp_2021-01-18-18-51-56_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-01-18-18-51-56_Running.gpx"},{"id":14,"file_id":549493,"color":null,"metadata":"","etag":"b448167c176335d0fe167f6f5936cdde","mtime":1611078346,"file_name":"RunnerUp_2021-01-19-15-09-24_Walking.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-01-19-15-09-24_Walking.gpx"},{"id":15,"file_id":549428,"color":null,"metadata":"","etag":"0e680369374baf0fcf3dee529d5a8826","mtime":1611850979,"file_name":"RunnerUp_2021-01-28-16-44-18_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-01-28-16-44-18_Running.gpx"},{"id":16,"file_id":549555,"color":null,"metadata":"","etag":"6506dbb1b454973704809eabc8eb5dd7","mtime":1612374139,"file_name":"RunnerUp_2021-02-03-18-15-45_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-02-03-18-15-45_Running.gpx"},{"id":17,"file_id":549435,"color":null,"metadata":"","etag":"f69d44b79ea3fe01da95332680a92adb","mtime":1614191343,"file_name":"RunnerUp_2021-02-24-18-48-20_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-02-24-18-48-20_Running.gpx"},{"id":18,"file_id":549458,"color":null,"metadata":"","etag":"d09022c8a440a8a50ef07aea35c4ea21","mtime":1614520886,"file_name":"RunnerUp_2021-02-28-13-58-48_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-02-28-13-58-48_Running.gpx"},{"id":19,"file_id":549510,"color":null,"metadata":"","etag":"82c103e014f67325e09f750400ae6904","mtime":1615553297,"file_name":"RunnerUp_2021-03-12-13-07-05_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-03-12-13-07-05_Running.gpx"},{"id":20,"file_id":549420,"color":null,"metadata":"","etag":"cf8b9a7f807c1b021eff9b5f39c9adc8","mtime":1615560107,"file_name":"RunnerUp_2021-03-12-13-48-36_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-03-12-13-48-36_Running.gpx"},{"id":21,"file_id":549548,"color":null,"metadata":"","etag":"35b601cff2106b261c8e5584305bacc7","mtime":1615560538,"file_name":"RunnerUp_2021-03-12-15-43-17_Running.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-03-12-15-43-17_Running.gpx"},{"id":22,"file_id":549467,"color":null,"metadata":"","etag":"40640b6aadcaede9397b058dca0f6686","mtime":1617561489,"file_name":"RunnerUp_2021-04-04-16-58-24_Walking.gpx","file_path":"\/Documents\/Runnerup\/RunnerUp_2021-04-04-16-58-24_Walking.gpx"}]

I don't really see how this request can be considered as bad json :/
Any idea?

Here is the content of the maps_tracks table of the DB

MariaDB [cloud_db]> SELECT * from maps_tracks;
+----+---------+---------+----------------------------------+-------+----------+
| id | user_id | file_id | etag                             | color | metadata |
+----+---------+---------+----------------------------------+-------+----------+
| 12 | julien  |  531931 | 137943c34def42031ea6d3b34b52b1a8 | NULL  |          |
| 13 | julien  |  532870 | 4060d4ddcd1b29ee49e3cfcaecf44483 | NULL  |          |
| 14 | julien  |  549493 | b448167c176335d0fe167f6f5936cdde | NULL  |          |
| 15 | julien  |  549428 | 0e680369374baf0fcf3dee529d5a8826 | NULL  |          |
| 16 | julien  |  549555 | 6506dbb1b454973704809eabc8eb5dd7 | NULL  |          |
| 17 | julien  |  549435 | f69d44b79ea3fe01da95332680a92adb | NULL  |          |
| 18 | julien  |  549458 | d09022c8a440a8a50ef07aea35c4ea21 | NULL  |          |
| 19 | julien  |  549510 | 82c103e014f67325e09f750400ae6904 | NULL  |          |
| 20 | julien  |  549420 | cf8b9a7f807c1b021eff9b5f39c9adc8 | NULL  |          |
| 21 | julien  |  549548 | 35b601cff2106b261c8e5584305bacc7 | NULL  |          |
| 22 | julien  |  549467 | 40640b6aadcaede9397b058dca0f6686 | NULL  |          |
+----+---------+---------+----------------------------------+-------+----------+
11 rows in set (0.003 sec)

[ruddyj]

Having the same issue on NC21, Maps 0.1.8.

Uncaught SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
jQuery 2
addTrackMap tracksController.js:294
getTracks tracksController.js:422
jQuery 4
jquery-migrate.min.js:2:2468

[vantino]

metoo - is there some workaround in sight ?

[Ablu]

It seems to try to de-serialize the metadata field (which is empty for me (and also seems to be empty for everyone else in this issue)):

So probably the maps:scan-* jobs are supposed to fill it (but somehow they don't?)

[Ablu]

Hm... Though the code always seems to add the metadata empty:

maps/lib/Service/TracksService.php

Line 284 in 9facdf4

$metadata = '';

The code of the UI also was not changed recently... So not sure what might cause this suddenly? (I personally cannot confirm that this only happens after an update, I only enabled Map after the 21 update).

[Ablu]

Ah.

maps/lib/Controller/TracksController.php

Line 131 in c639d0b

$metadata = $this->tracksService->generateTrackMetadata($trackFile);

seems to be responsible to generate it once the track is requested. But I guess since the track is never requested that does not happen.