How to deal with problems on some phone models?

Question

Android

Good afternoon.
I have been working with RN not so long ago and I had one problem that I encountered while working - different phone models work differently with third-party (and not only) components.
And yes, you can find a lot of closed searches on them, but sometimes the solutions there are far from obvious, just "make it work on this model", while it's not a fact that it won't break something else and whether it will work generally. And there are a lot of such problems, and they can be identified only after the deployment, when complaints are received from customers.

In this connection, I have a few questions:
1. Is the only solution is testing on "farms"?
2. How do well-known applications such as Telegram, Viber, WhatsApp, etc. achieve fault tolerance?
3. Is there a list of "Tested" components that have already been tested?
4. Perhaps there are some basic principles that would somehow minimize these problems?
5. Do I need to pump in native android or ios sufficiently to understand all the intricacies? (Then why is RN really needed ...)

If you answer at least one question, I will be very grateful!

PS Expo is no longer suitable.

Answer 1

Unfortunately, Android is such a thing that every phone has its own very specific glitches. For example, one of my applications stubbornly crashes on Honor / Huawei, and not always and not at all. But it works stably on Xiaomi, Samsung, Sony, LG, BQ, Highscreen and others. So far I have not found a solution, given that I do not have Honor / Huawei myself, and the libraries used are more than standard - from pure Android, not even GMS.
For questions:
1. The only option is because of the large zoo, and it's not a fact that there will be no glitches on a specific firmware version in a specific country.
2. They test long and hard, on all devices, plus log analysis in case of failures on release versions.
3. Components, that is, probably, but this is not a guarantee that the manufacturer will not break anything in the new firmware.
4. Try to work out any potential mistakes as detailed as possible, even through a banal try-catch
5. No need, over time the necessary skill will be pumped, and if you just cram it, it will quickly be forgotten without use. But this does not mean that you do not need to read interesting articles about typical mistakes for yourself.

Answer 2

1. yes, but you can ask users to test many things by purchasing problematic models due to a glitch
2. money
3. xs, I personally thought that the browser (webview) is already it
4. first, tell me what problems, they all have different and depend from tasks
5. something tells me that in the end I will have to, or to reduce the costs of item 2. or just to understand (if I just touched on these problems, and I don’t understand) where exactly these problems stem from,
I’m afraid the farm test cannot be avoided in any case, if your application is more complicated than hello world, especially if it climbs somewhere further than ui and
react native internet these are actually electron (chromium) based applicationsWebView (maybe based on firefox), and it takes a lot of headaches when you don't want to tinker with the features of audio and video rendering (for example, playing video) and access a lot of things that are not very standardized in android.
The browser (chromium) is already an operating system in itself, which takes on a lot of work, supports the standards of working with some peripherals, but not for free .... it stupidly eats resources.
If you suffer from react native problems, try to develop something on just android (java), supporting from the heels of the current versions of platforms even within the same smartphone model, you will immediately realize that it was not suffering, but just minor inconveniences.
ps The size of the test farm for truly native android applications (I'm talking about binary code, literally, the one that is built for the corresponding arm architecture), even if it's just a module (like telegram's ffmpeg for playing videos, for example), will become even larger.