Don’t take it personally. 
My advice isn’t intended to frustrate your efforts in fixing your problem; in fact, it was practical advice to show what you can do to move yourself forward. If you ask a broad question without sufficient clarity (e.g. some initial debugging results) then you could, conceivably, be waiting a very long time for an answer.
Moreover, a surprising number of people building software don’t know how to do the systems analysis to work out what to debug, or, if they do know what to debug, they don’t think in a systematic way that narrows the problem down. That’s not bad or wrong; they just need guidance on how to do that. In this context, I often think of that aphorism about “don’t give a man a fish, teach him how to catch his own”. 
With that in mind, you may find this advice useful.
(For what it’s worth, AI is making this phenomena worse, but it didn’t start it. The reason Stack Overflow attracts so many experts is that a free-for-all has not been tolerated, at least for the last ten years).
Super. What was it? Maybe someone else will find that advice helpful.