SP2 bug

For Titania and Mantis,
Their SP2 often misses on the second strike against an opponent unless that opponent is pinned against the wall. For Mantis this happens to me almost every time for Titania, I just started noticing it.
It happens after a MLLLM combo, throw SP2, first hit lands fine, the second misses. Sometimes with Titania it is not an issue because her rapid strikes lead to the next one landing or she is unlockable so they hit through block.
For Mantis it kills her SP2 completely.
I don't know if it is intended that these should only fully work when opponents are against the wall or not. Wanted to report just in case.
Their SP2 often misses on the second strike against an opponent unless that opponent is pinned against the wall. For Mantis this happens to me almost every time for Titania, I just started noticing it.
It happens after a MLLLM combo, throw SP2, first hit lands fine, the second misses. Sometimes with Titania it is not an issue because her rapid strikes lead to the next one landing or she is unlockable so they hit through block.
For Mantis it kills her SP2 completely.
I don't know if it is intended that these should only fully work when opponents are against the wall or not. Wanted to report just in case.
1
Comments
It was EXTREMELY frustrating when it took what should have been a perfect fight against enchantress and turned it into a huge mess by failing to knock her down and remove her spells, only to be immediately countered by her SP1 and damage reflection.
The way these newer champs work, bugs which break combos in the middle of specials need to be treated with urgency, because they can easily turn a victory into a loss.
I don't see this bug on the new trell9 board. Can we get any official acknowledgement that the team is investigating this?
I have a galaxy s20, and my Titania also has a hulk relic if that matters.
Would it be possible to get some acknowledgement that the game team is even aware of this bug? It's really killing the usability of my favorite champ in the game, and at this point, i have no idea when to expect that might change.