Common Issues
Last updated
Last updated
In some parts of the application, you might encounter this screen:
This can occur for many reasons:
Terminal window is not large enough.
The display resolution of your device is smaller than the supported 1920x189 resolution.
Scaling and or other display issues.
Quick fixes:
always run Zaun in full screen.
reduce the scaling factor in your device settings.
use a device that has a minimum display resolution of 1920x1080.
If you see errors about missing files or de-serialization issues, here are steps you can take to resolve them:
Firstly pinpoint the file with the issue
Make sure the format is as expected by the program by re-extracting from your application version's zip file.
If not, replace the malformed file with your newly extracted file and copy your configuration values to it.
If the file is missing, or accidentally deleted, then simply extract a new one and place it in the appropriate directory.
If you find that your bundles simply don't want to land. here are some of the probable causes:
Spamming operations. The Bundle Guard account may sometimes lag behind if operations are done in a fast and successive manner, such as quickly funding then cleaning then funding etc..
Insufficient balance, Sometimes its simply that the bundle itself just fails regardless, such as the case of not having enough funds to pay tip or transaction fees.
Network Or RPC Issues: Sometimes the network/RPC can be the bottleneck and lead to bundles not confirming
TLS/Websocket issues, Web sockets are used internally by the application to confirm transaction landing on chain. if they are misconfigured not working, it will lead to bundle timeouts excluding the fact of the bundle actually landing or not,
