+1 here, but with some additional detail. I looked back through some backup versions of .version and launcher_profiles.json and was able to determine some things:
From what I'm seeing, LastUsed is generally not being updated. AND this is not new to launcher 2.2.1259 but instead also happened for sure in versions back through 2.2.911, and possibly in versions prior to that as well.
What do I mean by 'generally'? It seems LastUsed is not updated when a profile is launched/played. However it does seem to be updated sometimes, apparently when a profile is updated:
My 'latest version' profile had a LastUsed of "2020-12-31". On 2021-01-23, I launched this profile. At that time it updated from 1.16.4 (I believe) to 1.16.5. At that time the LastUsed field DID get updated. But I've launched that profile a couple times since then and that LastUsed hasn't changed.
My 'forge' profile had a LastUsed of "2020-11-28". It seems to have remained there until 2020-12-31 when I updated forge to a newer version. At that time, LastUsed also updated to "2020-12-31". But it has not updated again since then. Keep in mind that I play this profile often, at least every 2-3 days minimum.
It seems the version check is now for a specific java version, where I suspect it used to be an 'at least or greater' version. I see this in the launcher log where this previously worked fine with JDK11, JDK14, etc:
Standalone Windows Launcher version 2.2.10327. Not using MS store at all.
I had confirmed a bit ago this issue was still happening (ie profile's lastUsed field not being updated when launched) while logged in with my Mojangaccount. However, and unbelievably, I migrated that account to a Microsoft account just now and after logging back in to the exact same launcher the problem no longer seems to occur. I can see lastUsed timestamp being updated with each profile launch. So for whatever that's worth, migrating my account might have inexplicably fixed it.
+1 here, but with some additional detail. I looked back through some backup versions of .version and launcher_profiles.json and was able to determine some things:
From what I'm seeing, LastUsed is generally not being updated. AND this is not new to launcher 2.2.1259 but instead also happened for sure in versions back through 2.2.911, and possibly in versions prior to that as well.
What do I mean by 'generally'? It seems LastUsed is not updated when a profile is launched/played. However it does seem to be updated sometimes, apparently when a profile is updated:
My 'latest version' profile had a LastUsed of "2020-12-31". On 2021-01-23, I launched this profile. At that time it updated from 1.16.4 (I believe) to 1.16.5. At that time the LastUsed field DID get updated. But I've launched that profile a couple times since then and that LastUsed hasn't changed.
My 'forge' profile had a LastUsed of "2020-11-28". It seems to have remained there until 2020-12-31 when I updated forge to a newer version. At that time, LastUsed also updated to "2020-12-31". But it has not updated again since then. Keep in mind that I play this profile often, at least every 2-3 days minimum.
Hope that helps!
Maybe a regression of
MCL-12104?Using launcher 2.2.3555 and see this issue too.
It seems the version check is now for a specific java version, where I suspect it used to be an 'at least or greater' version. I see this in the launcher log where this previously worked fine with JDK11, JDK14, etc:
Can confirm issue still present after updating to 2.2.7206 (Windows). That seems to be the latest for me, released only early this morning (Nov 2).
Standalone Windows Launcher version 2.2.10327. Not using MS store at all.
I had confirmed a bit ago this issue was still happening (ie profile's lastUsed field not being updated when launched) while logged in with my Mojang account. However, and unbelievably, I migrated that account to a Microsoft account just now and after logging back in to the exact same launcher the problem no longer seems to occur. I can see lastUsed timestamp being updated with each profile launch. So for whatever that's worth, migrating my account might have inexplicably fixed it.