>>Has anyone seen this?
The backend systems are frequently awkward and broken. Link to your own repos or bug-tracking systems.
>>It's already really frustrating & time consuming to get help from ST
The business structure is such that you should work through your local sales rep, or distributor, and the FAE / Support Engineer those relations provide.
Understand the purchase of a few dollars worth of parts does not buy you hundreds of dollars of engineering time, so you have to be doing an actual meaningful level of business to cover that.
Without NRE or willingness to pay realistic costs of engineering support / assistance, don't expect to see any.
I'd prefer to see problems addressed on the forum, not hidden behind the curtain of "support tickets", I don't like the opaqueness, but also understand a lot of support staff aren't equipped to deal with the hand-to-hand nature of forum interactions.
>>They say we can't help you if you are not specific.
Sure, problems are hard to solve, support staff aren't clairvoyant, vague "Doesn't Work" or "Help!" type request being particularly unhelpful. Don't get stuck in symptoms and tunnel vision, look at causes, if you can't see rational causes in the code you're looking at, look elsewhere. Superficial top-level code, especially as auto-generated, frequently isn't where the problems come from, you'll need to dig deeper.
Provide complete compliable source, perhaps provide as a github repo, and use that to communicate details, in a way you can control and edit, and then link to that in support tickets so you're not bound into failure of other's tools and methods.
