Fucked up a major feature in the app when I fixed one part of it. Now the customer is in total panic mode, even though I have fixed the issue and the new version is being rolled out to the users. Yay.
The root cause for this problem was that I removed one parameter from a message that is sent to the backend because that was no longer needed by that one part of the feature. Apparently it is indeed needed for the other part of the feature, hence, this major problem.
Support for SOAP over HTTP is deprecated, but it is still available over HTTPS.
Why should I use REST when there is SOAP available? ?
It has been cold for about a week but we haven’t gotten snow until now. The cold air also means that the sea has cooled a lot and the grass and tree branches form pretty nice ice art.
@matigo Yep. I had to debug the issue with a developer of the feature who noticed that the documentation was wrong. No wonder the app was not behaving correctly.
There was a pretty major issue in the app. Turned out that the name of a required parameter was wrong on our end. Then again, the documentation of the feature had that wrong too. ?♂
@matigo Well, in this case we were writing to each other, but you get my point. Also, we were discussing in English that is not the first language to either of us. However, I think I was able to express myself clearly enough. But what do I know, maybe I was everything else but clear. ?♂
Today is one of those days when I wonder does the other person I am communicating with understand a single word I say to them even though we are supposedly speaking the same language. Sigh…
@matigo Yeah. That could explain it if it would happen every time on their devices. But it’s inconsistent on their tests too. ?