Feature Tool: Crash on import

[laultman]

Describe the bug

Since Unity 2020.3.11f1 the MixedReality Toolkit fails to "install" in a brand new Unity project.

Please note. If you initialize Unity project as described below then close Unity (all running instances) and restart Unity the problem does not surface. It only happens when Unity is running. I tend to have multiple projects open and this may affect the operation.

To reproduce

Create a new Unity project with 2020.3.11f1 or higher. Open the Build settings and switch to UWP app. Setup for HoloLens per MS Documentation. Build the project just to get a baseline. Open the MR Toolkit, follow the steps to feature selection. Select from all the options just the MRTK Foundation latest version. (have tried 2.6.0 to 2.7.2 with same result) Move to next step. Validate the selection. Select Import.

Expected behavior

On pressing Import, I expect the MR Feature Toolkit to show me the list of packages as it previously has done. I expect it should then indicate that the action has happened. (Before 2.7.2 it sort of left you hanging, you had to "know" to close the tool. 2.7.2 corrects that with explicit text.) I expect Unity to do the import and for the Mixed Reality menu to become available.

Screenshots

If applicable, add screenshots to help explain your problem.

Your setup (please complete the following information)

• Unity Version 2020.3.11f1
• MRTK Version 2.72

Target platform (please complete the following information)

• HoloLens 2 current build of win 10 for HL2

Additional context

Add any other context about the problem here.

[keveleigh]

On pressing Import, I expect the MR Feature Toolkit to show me the list of packages as it previously has done.

What does it do instead?

@davidkline-ms for visibility

[laultman]

Immediately terminates. Nothing happens.

Larry - On the go...

On Jun 25, 2021, at 1:45 PM, Kurtis @.***> wrote:



On pressing Import, I expect the MR Feature Toolkit to show me the list of packages as it previously has done.

What does it do instead?

@davidkline-mshttps://github.com/davidkline-ms for visibility

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/microsoft/MixedRealityToolkit-Unity/issues/10029#issuecomment-868731064, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE2VEMVXGKL2FDRDKEOP5ODTUS6CFANCNFSM47JTKZUQ.

[david-c-kline]

@laultman,

Can you post the log file from c:\users<yourname>\AppData\MixedRealityFeatureTool? That may help us understand what you are seeing.

[stale[bot]]

This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.

[IssueSyncBot]

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!