Hi @aand,
Thanks for your reply.
The problem with this issue is that is it really rare. It only occurs if you’re using a specific, extremely uncommon combination of settings and choices. In fact, it is so uncommon that in 15 months, we only received your report. As a result, it wasn’t marked high priority.
So yes, we verified that it is a bug. Unfortunately, we do not have endless resources. That’s why we decided to allocate our resources to projects/issues/problems that affected more people.
I’ve been trying to find the conversation you had with our support team, but based on the information I have about you I cannot. We’d be more than happy to help you work around this problem if you reach out to our support team.
At the same time, you may have seen some movement on the GitHub issue. Our development team has added it to their queue, to investigate if it’s possible to resolve this problem. If so, they will. Otherwise, they’ll comment in the ticket why it’s not and close it.
Long story short, we’re sorry that we haven’t been able to fix the problem you encountered yet, even though this was a deliberate choice because of the low number of reports.
If you have any further questions, please reach out to our support team and refer to this conversation.
If you want to edit your review, you can do so here.
Thanks,
Taco