Bug Playername managment BETA - Deserialization failed on Android.

Hello,
on my Android device I get the following exception most of the time when trying to receive the playername with "await AuthenticationService.Instance.GetPlayerNameAsync()":

Deserialization of type 'Unity.Services.Authentication.Generated.Model.Player' failed.

I also get an exception when trying to change the name. When testing in editor this never happened, it all worked fine. I have no Idea what is causing this, any help is appreciated.

Error when trying to change the name:
{"code":55,"detail":"request failed validation","details":[{"errorType":"OpenAPI spec validation","message":"request body has an error: doesn't match the schema: Error at \"/name\": property \"name\" is missing"}],"status":400,"title":"Bad Request"}

Get name full log:

Code (CSharp):

1. <GetOrCreateServicePlayerName>d__4:MoveNext()
2. System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
3. System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
4. System.Runtime.CompilerServices.MoveNextRunner:Run()
5. System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
6. System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
7. System.Threading.Tasks.Task:FinishContinuations()
8. System.Threading.Tasks.Task:TrySetException(Object)
9. System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1:SetException(Exception)
10. Unity.Services.Authentication.<GetPlayerNameAsync>d__117:MoveNext()
11. System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
12. System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
13. System.Runtime.CompilerServices.MoveNextRunner:Run()
14. System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
15. System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
16. System.Threading.Tasks.Task:FinishContinuations()
17. System.Threading.Tasks.Task:TrySetException(Object)
18. System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1:SetException(Exception)
19. Unity.Services.Authentication.Generated.Api.<GetNameAsync>d__9:MoveNext()
20. System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
21. System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
22. System.Runtime.CompilerServices.MoveNextRunner:Run()
23. System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
24. System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
25. System.Threading.Tasks.Task:FinishContinuations()
26. System.Threading.Tasks.Task:TrySetException(Object)
27. System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1:SetException(Exception)
28. Unity.Services.Authentication.<SendAsync>d__19`1:MoveNext()
29. System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
30. System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
31. System.Runtime.CompilerServices.MoveNextRunner:Run()
32. System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
33. System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
34. System.Threading.Tasks.Task:FinishContinuations()
35. System.Threading.Tasks.Task:TrySetException(Object)
36. System.Threading.Tasks.TaskCompletionSource`1:TrySetException(Exception)
37. System.Threading.Tasks.TaskCompletionSource`1:SetException(Exception)
38. UnityEngine.AsyncOperation:InvokeCompletionEvent()

 

I have the same issue, works perfectly in the editor but not on Android... I'm using
[2.5.0-pre.3]

 

Good to know I am not the only one.

 

Hello,
thank you for the answer and providing a local fix.

 

Is there a fix that could be done remotely if our app is already in production?

Also, does the LinkXML annotation fix apply to iOS as well @erickb_unity?

Thanks for the heads up!

 

@erickb_unity I added the preserve line to my link.xml, but still end up with the 400s.

For some reason, I don't get this issue when I build to my device locally, but get the 400s in production.
Any help would be much appreciated!

 

@erickb_unity
Yep, seeing the exact same 400s errors as op on both get / update names -- our game is only iOS.
I was hoping there was a way to determine if the stripping patch actually was applied to our iOS build.

My link.xml is sitting under the Assets folder as so:

Code (CSharp):

1.  
2. <linker>
3.     <assembly fullname="Unity.ResourceManager, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null" preserve="all">
4.     <type fullname="UnityEngine.ResourceManagement.ResourceProviders.LegacyResourcesProvider" preserve="all" />
5.     <type fullname="UnityEngine.ResourceManagement.ResourceProviders.AssetBundleProvider" preserve="all" />
6.     <type fullname="UnityEngine.ResourceManagement.ResourceProviders.BundledAssetProvider" preserve="all" />
7.     <type fullname="UnityEngine.ResourceManagement.ResourceProviders.InstanceProvider" preserve="all" />
8.     <type fullname="UnityEngine.ResourceManagement.ResourceManager" preserve="all" />
9.     <type fullname="UnityEngine.ResourceManagement.AsyncOperations" preserve="all" />
10.     </assembly>
11.     <assembly fullname="Unity.Addressables, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null" preserve="all">
12.     <type fullname="UnityEngine.AddressableAssets.Addressables" preserve="all" />
13.     <!-- TODO REMOVE THIS WHEN AUTH FIX IS IN -->
14.     <assembly fullname="Unity.Services.Authentication" preserve="all" />
15.     </assembly>
16. </linker>
17.  

 

My guess would be that the problem is that you have multiple assembly tags in your file or that you need to move line 14. one line down, because you declared an assembly tag in another assembly tag.

 

Ah ‍♂️ thank you for the catch -- glad it was something trivial!
Haven't checked if a warning was thrown, but if serious, then maybe should be a larger issue,

Our production build works fine though

 

Unity has released version 2.5.0 of the authentication package, which should contain the fix for this issue: https://docs.unity3d.com/Packages/c...2.5/changelog/CHANGELOG.html#250---2023-05-09