@Kévin Dietrich (kevindietrich) this was introduced on rB753edafc . The problem seems to be at read time only, not on writing.

i did more tests on a 3dsmax, importing from file import does not read the uvs, but importing object by object creating the primitive (alembic can be created as a primitive like a cube, click alembic on prim select the path the object click on the scene) it does read the uvs, also created rotated 90º but that its a max thing ^^
So it seem that yep the uvs are there, didn't try to export and import alembic on max to max, to check if its a soft thing or an alembic thing

With 2.79RC1 it works just fine on my machine (Ubuntu Linux). In step 7 you may need to undo twice to get the modifier back, though, but after step 3 the UVs are loaded and stay loaded.

mmmhh, doesn't work for me, but probably I'm just doing it wrong. But if that's the final workflow for the Blender 2.7x branch I'd better go and try again...

b1a036861ddd changed the way we read UVs, so this may be fixed too. Can you re-check?

I just tried with the latest buildbot version (c66983c). It's not working for me :/

Works just fine here. These are the UVs after exporting the mesh and importing into a new Blender file. I'm simply using Space → Export Alembic and Space → Import Alembic, nothing fancy.

Which steps are you using that don't work? How do you define "not working"?

I tried my testfiles that I mentioned earlier in this thread. You can get them from here: https://developer.blender.org/T51820
They come from Houdini and load fine with UVs into other applications (e. g. gaffer)

@Philipp Oeser (lichtwerk) if the problem in this ticket is solved for the files used to demonstrate the problem, let's close this report. Loading UVs for files with changing topology is indeed something else; could you write a report for that and assign it to me?