It's going to do that. I honestly do not know the real answer, but this is my take. I have seen this behavior before.

Replication is not "smart" enough to determine that Table A needs to be in place before Table B because of the parent-child constraint.

It generates the snapshot objects in no order, so it may actually try to add the child table before the parent table exists and is populated.

if this was transactional replication, I would strongly recommend removing the foreign keys as well as defaults and check constraints.

Since it's snapshot replication, simply create all of the keys in a post-snapshot script.