I’m replying for the most of the system requirement questions.
ARDK is officially supported on Unity 2020 LTS and Unity 2021 LTS.
Tested with the above LTS versions.
The project was being implemented in 2020.3.1f1.
Also tested to 2021.3.xf1 LTS versions too.
The officially supported Scripting Runtime Version in Unity is .NET 4.x Equivalent.
Yes runtime version was set to 4.x
minimum version 13 : Yes, the version was set
Developing with ARDK requires Mac OS Big Sur or better. Mac OS Catalina and earlier are not supported.
Yes using Mac OS, Ventura latest one, included the latest Xcode too.
Tested the application with iPad Pro 11th generation with iOS version 16.4.1 , as well as iphone 12 pro with iOS version 16.x.x.
While the system requirements you listed are accurate, we do not support iPad devices and are unable to provide guidance with them at this time. However, I see that you also notice these errors on the iPhone 12, so I will focus our support on that device.
Could you please describe the steps you took that caused the errors to appear? For instance, are you just using the sample scene, or did you create your own scene with edited scripts, etc? I have been unable to reproduce the errors you see on iPhone, so any details you could provide would be helpful in our troubleshooting.
I have also got the same crash on iPhone 14 pro. 2. folly::threadlocal_detail::StaticMeta<void, void>::onForkChild()
EXC_BAD_ACCESS (KERN_INVALID_ADDRESS)
Attached is the stack trace for your convenience.
Crash happens when the scan process is almost done. Say about 95% done. Does not happen often. Could not find a pattern.
Could you please provide the versions of ARDK and Unity you’re using, along with your device iOS? In your testing, would the crash happen periodically and randomly under the same conditions, or was it after something was modified, etc.? Are you just using the sample scene?
The crash happens almost every time the scan is almost close to done. If the scan size is not too big, it works fine. I could reproduce it multiple times with a 2.5 m range, scanning some medium-sized objects. For example, a two-seat sofa scan crashed 4 consecutive times.
The strange thing is that it worked fine before I updated the OS. I have a lot of changes in the code, but the core scanning code has been the same. Also, the app was working fine without any crashes with the existing code. But after I updated iOS 17.2, it suddenly started this.
Edit: I just found that I am using 2.5.1, and there has been some significant bug fixes on scanning framework in 2.5.2, I will try out 2.5.2 and see it it fixes the problem.
Scanning Framework Settings:
Reconstruction Mode: Detail
Mesh Quality: Very High
Texture Quality: High
Range: 2.5m
I tried to scan a 3 seat sofa, which can be considered as a medium size object.
Update Nov5 - 6.20 pm: I have turned down the mesh quality to medium and tried out 10 scans. It did not crash with the setting. But the mesh quality is a bit poor.
We recently had a report of a similar issue with iOS 17.2 and Scaniverse (it uses the same engine for scanning and processing as Scanning Framework). We are currently investigating internally, but I will reach out again once I have any more information. Thank you for letting us know!
It seems that Apple has resolved the bug with iOS 17.2, but are you still experiencing crashing?
I tested the Scanning scene in ARDK 2.5.2 on device (iOS 17.2.1) and Unity 2021.3.17f1 but have been unable to reproduce the crashes so far. I am consulting the team again to try and get to the bottom of the issue.
Just to confirm, I know you had said that it works fine if the scan is not too big, but at what point does it stop working? (for instance, is everything fine as long as you scan for less then 5 minutes, etc.).
@Stacy Sorry, i am still getting the crash in latest iOS update. 17.3
Is there any plan to add scanning framework in the new ARDK? Or any way/advice for me to debug this issue?
I am starting to present my app to b2b AEC space(Report, inspection) and the regular crash is kind of making me worried about the feasibility of my solution. I know the support is gonna end in a week, which is also a bad news for me. I am adding the crash dump here. Any help is very appreciated. Thank you
