Changing profiles pre init doesn't work

[jelmerS2]

I'm trying to assign a profile to MRTK prior to initialization due to cross-platform development.
There are several issues:
In this guide, SetProfileBeforeInitialization() is mentioned. This functions seems to not exist anywhere.

Following this guide, I run into the following errors at runtime:

• There's already a IMixedRealityInputSystem.Mixed Reality Input System registered!
• Failed to start the Input System!
• There's already a IMixedRealityFocusProvider.Focus Provider registered!
• Failed to register the focus provider! The input system will not function without it.

My script is taken from there and as follows:

using Microsoft.MixedReality.Toolkit;
using UnityEditor;
using UnityEngine;
/// <summary>
/// Sample MonoBehaviour that will run before the MixedRealityToolkit object, and change
/// the profile, so that when the MRTK initializes it uses the profile specified below
/// rather than the one that is saved in its scene.
/// </summary>
/// <remarks>
/// Note that this script must have a higher priority in the script execution order compared
/// to that of MixedRealityToolkit.cs. See https://docs.unity3d.com/Manual/class-MonoManager.html
/// for more information on script execution order.
/// </remarks>
/// 
namespace Assets.Scripts.Core
{

    public class ProfileSwapper : MonoBehaviour
    {
        public MixedRealityToolkitConfigurationProfile arProfile;
        public MixedRealityToolkitConfigurationProfile vrProfile;


        void Awake()
        {
            MixedRealityToolkit.Instance.ActiveProfile = vrProfile;

        }
    }
}

Script exec order is:

What am I doing wrong? Or is there a bug?

[keveleigh]

@MaxWang-MS made some fixes in #8787 for the upcoming MRTK 2.6 release which should better support this scenario.

[MaxWang-MS]

There are known issues with profile changing in the current releases of MRTK. Like @keveleigh has mentioned, these issues have been fixed and will be included in the upcoming 2.6 release. You can try them out now by using the mrtk_development branch and the code there corresponds to the first guide you mentioned.