Unfortunately, the only solution we found is to create a new target for the watch application and migrate all the files and assets, as replacement for the automatically merged one. This seems to fix the issue on these specific devices.