Crashed in OnStart with ArgumentNullException: Value cannot be null.

Created at 07 Jan 2025, 20:19
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
DU

dudavianna

Joined 07.08.2023

Crashed in OnStart with ArgumentNullException: Value cannot be null.
07 Jan 2025, 20:19


Hello everyone,

In the past few days, I've noticed a problem that has arisen, and I'm seeking help to resolve it.

I have a cBot that has been working for several months without any issues. When I run the cBot locally, it works perfectly without errors, even in Visual Studio debugging.

However, when I run the same cBot in the cloud, I receive the following error message:

`Crashed in OnStart with ArgumentNullException: Value cannot be null. (Parameter 'input')`

In addition to this, other errors have also started to appear in the cloud, errors that did not occur before.

I would like to know if there have been any changes in the environment that might be causing these issues. Does anyone have any tips or suggestions on how to resolve this?

Thank you in advance for your help!


@dudavianna
Replies

firemyst
08 Jan 2025, 00:16 ( Updated at: 08 Jan 2025, 08:29 )

There are a lot of limitations bots have when running in the cloud versus locally. For instance, you can't open network connections, send emails, read files, draw on charts, etc.

You haven't posted any code that's causing the issues, so nobody can really say for sure what's happening in your scenario unless someone from Spotware actually confirms there's a cloud issue.


@firemyst

dudavianna
08 Jan 2025, 15:19

RE: Crashed in OnStart with ArgumentNullException: Value cannot be null.

firemyst said: 

There are a lot of limitations bots have when running in the cloud versus locally. For instance, you can't open network connections, send emails, read files, draw on charts, etc.

You haven't posted any code that's causing the issues, so nobody can really say for sure what's happening in your scenario unless someone from Spotware actually confirms there's a cloud issue.

Thanks for your help.

I'm reviewing all the code, I think it might be something related to displaying a control panel. I just find it strange that it used to work and then suddenly stopped working. That's why I think there was some change in the cloud environment.

Another thing I noticed are some alerts about changes in the ModifyPositions() method (new version with ProtectionType parameter), it seems that new overloads were created and new parameters. That's why I think there might have been some change.

Thanks again and I think the problem might be the control panel that shouldn't exist in the version that runs in the cloud, only in the local version.


@dudavianna