@Gualtier Malde Thanks for your response here! At this point, do you think it's worth making the effort to release a build with a workaround? Or should we wait and see if a fix is in the upcoming 17.4.1 update? We could probably only handle a couple more weeks before this issue impacts a significant enough number of our users that we will have to do the workaround, but we don't want to push it out if it's not necessary. Thanks!