Scan Error on Android 12 Galaxy S10 SM-G973F/DS

  • Description of the issue: I’m using a Samsung Galaxy S10 SM-G973F/DS running on Android 12. ARCore is up to date and installed on my device. All permissions have been manually granted in the app settings. Opening the App and choosing any options to scan I first see the camera feed, as soon as I click the capture button the stripes appear, and no matter where I move my device nothing happens. I’ve been trying for 10 minutes / test, then pressed the stop button to finish the scan, but it gives me a “Scan Error” every time. The stripes do not disappear, nothing appears.
  • Date: 2024.Oct.28. (first time using the app)
  • Device type & OS version: Android 12, OneUI 4.1 , Samsung Galaxy S10 SM-G973F/DS
  • App version: V1.0.1(84)
  • Reproduction Steps: Tap New scan button. Select any option. Start scanning. Move device around for any amount of time. Press stop button. It says “Scan Error” while nothing happened in the background.

Thank you!

Hello,

I’m sorry for not getting back to you sooner. We did see your post and are still looking into this, seems to be a bug more than likely if everything else is up to date. I will get back to you as soon as possible.

Gotcha! Thank you so much!

Hello,

Would you be able to provide a logcat output of device when you try running Scaniverse? You will need android command line tools for this. Here is some documentation you can reference: https://developer.android.com/tools/logcat

Alternatively, you might be able to go into the Developer Options of your device and see if there is an option to generate a bug report. If there is, that should also include a log cat as well. Just make sure that you used Scaniverse and replicated the bug above before generating one so that we have some logged information to look at.

If you don’t see developer options on your device, this guide will show you how to enable developer mode: https://www.digitaltrends.com/mobile/how-to-get-developer-options-on-android/

Hi! I tried to replicate the issue but it seems to have gone away by itself. I’m not sure why or how but it seems to be working correctly now. It didn’t for days and now it does. I’m not sure how that’s even possible, but if I’ll have the issue pop up again I’ll take a bug report. Thanks!

Well that’s interesting. I’m glad it’s working now though. I was able to test on the same device you have and didn’t have that issue so we were looking into it but I’m glad it fixed itself.

If it does happen again please submit a new topic (you can link back to this one as well so we know we’ve worked with you on this issue before) so that we can take another look at it