Do you happen to know if this is something that will be looked at? I’ve experienced this issue since this release was in beta and had to switch to the public version. Now that the public version is on 1.25.2.5319, I’ve had to revert back to 1.24.5.5173. We obviously can’t stay on this older version forever, so I’m hoping the next release will have it ironed out.
