From a Discord report:

A couple more issues with identities:

• Server and client use different endianness when converting identities to strings, which makes them more difficult to compare (ex. in logs)
• I feel like AuthToken.GetTokenKey() shouldn't be exposed and users should instead be encouraged to use AuthToken.Token. The latter has the stored token, while the former has a key which is used internally to store token in PlayerPrefs. Exposing both makes API confusing
• Related to the last point in my previous message, DbConnectionBuilder.WithCredentials doesn't even USE identity, so having it as an argument is extremely misleading (and made me lose half an hour on it)

Unable to reproduce the issue as described, additional clarification required.

Specifically:

• Different address printing order between client and server - How can this be observed/validated?
• Server and client use different endianness when converting identities to strings, which makes them more difficult to compare (ex. in logs) - How can this be observed/validated?
• I feel like AuthToken.GetTokenKey() shouldn't be exposed and users should instead be encouraged to use AuthToken.Token. - If we make AuthToken.GetTokenKey() private, that should satisfy this, and would simply require us checking if AuthToken.Token was present in PlayerPref.
• DbConnectionBuilder.WithCredentials doesn't even USE identity - As ".WithCredentials" is already deprecated, this is likely already resolved.

Issue is being placed as blocked until further clarification can be provided.

 Different address printing order between client and server

I can't repro it on latest release either, so it was probably fixed at some point.

The inconsistency happened when printing identities in C# client vs rust module. If you had two print statements, they would have different outputs. Ex.

• In Rust, spacetimedb::log::info!("{}", identity); would log abcd
• In C#, UnityEngine.Debug.Log(identity) would log dcba

Created #237 to move AuthToken.GetTokenKey() to private. AuthToken.Token can be used to get token value.

Checked most recent builds for behavior:
In Rust, spacetimedb::log::info!("{}", identity); produces abcd
In Unity C# , UnityEngine.Debug.Log(identity) produces abcd