1 hour ago, Ianrivaldosmith said:

Then how would they ever know the addons don’t work upon release? I’ve never understood this logic

Asobo aren’t responsible for add-ons, the developers creating the add-ons are responsible since they are the ones that created them.  

If you notice, one of the first responses to reporting of Beta bugs is “Did you disable all add-ons”.  This is asked in order to try and help remove the variables outside of Asobo’s control.

A good “real world” example going back to P3D.  LM fixed a bug with how nose wheel steering would operate, but because so many existing add-ons had worked with the bug “as is”, the change broke many add-on aircraft resulting in the need for many aircraft to be updated.

 

13 hours ago, SayAgain said:

Asobo aren’t responsible for add-ons, the developers creating the add-ons are responsible since they are the ones that created them.  

I never said they were?

I am well aware of that.

 

However, it would be naive to think that in a public beta environment, people are not going to use addons. In fact, I remember rather recently in the XP forums, a lot of people like yourself used to say 'don't use addons!', and then one of the devs stepped in and said 'actually, no. Use addons, we need every scenario tested, otherwise how will we ever know?' 

7 hours ago, Ianrivaldosmith said:

However, it would be naive to think that in a public beta environment, people are not going to use addons

Agree, and I never indicated otherwise.  

As a longtime developer, if someone reports and issue to me and I say what happens when you remove your add-ons and the user says I no longer have the issue, then I ignore the reported issue because there is nothing I can do about it until the add-on developer contacts me (if they contact me, which is rare because they have the source and can debug the issue).

I think it's naive to believe Asobo will contact all the add-on developers that users reported as problematic with a MSFS Beta release.  There are 1000's of add-on content providers, Asobo does not have the money or time for that.

If you want to take it upon yourself to report to the content/add-on provider that a Beta version of MSFS has problems with their product, sure that might help the add-on developer.  How the add-on developer responds to issues will vary, some will wait until MSFS goes "official" release before they test their product (common approach).  Some add-on developers will test with each Beta iteration of MSFS to see if there is anything significant they need to address or go to Asobo for additional information and/or problem.