“”::
“”: + anything in spotlight.
It crashes springboard and reloads in about half a second.
Sounds like SQL injection, actually more like a JSON injection… As if it’s trying to concatenate the input directly inside the value of a JSON dictionary, without proper escaping and/or encoding (base64 or hex, for example).
Possibly the input is being stored for user history (and, therefore, auto completion) purposes? Be it or not, something JSON-related is taking place here, from a kernel level or sufficiently deep so to cause a kernel crash (and rebooting).
(Sorry for jargons, I’m a developer seeing this issue through a developer lens)
Stuff likes this me think that modern technology is glued together random shit that somehow works, or at least as long as you are using your phone like a zoomer or a normie which only scrolls Facebook. The moment you do something that is not done by >90% of users, you will only encounter random fucking bugs and freezes (although these also happen when normally using an app, see YouTube Music in which it takes forever to load the library while offline completely making downloading songs completely useless).
I have a moderately new mid (mid-high?) range phone (from 2021) and it’s crazy how often software freezes or just glitches the fuck up, despite of running on a device that’s probably millions times faster than a computer used to launch people to the fucking moon. In no period of history the technology was so unresponsive as nowadays. I think it just went worse from mid 2010’s (or maybe even earlier) onwards.
I work in IT as PM, you’re pretty close.
Modern technology is glued together NOT random shit that somehow works.
Everything created has been built with a purpose, that’s why it’s not random. However, the longer you go on, the more rigid the architecture becomes, so you start creating workarounds, as doing otherwise takes too much time which you don’t have, because you have a dozen of other more important tasks at hand.
When you glue those solutions together, they work because they’ve been built to work in a specific use case. But it also becomes more convoluted every time, so you really need to dig to fix something you didn’t account for.
Then it becomes so rigid and so convoluted that to fix some issues properly, you’d have to rebuild everything, starting from architecture. And if you can’t make more workarounds to satisfy the demand? You do start all over again.
