There's frequently the situation that we start polling before the upload rely with the captcha id is received:
2012-01-26 15:02:38.562 Graf[24140:707] call: upload
2012-01-26 15:02:38.566 Graf[24140:707] request byte count: 54451
2012-01-26 15:02:38.571 Graf[24140:1903] elapsed: 0.0
2012-01-26 15:02:38.573 Graf[24140:1903] result: (null)
2012-01-26 15:02:38.575 Graf[24140:1903] polling for image id 7cec961c4b7ab2af4dd090f923c2eead ...
2012-01-26 15:02:38.577 Graf[24140:1903] polling for captchaObject: {
}
2012-01-26 15:02:38.581 Graf[24140:1903] captchaId: (null)
2012-01-26 15:02:38.610 Graf[24140:4b03] wrote data with tag 3
There should be a "didUploadImage:" callback from which the controller can initiate the polling rather than scheduling it directly after the upload call.
There's frequently the situation that we start polling before the upload rely with the captcha id is received:
2012-01-26 15:02:38.562 Graf[24140:707] call: upload 2012-01-26 15:02:38.566 Graf[24140:707] request byte count: 54451 2012-01-26 15:02:38.571 Graf[24140:1903] elapsed: 0.0 2012-01-26 15:02:38.573 Graf[24140:1903] result: (null) 2012-01-26 15:02:38.575 Graf[24140:1903] polling for image id 7cec961c4b7ab2af4dd090f923c2eead ... 2012-01-26 15:02:38.577 Graf[24140:1903] polling for captchaObject: { } 2012-01-26 15:02:38.581 Graf[24140:1903] captchaId: (null) 2012-01-26 15:02:38.610 Graf[24140:4b03] wrote data with tag 3
There should be a "didUploadImage:" callback from which the controller can initiate the polling rather than scheduling it directly after the upload call.