ondatastream not firing on iOS

You must Login before you can answer or comment on any questions.

Does anyone know if there are plans to fix the ondatastream event in iOS? In Android, it correctly reports bytes downloaded though I'd like to see a percentage value as works in posting a file with onsendstream. However, iOS ajax.ondatastream only fires once, at the end with a value of 1. So my users sit there looking at "Loading..." for 2 minutes on a larger file with no indication that anything is working.

I've seen numerous posts about this issue, some from literally two years ago! I too, would like to have progress of downloads without having to resort to kludgey workarounds or explicitly controlling the cardinal position of event handlers assigned to ajax object which none seem to work anyway.

My code is exactly like any number of posts asking about the problem in the past in terms of structure.

Any advise? Thanks!

— asked 8 months ago by Lee Jenkins
2 Comments

  • Does anyone know if there are plans to fix the ondatastream event in iOS?

    Um;

    1. Is there an open JIRA?
    2. If there isn't a JIRA open, have you thought about submitting one?
    3. You mentioned 'your code is the same as everyone elses', that seems like an excuse not to actually submit a complete and valid question.
    4. You left out a truckload of information that would be expected with a complete and valid question worth an experts time.

    --

    Missing from your question are a number of important pieces of information. I suggest you take a look at the Using Questions and Answers article, specifically the Q&A Question Checklist. The missing information is critical to reproducing problems in a test environment and often indicates other factors that cause the undesirable outcome you are experiencing.

    — commented 8 months ago by Stephen Feather

  • Really? And what "truckload of information" is missing? People have been posting about this bug for two years! I experienced the problem as described above, searched Q&A and saw post after post describing the same problem, exactly as I am experiencing.

    Just look at any one of post after post going back two years on the subject and you'll see quite enough code, but no indication of a fix.

    I was just curious if anyone knew if Appcelerator thought it was important enough to fix a long standing bug in a very core part of the toolset's functionality. I don't need code snippets showing me how to make it work, I already KNOW it doesn't work and won't work without yet another kludgey workaround.

    — commented 8 months ago by Lee Jenkins

Your Answer

Think you can help? Login to answer this question!