timestamp on participant version history is very weird

[biblicabeebli]

Foundi it!

• We are using the old version values when we create a new app version history event, so the time recorded is the time that they CHANGED AWAY FROM the version listed.

beiwe-backend/authentication/participant_authentication.py

Lines 93 to 97 in 2172963

	## App and OS version tracking
	# get the existing version code info
	prior_version_code = participant.last_version_code
	prior_version_name = participant.last_version_name
	prior_os_version = participant.last_os_version

beiwe-backend/authentication/participant_authentication.py

Lines 116 to 124 in 2172963

	# attribute is updated in update_only
	if (prior_version_code != participant.last_version_code or
	prior_version_name != participant.last_version_name or
	prior_os_version != participant.last_os_version):
	# log(f"os version changed: {last_version_code} to {session_participant.last_version_code}")
	participant.generate_app_version_history(
	prior_version_code, prior_version_name, prior_os_version
	)

That's very silly, fix:

• The field currently in use to identify this one is the created on date
• this has a last updated field
• so we can transition this to "date of upgrade" by creating a new timestamp field, populating it from the history, and just creating an entry for the current version.
• (and last updated differing from created_on becomes an indicator that it was migrated)

Question: is anyone using this api endpoint?