I’m sorry that you get hit by these issues - we always try to deal with problems as soon as we can, but please understand we are, as you can probably see from the number of open issues, always busy.
We have to prioritize and that sometimes can mean some issues get no or little attention for a long time. If these really bother you as home user you can try to find somebody with developer knowledge who can fix them, if it bothers you as enterprise user perhaps you can contact our sales team.
Also note that github is NOT a support platform: saying that you get an error is not very helpful. You can ask here, if somebody can figure out what is wrong, or use github to report a specific bug after you’ve found the core issue. That is not the case with the problems you mentioned - so those bug reports are not helpful to us.
Let me put it differently: you have to do the work to identify the root cause so our developers can fix it right away. Example code, curl examples or example apps are good ways of showing what is wrong, and we very much welcome patches and links to the relevant code. Also, please make sure you have tested if the issue also happens on the latest daily build of Nextcloud. You can learn how to set up a developer instance here: https://docs.nextcloud.com/server/latest/developer_manual/
Of course, if you can’t do this debugging, you can ask other home users who might be willing to help or give pointers. If nobody wants to help, sorry, there’s not much that can be done other than that you put in more time yourself. If your business need this issue fixed, we’re happy to do the debugging for you as part of our subscription services.
meanwhile, complaining here and on other channels that we don’t take your issues serious isn’t really a motivation for us to fix them, sorry. We have loads of work and loads of issues and we don’t get paid to fix your problem.