# Issue with Marker Tracking App on Magic Leap 2

**URL:** <https://forum.magicleap.cloud/t/issue-with-marker-tracking-app-on-magic-leap-2/4293>\
**Category:** General\
**Created:** [September 26, 2024, 3:34am UTC](https://forum.magicleap.cloud/t/issue-with-marker-tracking-app-on-magic-leap-2/4293 "2024-09-26T03:34:15Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![etucker](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.magicleap.cloud/etucker/32/842_2.png) [@etucker](https://forum.magicleap.cloud/u/etucker)\
**Post date:** [September 30, 2024, 8:26pm UTC](https://forum.magicleap.cloud/t/issue-with-marker-tracking-app-on-magic-leap-2/4293/7 "2024-09-30T20:26:17Z")

</div>

We are tracking a similar issue with another developer. We currently think it is related to jumping too many version of the OS at once.

To note, this process above is not a workaround and is documented [here](https://www.magicleap.care/hc/en-us/articles/10731234815757-Magic-Leap-OS-Update-Path). However, we are doing further testing to see if when a device is updated using the prescribed process, the reboot behavior is reduced/resolved

1. **Rollback devices to 1.1.0 (check the "factory reset option, only during this step. Please leave unchecked for steps 2-4)**
2. Update 1.1.0 to 1.2.0
3. Update 1.2.0 to 1.5.0
4. Update 1.5.0 to 1.9.0

* * *

A future version of MLHub will help guide users through the update paths.

---

_[View the full topic](https://forum.magicleap.cloud/t/issue-with-marker-tracking-app-on-magic-leap-2/4293)._