This collision occurs when SAP and customer enhance the same development object and customer tries to release his changelist after importing SAP's changes. The following steps describe the scenario.
1. SAP creates a development object and transports it to the customer repository.
2. Based on customer specific requirements, a technical consultant enhances the original version of the development object. This is done in a side branch since SAP owns the development object.
3. SAP also enhances the original version of the development object and transports it to the customer repository.
4. When customer changes are released, Mobile Application Studio reports a collision between the version transported by SAP and customer's own enhanced version.