Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SerializationException: Invalid JSON string #12

Open
EthanSK opened this issue Aug 9, 2021 · 4 comments
Open

SerializationException: Invalid JSON string #12

EthanSK opened this issue Aug 9, 2021 · 4 comments

Comments

@EthanSK
Copy link

EthanSK commented Aug 9, 2021

The response seems to be fine, and in wireshark it looks fine, but when being parsed in the Unity SDK, it throws SerializationException: Invalid JSON string. If I print the string it's trying to parse, it just gives a question mark character.

This issue does not happen when using the live Azure Function, only the local one with executefunction.cs

@MGudgin
Copy link
Contributor

MGudgin commented Aug 13, 2021

@EthanSK does this happen for all your Azure Functions, a subset or just one? Can you debug the local ExecuteFunction itself and see if the response looks right or wrong while inside that implementation before being returned to Unity?

@EthanSK
Copy link
Author

EthanSK commented Aug 13, 2021

It happens for all of them. The response looks fine in wireshark.

@MGudgin
Copy link
Contributor

MGudgin commented Aug 14, 2021

Does it look fine in wireshark both between the Azure Function and ExecuteFunction and between ExecuteFunction and Unity?

JayZuo added a commit to JayZuo/pf-af-devfuncs that referenced this issue Dec 16, 2021
MGudgin pushed a commit that referenced this issue Jan 4, 2022
@MGudgin
Copy link
Contributor

MGudgin commented Jan 4, 2022

PR #13 from @JayZuo has been merged. @EthanSK, please can you try the updated code and see if it addresses your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants