MR Feature Tool V1.0.2206.1 Preview crashes for MRTK3

[scrooksjr]

MR Feature Tool crashes whenever a feature from MRTK3 is selected and 'Get Features' button is entered.

The bug prevents a user from successfully selecting any feature under MRTK3 for import into Unity. However, I found I can import the 'OpenXR' feature from Platforms. Spent around 5 hours troubleshooting so need to validate if the issue is on your end.

To reproduce

Steps to reproduce the behavior:

1. Open Mixed Reality Feature Tool
2. Click on 'Start' button
3. Select Project Path to Unity Project version 2020.3.* or 2021.3.6f1
4. Select 'Discover Features' button
5. Under MRTK3 select any feature and press the 'Get Features' button

Expected behavior

After a feature is selected from MRTK3 and the 'Get Features' button is pressed the MR Feature Tool will close. The expected behavior would be to go to the next screen to validate and import MRTK3 feature.

Screenshots

If applicable, add screenshots to help explain your problem.

Your setup (please complete the following information)

• Unity Version [e.g. 2020.3 & 2021.3]
• MRTK Version [3]

Target platform (please complete the following information)

• HoloLens 2

Additional context

Have built several projects using the MR Feature Tool with MRTK version 2. Feature Tool worked before and as of today 8 July 2022 the tool will not get MRTK3 packages for import into Unity.

[david-c-kline]

@scrooksjr

Can you confirm the version of the MRTK3 package you are trying to download? I have seen on instance of this when we had to remove an earlier version from the feed. If it is before -pre.6, please refresh the feed and try again.

Also, it would be good to see the contents of the log file when the crash occurs. It may shed some light on the issue. The easiest way to access the log is to go to Settings > Diagnostics.

[david-c-kline]

In a separate conversation on the HoloDeveloprs slack channel, this was discovered to be an issue with a previously saved configuration in settings.

Some early access changes were made in 1.0.2206.x that likely caused this.

[david-c-kline]

Re-opening this since I misread the names on the two threads... Still need to confirm that this is the same issue.

[Spyispie120]

@davidkline-ms Hi @scrooksjr, I can't say for sure if we have the same problem since you didn't post the crash log, but mine crashed similarly like your. It turned out to be something related to "SSL connection could not be established".

I was trying to get MRTK 3 yesterday with the new MR Feature Tool 1.0.2206.1. However, the MR Feature Tool would not run after many tries of opening (noticed the program would run in task manager then crash). Similar to this #10664. The time that it somehow open, I checked the output log and it turned out to be something related to SSL connection could not be establish. Then I proceed to select a few MRTK 3 packages (MRTK Input & MRTK UX Components), then click "Get Features". The tool would tried to download a couple of package before decided to crash. From the log again, it also related to "SSL connection could not be establish". Similar to this issue #10636.

Temp fix: I thought this maybe somehow related to computer firewall, but it doesn't seem to be the case after turn off all of computer network firewall. I also tinkered with my router(Inseego) firewall settings, also didn't fix it. I decided to switch to a different network access point, using a different router(Netgear) instead, and it seem to fixed it. No more SSL connection problem. The program would open right away instead of keep crashing until somehow magically open. Downloading packages seem to go through without hitches. Another way I was able to get it work reliably is by using phone data, and tether my cell phone to my computer as internet access point.

I can't really provide any insight into why or what settings different between the routers, since a lot the settings are hidden away by OEM (probably for good reason). I will try to look into it more once I have more time, but this is the only temp solution I can come up with for now.

[Spyispie120]

Posting logs just in case anyone has any insight. Log when crashing: https://pastebin.com/W7wKbn1N

Log when tool import successful https://pastebin.com/gPJqCkX7

[Zee2]

@davidkline-ms , is there progress on this?

[david-c-kline]

@Zee2, looking at the logs to see what I can spot.

[david-c-kline]

@Spyispie120, thank you for the detailed description and the log files. There does appear to be something router related based on your testing. I will need to do some investigation to see if I can identify anything that might be a connection blocker and hopefully find something that can be added or changed in the tool to work around what you are seeing.

[GennaroBaratta]

Hi all, I had a similar issue, the log said there was an exception during connection. I did resolve importing one feature at a time.

[Zee2]

@Clandguth will take a look at seeing if he can get these issues to repro. The other folks here on the team are having a tough time reliably getting these crashes to repro. Will update!

[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 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!