The timestamp which is displayed in the App on the Exposure Detection view ("Aktualisiert: Heute, 02:25") is inconsistent with what is displayed by the iOS "COVID-19-Kontaktprotokoll" ("Heute, 00:25").
This is confusing and probably due to a wrong interpretation of timezones, since the timestamps displayed in the App and in the iOS settings should be the same, according to the timezone which is set in the device settings.
The timestamps displayed for exposure detection in the app should be the same as the ones displayed in the iOS settings.


It seems that the timezone handling in the app is not quite correct. Exporting the contact protocol from the iOS settings shows the original timestamps:
{
"Hash" : "...",
"RandomIDCount" : XXXX,
"MatchCount" : 0,
"DataSource" : "de.rki.coronawarnapp",
"Timestamp" : "2020-07-03 00:25:48 +0200"
}
This means that the update was done at 00:25 CEST (UTC+2), not at 02:25 CEST
Interesting. What is your time zone setup? I have automatic, Berlin and don鈥榯 experience this problem.



@jwildeboer I have the same timezone setting (automatic, Berlin).
The screenshots that you have posted are not the issue. This is consistent for me as well.
What does your in-app update timestamp say? Is it 21:31 as well?
I could now confirm this on another iPhone: the CWA last update timestamps are two hours later than the correct timestamps in the system exposure notification settings
@palminx my app shows the same time, that鈥檚 why I said I don鈥檛 see the problem on my side. 
OK, that's interesting. As I said, I have seen this in two different phones now.
The two phones I checked have the language set to German, yours is English.
Just to add more data:
Timestamps are consistent on my phone (iPhone X - iOS 13.5.1). Language set to English. Time zone Berlin, automatic.
Last night鈥檚 update now shows consistent timestamps. I switched to English language settings and back, and now I cannot be sure if this is related to the language setting. I will check again tomorrow.
I guess the time stamps are fine now? Safe to close this bug?
I haven't been able to reproduce this issue for the last two days. It seems that there is/was some initial condition which made it appeared, which is no longer applicable.
Closing