runbox7
runbox7 copied to clipboard
runbox
"Undefined" ipo header when replying
When replying to a message, the word "undefined" is placed in place of the "reply header" (from, time, to, subject). Spotted once, could not reproduce even with the same message, message being replied-to has all fields (from and to email, subject not blank).
Since recently i get it every time, irrespective of the sender's client (desktop, phone app, automated email). HTML email seems to be a precondition.
( Runbox 7 build time: 2021-11-15T13:08:33.650Z )
Yes, I see this too now on HTML messages.
@kvviecien Could this be related to https://github.com/runbox/runbox7/pull/1120, or is it independent?
@gtandersen There is a possibility my fix could break after fixing the headers for recent Sentry issues, because that's the same part of the code. I will look into it again.
This appears to be much better but can still be reproduced with some messages, e.g. with https://runbox.com/app/#Inbox:12205016 in the test account.
@kotecky Thanks for the updates.
Do you mean that the error occurs when replying to one recipient but not when replying to more than one recipient?
@gtandersen, that's what I meant, but did not try. A hypothesis to be tested.
Not reproducible any longer with the above example message.
Closing issue; reopen if it occurs again.
@gtandersen To be reopened as it is currently happening again. @gtandersen Issue still there.
@kotecky Issue reopened.
Would you be able to provide an example message (your Runbox username and the message's ID from the browser URL) via Runbox Support?
Thanks!
But i have the impression that it has to do with the state (slow XRH or something) rather than the message itself - sometimes it kicks in ("undefined") for one message but not when trying the second time for the same message. A third attempt would be again "successful" in reproducing.
But i have the impression that it has to do with the state (slow XHR or something) rather than the message itself - sometimes it kicks in ("undefined") for one message but not when trying the second time for the same message. A third attempt would be again "successful" in reproducing.
@kotecky Thanks for the additional details. This then appears to be performance related and not caused by a bug per se.