Transaction time problem
000exploit opened this issue · comments
Possibly related to #246, but I'm not sure.
I have identical time zone on both the server and my phone, but it shows a transaction 3 hours apart (my time zone assumes UTC+3). If I set the transaction date correctly in the web version, then the client shows me the transaction 3 hours earlier than the server, and vice versa. I have already tried to change the time zone settings, language, enable and disable the server time zone in the Waterfly settings, etc. Nothing helps, and I don't know what to do.
Screenshot from the same transaction of both server and client:
Hi, is this for all transaction or just a specific one? What does the server show when you update the time?
Is there really no difference when you do the timezone setting in the settings?
is this for all transaction or just a specific one?
For all transactions
What does the server show when you update the time?
The time in transaction is 3 hours ahead.
Is there really no difference when you do the timezone setting in the settings?
I have already tried doing this, no difference. The only thing I haven't tried is switching to a different timezone on both server and phone.
BTW, emansih/FireflyMobile shows correct time
Looking at this, and also your other bug report (where you provided a debug log) - do you have any special software or app restrictions running on your device? Any special OS? It seems like Android-internal communication channels are not working properly. The debug log of the other report should report the Device Timezone as well, but doesn't (only the Server Timezone, which is fetched via the API)... I'm honestly a bit confused here. I tested the apk you also installed (version 2703) on a completely fresh (stock) Samsung device and the debug log looks completely different than yours.
Could you please kill the app via the settings and re-start it from the launcher and see if the problem persists?
@dreautall I'm using LineageOS 21 (Android 14), I've already granted the app all permissions, and yes, I tried to kill the all and recheck it again. Nothing has changed in the OS itself between normal operation and these two reports. There may be a problem with Android 14 itself.