Does ParseUser.CurrentUser block? about parse-sdk-dotnet

[hallucinogen]

Hi @andymads, thanks for your report.

ParseUser.CurrentUser will block on some platforms (like Unity iOS), but it will work on some others (like WinRT). We're currently looking for a good fix for this.

Currently, there's no fix for this. The fastest and probably something that we want to do in the future is to publicize ParseUser.GetCurrentUserAsync()

What do you think @grantland, @nlutsenko, @richardjrossiii, @wangmengyan95

[andymads]

I'm targeting Unity iOS so this is interesting to me.

I'm using ParseUser.Current as a flag in some coroutines so it will be called at least once per frame - perhaps I need to rethink this.

And... I've just noticed in the profiler that it's generating 5Kb of Garbage Collector allocations every frame! (at least in the editor - cannot see it in profiler when running on device)

[andymads]

Ok, on device I think it's generating 700 bytes of garbage every single frame.

[rihadavid]

@andymads see #32 for workaround

[montymxb]

Closing in favor of #32