*What*
With master version of [aerogear-app-metrics|https://github.com/aerogear/aerogear-app-metrics/commit/5d42dc445f5712561a9ab59e5144dc400873ee75], when the metrics data (app & device info) are sent from iOS app, they are successfully saved, but the error is thrown in the console
{code}
2018-03-07 16:41:28.755 [Debug] [MetricsNetworkPublisher.swift:18] publish > Sending metrics ["timestamp": 1520437288754, "clientId": 5F766958-56E8-44E5-A9CA-84BD7EBF3FFC, "data": ["device": ["platformVersion": "11.2", "platform": "ios", "device": "iPhone"], "app": ["appVersion": 1.0, "sdkVersion": "DEVELOPMENT", "appId": org.aerogear.AeroGearSdkExample]]]
2018-03-07 16:41:29.111 [Error] [MetricsNetworkPublisher.swift:21] publish > An error has occurred when sending app metrics: responseSerializationFailed(Alamofire.AFError.ResponseSerializationFailureReason.inputDataNilOrZeroLength)
{code}
I think this might have something to do with the newest changes on app-metrics, when recently only the statuscode is returned back to client app after data is saved
ping [~wtrocki] [~danielpassos]
Update: It is true that it's not our responsibility to handle the response from api server in SDKs (as discussed [here|AGIOS-668] and [here|https://github.com/aerogear/aerogear-android-sdk/pull/119#issuecomment-370604006]), but imo we should at least do the logging in a right way - response without message but with status 200 should not be logged as an error. |
|
