Hi @Vision Pro Engineer I saw my post was linked. The error we were seeing is a fatal error which stops the scan entirely, we have tracked that this error is heavily tied to memory and reduced it. However, our users also have similar reports of the OP. I'm going to try to gather as much information as I can and submit a bug report, I'll link it here once it's complete.

We are also dealing with this issue. It seems to happen when the memory of the application starts to float at a level close to ~2GB (not a perfect metric, obviously depends on the phone and other factors). I found it happened consistently for us when we had a memory leak, and was able to be reconciled by really profiling the app, and making sure all memory is freed before performing another user scan.

We've recently started seeing this exception as well. Did you ever find the root cause?