GETAsync & POSTAsync are invalidating the Client property of the TMARSClientResourceXXX component resulting in Access Violations on 2nd & subsequent calls

[stuartclennett]

GETAsync and POSTAsync leave the MARS Client property of the Resource Component (e.g. TMARSClientResourceJSON, TMARSClientResourceFormData, TMARSClientToken) in an undefined state.

Second and subsequent calls using the resource fail with access violation.

Open the MultipartFormData demo project.
Compile and run the server
Compile and run the client with debugging
Click "Select and Send" - select an image, the result is a valid JSon
Place breakpoint on FMXClient.DataModules.Main line 57 : HelloWorldRes1.PostAsync(nil, ...
Click "Select and Send" again.
At the breakpoint, inspect the HelloWorldRes1.Client property - note that it is invalid (either nil, inaccessible or contains empty property values - i.e. no engineURL).
Proceed to execute (F9) and note that the call will fail.

Setting the specificClient property does not workaround this.

[kitesoft]

hi
do you have a temporal workaround for this bug?

[andrea-magni]

hi
do you have a temporal workaround for this bug?

I've just pushed a first tentative fix for POSTAsync (so be aware GETAsync and the other methods are still affected by the issue).