appcenter-sdk-dotnet
appcenter-sdk-dotnet copied to clipboard
microsoft
Make Crashes.GetErrorAttachments async
Is it possible to make Crashes.GetErrorAttachments async? I got a scenario where i need to retrieve some user data from my app database async.
Good idea but I cannot answer about any ETA for this.
We need to discuss it for iOS as it needs to be done on underlying SDK side. For Android, that should not be an issue as this is called from a background thread already, it's safe to block there.
A workaround in iOS is to use the confirmation feature. Return true in Crashes.ShouldAwaitUserConfirmation, then call Crashes.NotifyUserConfirmation(UserConfirmation.Send) from a background thread that you spawn from that callback for example, this will resume the workflow and call get error attachments from same thread as Crashes.NotifyUserConfirmation(UserConfirmation.Send).
Note that the workarounds mentioned is not to use async but to block in a thread that is guaranteed not to be the UI one, we keep the issue opened for providing a real async mechanism.
Hi @imuller , I would like to refresh the status of this feature request. Could you please confirm that you are still interested in this feature?
Since there were no activity for a while I'm closing this issue. Please leave a message if you are still interested in it and we will reopen the issue.
I'm still interested in having the call async.
Like the initial commenter I have some interaction with the database layer in order for it to included as an attachment.
For the moment I'm using a .Wait on the await-able method call but as this is typically frown upon as it will tie up an additional thread it would be preferable to support async methods.
Can't quite believe we are in 2023 and this is no further forward. Oof, that's 6 years.
This is a useful feature for most callback methods to be fair. I don't see adding it here as an exception. Easpecially when you might need to read/write asyncronously from/to file storage assuming you want to create an all up logging/reporting service.
Can't quite believe we are in 2023 and this is no further forward. Oof, that's 6 years.
It took about that long for them to support all platforms that Xamarin.Insights supported despite promising "feature parity on launch" when Insights was canned in favour for this product. Don't lose hope just yet.
As we do not have plans to add support for this feature in the next year, I'm closing the issue. However, contributions are still welcome.