SSDT Schema Compare keeps finding differences for users?

Question

The title says it all but for further details. When i use the schema compare tool in VS2015 for my SSDT Project and my database on a server. The compare results always come back with the Users as being different. I check the differences it speaks about but there is not a single difference between the environments.

I even went as far as updating my project from the compare results to try and correct these "differences". I then ran another compare and the same users came back with differences again... WHAT! haha.

Anyone have a clue what would cause this sync issue or am i doing something wrong? The users were added manually to the database on the server rather then thru SSDT deployment so maybe that is a reason?

EDIT:

Answer 1

Please hit the arrow on the left of the user differences found. You will see a properties folder and the missing login which is the real difference. If you go Schema Compare Options -> Object Types (tab) -> Non-Application-scoped -> Logins to add Login object type to your comparison then your issue will be resolved.

Logins objects

Answer 2

When I drill into the schema compare under Change > User > Properties > Spanner icon, I can see this difference:

Source (SQL Azure)    Target (Project)
=============         ===================
UserType=2            UserType=0

What does this mean? I googled to no avail.

Updating doesn't fix it. Deleting the user script from the project and Updating doesn't either.

I can't find UserType in the source code so this must be generated internally by the compare.