Getting "Byte order could not be determined" error when opening up Ensight Case Gold files written from ANSYS Fluent 2021R2

My workflow is to have ANSYS Fluent 2021R2 write Ensight Case Gold files that i then post-process in paraview. I could successfully do this before with a different simulation (the ANSYS Fluent version and paraview version are remained the same), but for some reason, when i try to open my *.case file with this simulation, Paraview 5.10.1 spits out this error.

I am running a parallelized version of paraview but this error is also given when i run paraview on a single core. After doing some digging online, several people have encountered this issue. I have also applied the fixes to the encase/case file described in this thread.

ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTKExtensions/IOEnSight/vtkPEnSightGoldBinaryReader.cxx, line 4159
vtkPEnSightGoldBinaryReader (0x1dd4610): Byte order could not be determined.

ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTKExtensions/IOEnSight/vtkPEnSightGoldBinaryReader.cxx, line 332
vtkPEnSightGoldBinaryReader (0x1dd4610): Invalid part id; check that ByteOrder is set correctly.

ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTKExtensions/IOEnSight/vtkPEnSightReader.cxx, line 341
vtkPEnSightGoldBinaryReader (0x1dd4610): error reading geometry file lower_iha_primary_case.geo 0

ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkCompositeDataPipeline (0x17606b90): Algorithm vtkPEnSightGoldBinaryReader(0x1dd4610) returned failure for request: vtkInformation (0x1761adb0)
  Debug: Off
  Modified Time: 165820
  Reference Count: 1
  Registered Events: (none)

If i write the same Ensight file but in ASCII (as is an option that ANSYS Fluent provides), i can successfully open it. I prefer the file in binary because it’s smaller and will potentially open up faster.

EDIT: This issue also seems to be captured here.