please clarify: Using GameObject.AddComponent is no longer allowed and will throw an exception

beta 22 release notes:

Does this mean that AddComponent<RigidBody>() will now break?

 

Code (CSharp):

1. using UnityEngine;
2. using System.Collections;
3.  
4. public class test : MonoBehaviour {
5.  
6.     IEnumerator Start () {
7.         yield return new WaitForSeconds(4.0f);
8.         this.gameObject.AddComponent<Rigidbody>();
9.     }
10.  
11. }
12.  
13.  

Works for me using B21.

 

The OP is taken from the beta 22 release notes. Not beta 21!

 

Scary, very scary stuff. We would like some clarification on this as well please.

 

It seems to imply you could previous call AddComponent with a non-monobehaviour class and it'd work automagically? If so, that was some sneaky dirty behaviour =)

 

If only MonoBehaviours were intended to be added with "AddComponent", 1) Why would it be called "AddComponent"? and 2) Why would it accept any Component class rather than only MonoBehaviour classes?

Also, I made a test project with b22. AddComponent<Rigidbody>() and AddComponent(typeof(Rigidbody)) do not throw any exceptions... EDIT: See below.

 

and fixed in the release notes....ah, html escaping. bah.

 

Phew

 

@Tautvydas Zilys Can you explain why do that ?

It's a big problem for me, i have a class like this in my project :

Code (CSharp):

1. public abstract class ManagerBehaviour<T> : MonoBehaviour where T:MonoBehaviour
2. {
3.     protected internal static T m_instance;
4.  
5.     public static T GetOrCreateInstance()
6.     {
7.         if (m_instance == null)
8.         {
9.             m_instance = new GameObject(typeof(T).Name).AddComponent<T>();
10.         }
11.         return m_instance;
12.     }
13. }

So i can't do that anymore ?

Edit : I tested this code and it's ok, but i don't understand what have change so ?
I have an AddComponent exception with this code :

Code (CSharp):

1. CrashReporting.Init( "XXX", "XXX", "XXX" );

 

Ok thank you

 

We are also getting the "AddComponent with Monobehaviour is not allowed." error with the following call:
UnityEngine.CrashLog.CrashReporting.Init("XXX", "XXX", "XXX");

I'm assuming you'll fix that, but in the meantime, will CrashReporting still work as before?

 

See http://forum.unity3d.com/threads/performance-reporting-throws-error-at-init-beta-22.412298/