aha .. good to know .. though those reports are handed over in the background somehow .. :)

Quote from: jz831 on February 23, 2015, 04:52:52 PM

Quote from: xeroc ¯\_(ツ)_/¯ on February 23, 2015, 07:23:31 AM
crash reports are sent to the bitshares devs .. so please send them over .. (no need to be afraid of losing funds via report .. no private keys are sent)

"so please send them over" - just to be clear, is that via the [Send to Apple] procedure - will that suffice? or is creating / adding to a Github issue preferred?  Thanks for the info!

The "Send to Apple" is not helpful. I believe only the Windows client has a separate crash reporting service that gets sent to us. You can create a GitHub issue with any details of the crash.

Quote from: xeroc ¯\_(ツ)_/¯ on February 23, 2015, 07:23:31 AM
crash reports are sent to the bitshares devs .. so please send them over .. (no need to be afraid of losing funds via report .. no private keys are sent)

"so please send them over" - just to be clear, is that via the [Send to Apple] procedure - will that suffice? or is creating / adding to a Github issue preferred?  Thanks for the info!

yup / you can use https://github.com/BitShares/bitshares/issues if you're familiar with github!

crash reports are sent to the bitshares devs .. so please send them over .. (no need to be afraid of losing funds via report .. no private keys are sent)

Curious - what should I be doing when the application crashes - is there any way to help by offering my info?
Having worked on mobile apps for Android, the crash reports there are most helpful for development - I'm wondering if the [Send to Apple] option on the UI after BitShares crashes is useful or not, or should I be posting that info somewhere else, if it's worthwhile to do so?  (Obv. I'm running on OSX)