from the first paragraph of the article, it sounds like they share your feelings:
Battery technology is one of those areas that is getting a lot of promising research results but very little in the form of commercial products we can use to power digital devices, electric vehicles, or off-grid homes. That may soon change thanks to sodium-ion batteries that are safer, more durable, and cheaper to manufacture when compared to conventional lithium-ion batteries.
This seems wrong to me. Existing paradigms like try catch or returning result codes enable handling these situations gracefully and in an informed manner. Making an inert api as is suggested here means that now you have an api that doesn’t behave as expected but without an explanation why.
“The app was probably only tested against a PC so an exception would be unhandled” means that they did not implement it well against a PC. There are a bunch of possible reasons you’d get an exception while adding a printer on a PC, and I can’t imagine that the correct behavior would be to crash whatever it is you’re doing.