Art of Submitting a Bug Report

1. Unless you are paying for support, don't expect anyone to contribute anything to your issue. Most people either echoes your problem and are happy to help a fellow internet stranger, or trying to build internet influence/karma, which makes the internet a surprisingly helpful space, but don't take anything for granted. I could have stared into the void with my free time instead of wasting it on your issue.

2. To help anyone with an issue the easiest route would be I, the answerer actually had the same issue as you before. This is extremely rare and don't count on it. Typically when that happens it means you didn't google enough.

3. The next way to get help is to give sufficient information for me to reproduce your issue with my own free time. This is why most repos ask for a reproducer repository. Even if you post a repo its a lot of effort for me to check out and build these. This is also why most repos ask for a reproducer as a fork of the example app, as the maintainer often has that example app checked and built. If you post some lazily formatted code snippet it's not going to get anywhere.

4. Another way to get help is to have sufficient debugging logs for me to give educated guesses on the problem. Most people dont do this anyways and I'm often too dumb to read logs.

Any other way of bug reporting is effectively wasting your own time.