Same problem here.
I think it is primo 2.4 causing this, not the maps.
I am going to install primo 2.0 on a second device and test the maps.