We are encountering weird issues from time to time when mobile application tries to access local entity with same name but from another module. We thought that it has been related to recent platform upgrade but after fixing similar issue it happened again without any obvious reason or code change from our side. 

Imagine we have application A and two modules M1 and M2. Both Modules has local entity called L. Application has references to both modules M1 and M2 but only references and uses L from M2. On runtime we have an error when specific attribute from L (M2) is not found. Creating a new L1 on M2 and replace all usages of L in M2 and refreshing references solves the issue. However it seems like a bug in ServiceStudio that incorrectly maps local entities. 

Thank you