Unity Editor version (if applicable):
ML2 OS version:
ML Hub version:
Magic Leap Application Simulator (ZI) Runtime version:
Magic Leap App Simulator for Unity (if applicable):
Host OS: (Windows/MacOS)
Sonoma 14.0 (23A344)
Please do not submit without first getting a ZIP of your logs from:
^^^ got 404 - PLEASE FIX YOUR ERROR-REPORTING LINK!
Don't forget to attach the logs!
@Magic Leap Team: please make this error reporting friction lower. How about your Hub Home screen having a "Report a Problem" button that directly integrates with your forum here? You could streamline getting the relevant version information you're asking for in the above preamble, instead from "aboutVersions.txt"
I get this in the Unity console:
[ZIF] App Sim runtime path discovered: /Users/otri/MagicLeap/tools/zi/v22.214.171.12430814/
When packages are pulling in the newer release "v126.96.36.19930919".
If I try to start a session, it fails:
"No Magic Leap App Simulator session is running. Exit Play mode and start App Simulator before entering Play mode again."
Then after that warning, it tries continuing, but generating more errors:
Error: MLZIIsServerConfigured in the Magic Leap API failed. Reason:
MLResult_NotImplemented UnityEditor.XR.MagicLeap.AppSimShimLibSupport:CheckForLibrarySearchPaths () (at ./Library/PackageCache/com.magicleap.unitysdk@ce854badf960/Editor/MLAppSim/AppSimShimLibSupport.cs:111) Failed to detect running Magic Leap App Simulator session, or a running session if any is not compatible (e.g. protocol version is different between the frontend and the backend). UnityEditor.XR.MagicLeap.AppSimShimLibSupport:CheckForLibrarySearchPaths () (at ./Library/PackageCache/com.magicleap.unitysdk@ce854badf960/Editor/MLAppSim/AppSimShimLibSupport.cs:111)
.. etc ..
So, it seems some automatic discovery fails (detects older app sim), and then cascades onto the other problems in AppSimShimLibSupport.cs loading the wrong DLL and unable to find the corresponding support functions.
I find it really tricky whenever a release goes out that we get prompted to upgrade all over the place, but once any part in the stack upgrades, we get a whole heap of pain. Let's get this smoothed out please. ML2 Hub is the one central place that should prompt to download a set of updates.
ML2 Hub could tell us what the compatible set of packages are that work with a particular release. There's no sense in having modularity if any part of that modularity can break everything. So, when I say Platform your release, it means making a set of modules that all go out in unison. The developer chooses which platform they want to move to, and the platform tells the developer clearly what they need to be working with.
And without further ado, here's the logs, but had to scrub the confidential stuff.
MLHubLogs-20231027-162746-macOS.zip (352.6 KB)