Bug: JSON deserialization error occurs on ARM64 builds (aka port to .NET 9)

[ilGianfri]

I'm getting this error on launch on the latest store version, the app does not display anything. Seems something is not getting parsed correctly in the json.

Home:

Notifications:

I've tried to launch the app in debug from the master branch and everything works, no errors and TL loads correctly.

[gus33000]

Same here; reproduces fine and I am unable to use the app

The JSON value could not be converted to System.String. Path: $.view.creator.description I LineNumber: O I BytePositionlnLine: 790.
at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack&, Utf8JsonReader&, Exception) + 0x4c
at System.Text.Json.Serialization.JsonConverteÖ1.ReadCore(Utf8JsonReader&, T&, JsonSerializerOptions, ReadStack&) + 0x258
at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpar€1, JsonTypelnf&1, Nullabl@l) + Oxdc
at JsonTypelnfo'1) + Ox15c
at System.Text.Json.JsonSerializer.Deserialize[TValue](String, JsonTypelnfo'1) + 0x60
at FishyFlip.Tools.HttpClientExtensions.<Get>d_ö1.MoveNext() +
- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchlnfo.Throw() + 0x24
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + Oxac
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x58
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x24
at FishyFlip.Tools.ATProtocolExtensions.<Get>d_ff1.MoveNext() + Ox190
End of stack trace from previous location where exception was thrown
at System.Runtime.ExceptionServices.ExceptionDispatchlnfo.Throw() + 0x24
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + Oxac
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x58
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x24
at DarkSky.Core.ViewModels.HomeFeedViewModel.<Setup>d_4.MoveNext() + 0x40c

---

Above stack trace was copy pasted using OCR technology; mistakes can exist as a result; consider enabling copy pasting stack traces to improve such experience

[SirKubiac]

Same error on a Surface Pro 11 with Snapdragon CPU. No problems on my Notebook with Intel x64 CPU.

[FireCubeStudios]

@gus33000 @ilGianfri are your devices arm64?

[ilGianfri]

@gus33000 @ilGianfri are your devices arm64?

Yes, it's a Galaxy Book4 Edge arm64

[FireCubeStudios]

So it seems that this could be an issue with .NET Native on arm64 not working with the ATProto FishyFlip library that is being used. Another uwp app called Unisky also seems to have the same issue.

To temporarily fix this in the short term I will only be deploying x64 and x86 builds to the store and hopefully it will work with emulation even if this is not ideal.

I think this issue can be fixed by upgrading the project to UWP .NET 9 NativeAOT. Just to be sure however I will create a test app to see if the library works on UWP .NET 9. Since I don't have an arm64 device myself it would be up to someone else with an arm64 device to test if the UWP .NET 9 test app works. If it does then I will immediately start porting DarkSky to UWP .NET 9. If it does not work then we will see.

[SirKubiac]

I can test this version, if you want. Just let me know.

[FireCubeStudios]

More updates from information in Discord:

When compiling with debug arm64 the app works normally.

Some things like profile page work even in store release arm64 while other things don't 🤔https://discord.com/channels/714581497222398064/753345992543305808/1316388324088217681
https://discord.com/channels/714581497222398064/753345992543305808/1316388685146755164

[FireCubeStudios]

So 0.3.8 is out in the store. Is it possible to update to that and see if it works?

[SirKubiac]

It works. No error, no crash so far. 👌

[FireCubeStudios]

Nice, in the meanwhile we got devs that are smarter than me working on trying to figure out what went wrong with the arm64 build.

I will change the name of this issue to "UWP .NET 9 NativeAOT port" as that is the long term plan for DarkSky and it would prevent future .NET Native issues whether on arm64 or not

[Lamparter]

Let's create a new issue for tracking the UWP .NET 9 port