From ce273a162cd34df8d6e07ba47f1b95535afeab4e Mon Sep 17 00:00:00 2001 From: Andy Porras Date: Tue, 31 Dec 2024 12:14:43 -0600 Subject: [PATCH] Fix incorrect Unix epoch date displayed for uploaded GNSS traces Resolved an issue where OSMTracker displayed the Unix epoch as the date for all uploaded GNSS traces instead of the actual capture date. The problem was consistent across all uploads and affected the user interface. The correct date and time are now shown within the app, aligning with the information reported on the OSM site. --- app/src/main/java/net/osmtracker/activity/TrackDetail.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/java/net/osmtracker/activity/TrackDetail.java b/app/src/main/java/net/osmtracker/activity/TrackDetail.java index 5f4eb6d9..72d08a79 100644 --- a/app/src/main/java/net/osmtracker/activity/TrackDetail.java +++ b/app/src/main/java/net/osmtracker/activity/TrackDetail.java @@ -181,7 +181,7 @@ protected void onResume() { if (cursor.isNull(cursor.getColumnIndex(TrackContentProvider.Schema.COL_OSM_UPLOAD_DATE))) { map.put(ITEM_VALUE, getResources().getString(R.string.trackdetail_osm_upload_notyet)); } else { - map.put(ITEM_VALUE, DateFormat.getDateTimeInstance().format(new Date(cursor.getLong(cursor.getColumnIndex(TrackContentProvider.Schema.COL_EXPORT_DATE))))); + map.put(ITEM_VALUE, DateFormat.getDateTimeInstance().format(new Date(cursor.getLong(cursor.getColumnIndex(TrackContentProvider.Schema.COL_OSM_UPLOAD_DATE))))); } data.add(map);