New Approval Func<ConnectionApprovalRequest, ConnectionApprovalResponse> restricts approval to main thread

[JayPeet]

Feedback
The new changes to the NetworkManager.ConnectionApprovalCallback seems to restrict the usage of Approval to anything main thread related (since its waiting in the function to return the ConnectionApprovalResponse). The documentation gives an example of doing a Steam API ticket check on client connection, which would be a web request that could take seconds to complete.
In my current code, I do a web request to the authentication API to check if the client is authenticated, which now requires me to lock the main thread, whereas before I would just call the callback later once my web request had finished.

Suggested Changes
Not sure what to suggest as this change was intentionally made by the NGO team. However it seems like the Approval callback is now useless for doing any actual authentication / approval since it seems to block the main thread

[ashwinimurt]

Thanks for reporting. We are working on some refactor on Connection Approval logic and will take this into consideration.
After the refactor, it will be possible to use any thread to perform approval.

[ashwinimurt]

Will be addressed by MTT-2567

[jeffreyrainy]

Hi JayPeet,

Thanks, this is the kind of great feedback we need. We were a bit hasty in the changes. #2002 would address the concerns you raised, I believe.

Please let me know if you think otherwise.

Thanks!

[JayPeet]

Much better, thank you for taking the time to make these changes!