Hi,

Those data are only meant to be decoded by us, not by our users. They are not only base64 encoded but also strongly encrypted so that sensitive data will not be revealed even if the plain data are posted publicly. More over, even if we do not encrypt it, they are binary crash related debug data that our user will have little use. We use those to match up with our debug symbols in order to find more information about the crash.

You can send the crash data directly to us through our "Contact Us" page. However make sure that you are on the latest build first. Beside the issue might have already been fixed in the latest build, because the debug symbol files are enormous, we only keep them for recent builds, which means that there isn't much we can do with the crash data based on older builds.

Once you have collected the data on the latest build, you can either send them to us using our Contact Us page or using the new Debug Tools application (which only exists in the latest build) to send the crash data file to us. Make sure you send the CrashDataEventArgs.Data exactly as is (for example, using File.WriteAllBytes) --- do not try to encode/decode it. They are binary format, not text format. So any changes will make it unusable.

Thanks!