This is my third week of attempting to trouble shoot this bug in Shapr3D beta.
Full disclosure I have development experience extensively in backend and a minor bit of iOS development in my personal history.
Exactly two weeks ago (October 27th) I made an edit on my windows Shapr3D Beta (history) app. As usual this synced to the cloud.
I attempted to open the app on iOS on my iPad a day or two later and instead of popping open like normal there was a brief loading screen “Loading… filename… processing” (see image below), and then the iOS app crashed back to the home screen.
The file was not able to be opened but there was no error message. I reached out to Shapr3D support via email and asked to have a previous version duplicated / restored. In this case file “version 93” (for ease of use, so that I can refer back to it).
Shapr3D restored the file at issue and appended the date to the file name to make it clear which was the duplicated / restored file and which was the original “version 93”.
When attempting to open the restored “version 93_date-restored” file there was no change in app behavior (issue persisted on newly cloned / restored OLDER version of the file); the iOS Shapr3D beta app crashed back to the home after briefly showing the loading screen image shown above.
At this point I thought that probably the issue was related to my user permissions within Shapr3D cloud. I reasoned that since “version 93” was created before the bug occurred, it couldn’t possibly be a corrupted file so on Friday I requested that the originally “version 93” file be dumped to .shapr file.
This morning I was notified that dumping the file will take some time, and I was on my way back into the office to use my Windows installation anyway, so I attempted to open the “version 93” original file on Windows (thinking perhaps there was an issue).
When I opened the Shapr3D windows beta app I was notified there was a new beta version for windows. I asked to download the update BEFORE opening (instead of in the background) and the Beta windows Shapr3D app restarted and then opened showing all my files as normal on my home screen.
The first file I attempted to open was the “version 93” file that had been inoperable for two weeks.
The file DID NOT open but DID (on the new Windows version) throw an error showing the the file was damaged and couldn’t be opened with text “Import Failed: Your source file couldn’t be loaded because it is damaged.” , see image:
The “version 93” file has never left the Shapr3D cloud, therefore any damage was caused by one of:
- Shapr3D Beta (Windows)
- Shapr3D Beta (iOS)
- the Shapr3D Beta cloud backend
Next I attempted to open the restored version which had been cloned by Shapr3D support with the date code appended “version 93_datecode”. The same exact error screen was shown.
After that I attempted to open another file, which HAD been working this morning on Shapr3D Beta iOS on my iPad, lets call this one “File 2”. I got the same message: “Import Failed: Your source file couldn’t be loaded because it is damaged.”
At this point I went to my iPad and attempted to open “File 2”.
The bugged behavior now replicated on the iPad / iOS Shapr3D Beta for “File 2” and that file was in-accessible.
Remembering that I had just updated Windows Shapr3D Beta, I closed Shapr3D Beta iOS and checked TestFlight: YES there was a new version. I updated the Shapr3D Beta from TestFlight to the latest version and attempted to open “File 2” - the behavior persisted.
At this point I have three files which can’t be opened:
- Version 93 (original File 1 that had issue on October 28th or 29th)
- Version 93_DateCode (restored by support)
- FIle 2 (just became in-operable today)
I am relaying this information to support but I am also posting the forum to save a future user who encounters this bug on Beta some time, and to see if anyone else knows of a workaround not yet suggested by support.
I will update here if I find a solution or get one from Support.