But better would be to find the reason for the errors. You need to fix it at Rhino before, for example explode and join with a lower tolerance or manual join naked edges ( JoinEdge). As you can see the NURBs surfaces are not of equal density and edge loops plus seams do not marry up nor do they stay consistent in direction etc. I have tried this option without sucess with the sample file.There are still open edges: The problem is the model quality, to much naked edges. Image 1 is from a polygon modelling app, image 2 is a NURBs cube with filleted edges being prepped for export as a polygon mesh (obj in this case). ** Edit - I have just added two screenshots to help you understand a little better. Here are some third-party Pixel cases that might be better than the official. Once you are happy with the mesh, complete the export from Rhino, then use KeyShot to import and UV map the exported polygon model. Google’s new Pixel 6 and 6 Pro are great, but you’ll need a case to protect against their slippery glass backs.

Export your model from Rhino as an OBJ LWO FBX or whatever polygon format you prefer, you should get a dialogue box to adjust mesh density and quality and you should be able to see the mesh being generated. UV Mapping really needs to be applied to a polygon based mesh. Using your shape apply the wireframe material from the miscellaneous materials and then zoom into any fillets or blended surfaces and you will see the underlying tessellated surfaces have different mesh densities, those kind of surfaces are fine for procedural shaders but are no good for bitmapped textures which is why you can't get good results with UV Mapping and a complex NURBs model/solid. NURBs surfaces are mathematical equations resulting in shapes, that are 'glued' together to produce solids. Rhino does not produce a UV map as such as it is a NURBS modelling app. I see you mention Rhino as your modelling package.

Moi3d can't find naked edges