Command Search Bug on iPad

Need help? We are here.
1

I’ve attached a video below showing the issue in detail. The issue is non-existent on MacOS, this only seems to affect iPad.

When searching for a command on an iPad, the first character typed causes the cursor to move back before the character, causing it to type the word incorrectly. As you can see from the video, this is extremely frustrating and causes a significant slowdown in workflow.

My iPad setup is normal, and I use all official Apple products. This does not happen in other software, and only Shapr3D is affected.

Video is below :arrow_down:

A fix for this ASAP would be fantastic. I’ve tried to deal with it for months now and I’ve just given up and can’t really use the software effectively at speed on iPad, causing me to move away from it and onto MacOS only. A shame really considering I invested £1.5k into my iPad setup for the main purpose of Shapr3D.

Thanks for all your help Shapr3D team :slight_smile:

2

I couldn’t reproduce the problem on my end. Could you please share the following details to help us investigate further?

  1. Your iPad’s hardware and software specifications.
  2. The version of Shapr3D you’re using.
  3. The .shapr file where the issue occurs.

If you prefer to share this privately, feel free to submit a ticket on our support portal here.

3

Hi Lys,

I have discovered more on this issue. Please see the video for evidence.

It seems to be caused by using the Apple Pencil in combination with the Apple Magic Keyboard (or any keyboard, tested this with a MX Mechnical from Logitech as well). The issue is bizarre, but hopefully, this new video will help you replicate it.

Sure here are the details:

iPad Pro (11-inch) (4th generation)
iPad OS 18.3

iPad Keyboard is the Apple Magic Keyboard.

App version (Shapr3D) 5.770.0.7944 #b80e3ce3

There is no specific .shapr file that is affected, it happens on every file, new or old.

Thanks,

Ben

4

@Lys any update on this?

5

Thanks for bringing this to our attention. I’ve forwarded the issue to the relevant developers for review. While I can’t promise you a timeline for a fix, I did find that using an external Bluetooth keyboard does not encounter the same issue.

Thank you for your understanding and patience.