Feature Request: Cloud Diagnostics Obfuscation Support

After contacting support I was pointed to the forums to make a feature request.

Would it be possible to add support for code obfuscation to cloud diagnostics?

This would be the ability to automatically translate obfuscated code seen in reported exceptions and crashes back to readable method names with a translation file provided after building the project.

An example of this is with this asset https://assetstore.unity.com/packages/tools/utilities/obfuscator-48919
Code is obfuscated with random method names and a translation file is produced so that the randomised method names can be translated back their original names.

Thanks!

 

Could be highly useful to have something like this, although some common ground with obfuscation methods should be considered first.

 

Hi @matt_mp, @Novack, and @michal-gs! Thanks for your interest in this feature! I'd like to bring in @SidM1 to help go over what your main reasons would be for a feature like this. Is it mainly for additional security of your code?

 

Thanks for responding @ryanc-unity. The main reason is security and IP protection. I'm working on a codebase where builds get obfuscated and a dictionary map is provided as part of the build. Being able to provide such a dictionary to deobfuscate stacktraces in cloud diagnostics would really help. At the very least being able to have an integration with an external webhook would be enough, but currently only the first line of the stacktrace is provided in the request. Right now we have to do this manually.

 

They are local builds @SidM1.

 

@ryanc-unity and @SidM1 thanks a ton for the interest. I'll summarize our case.

We use code obfuscation on our builds to help us deal with cheats and unconsented copies ("hacked mods"). We use IL2CPP but we found the hard way, that we need obfuscation.

We use Unity Cloud Build for all our builds (our project deploys WebGL and Android), and we have production builds with obfuscation enabled, and QA builds with obfuscation disabled for easier issue tracking.

When it comes to production releases, the obfuscation is a pita in regards to bug tracking: logs and stacktraces need to be "translated" using a table of the renamed class/method/etc. As @michal-gs has pointed out, being able to provide a translation table to Diagnostics to do the change for us, would be a game changer. I also agree that having a webhook would be acceptable, though the ideal remains on Cloud Diagnostic making it transparent for us.

Finally I'd like to mention something that may help, Beebyte's Obfuscator is the goto solution in Unity for this matter.

Thanks again.

 

I'm in a very similar situation to @Novack. The only difference is that we run builds locally at the moment. Also agree with the other points raised.

 

any news on this? We are on the same situation than @Novack.
I guess there's no intention on adding this feature ?
What did you guys ended up doing If may I ask?
Thanks!

 

Also interested in this feature, this would be an amazing upgrade

 

Also interested, any news?