Comment 5 for bug 1948540

The issue is that all the sorrounding code is not aware of a failure.
This applies to the string for the backend in the same way.
There we must add some extra null checks and than we can finally remove the assertion.
I didn't not think we need a warning at all.