{L_BUTTON_AT}TMSupport
Hi,
Any news about my request?
(see my previous messages)
The issue has not been fixed in 4.2.28.
In which subsequent version will it be fixed?
We are waiting patiently and following the forum. Earlier you said it would be fixed in the subsequent version, the subsequent version did not contain the fix. It seems you are not delivering on your commitments.