# My file didn't come through

{% hint style="warning" %}
Big protections like constants may cause a max stack error which will result in your file not being sent back obfuscated.
{% endhint %}

If you can't find your file after obfuscation it is likely that something has gone wrong on the server side whilst obfuscating. A common issue is a dependency issue. Our obfuscation engine requires your .dll files and other dependencies to run. If your dependencies are embedded, the obfuscation engine won't work as they can't be resolved. Another issue could be an overflow issue. If you are using all protections on a heavy file (1mb+) then this could be the reason why your file hasn't come through.

To fix:

1. Remove any sort of embedded dependency from your project and have it external.
2. Contact us so we can store your dependencies in the cloud (we know this is a hassle to do, but we are working on fixing this so they can be sent automatically)
3. Try to reduce file size where possible, getting rid of embedded dependencies and having them external will reduce file size by a lot in most cases.
4. Reduce the amount of protections you use and pay attention to any pop up warnings for certain protections (such as call to calli conversion) as they may be the reason your file isn't obfuscating properly.

{% hint style="success" %}
We plan on adding a dependency feature to automatically send them to the cloud.
{% endhint %}
