You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in Release mode the SDK is not capable of upload any file. In Debug mode it works properly but not in Release. (See Edit Scheme > Run or Archive and run)
The method that results in failure:
- (CLDTransfer *)uploadItem:(CLDItem *)item
shouldOverwrite:(BOOL)overwrite
cellularAccess:(BOOL)cellularAccess
priority:(CLDTransferPriority)priority
resultBlock:(void (^)(CLDItem *))resultBlock
failureBlock:(void (^)(NSError *))failureBlock
By inspecting the request I've found that when in Release mode, the call to the API has a Content Length of 0. While in Debug mode, it's Content Length is not 0.
The error output of the SDK:
The operation couldn’t be completed. (pt.sapo.osx.meocloudsdk.ErrorDomain error 115.)
115 -> CLDErrorCodeInvalidParameters, which matches the wrong request content length.
EDIT:
Further investigation of this issue (and thanks to @p4checo), resulted in the attribution of this issue to the usage of NSAssert throughout the codebase. Which when build in Release mode, triggers the stripping of those NSAssert's, taking with them the method called inside some.
The text was updated successfully, but these errors were encountered:
When running in Release mode the SDK is not capable of upload any file. In Debug mode it works properly but not in Release. (See Edit Scheme > Run or Archive and run)
By inspecting the request I've found that when in Release mode, the call to the API has a Content Length of 0. While in Debug mode, it's Content Length is not 0.
The error output of the SDK:
115 -> CLDErrorCodeInvalidParameters, which matches the wrong request content length.
EDIT:
Further investigation of this issue (and thanks to @p4checo), resulted in the attribution of this issue to the usage of NSAssert throughout the codebase. Which when build in Release mode, triggers the stripping of those NSAssert's, taking with them the method called inside some.
The text was updated successfully, but these errors were encountered: