Ipad- getting repeated characters with fill-in survey boxes

Hello all, Hope everyone has a great holiday break and new year!!

I was wondering if anyone has experienced an issue when filling out text input boxes via an Ipad or iphone?

On the Iphone any text box i type into repeats every character i type, for example, typing hello will come out "hheelllloo".

On the Ipad the same thing happens expect that the character only repeat at random, not with every one typed.

This is content running as HTML5 via an LMS. It is only text input fields that do this weird thing, they work fine on a pc.

I have built a brand new bit of content to test it, see attached files. Is this a bug in the exported content, in how it interpreters the ipad and iphone inputs?

Any help would be greatly appreciated as we are having to pull  content off our mobile support as it just is not usable in this state :(

Video attached shows me typing in the keyboard on an ipad, from top left of keyboard onwards. I am not typing two letters when they show twice. I will try to add the project files after logging this message.

Thanks all!

20 Replies
Ashley Terwilliger-Pollard

Hi Richard,

Thanks for sharing the movie and the .story file. I tested this on my iPad mini using iOS7 and didn't have any duplicated text. I uploaded it to my Articulate Online account, and you can access it here: http://aterwilliger.articulate-online.com/9369998180

Can you test that version and let me know if the behavior continues? Also what version and iOS are you using on the iPad? 

Richard Mundon

Hi Ashley,

Thanks so much for uploading the file so i can test it out on another hosting platform. The good news is that when testing via the link you sent, the issue does no occur.

Which leads the investigation towards the question: Why would hosting the same content on an LMS cause letters to be duplicated? very strange.

Also to answer your questions, this is on the latest ios (7.0.4) for Ipad. On our LMS i have also tried it on an Ipad 2, Ipad air and Iphone 5 (all on latest os). All the same result. :(

What behavior does the content respond too or send out when accessed via an LMS that could cause text to be duplicated? I am newish to the structure and behaviour of Storyline and SCORM and SCORM messages.

Thank you for your help so far, looking forward to hearing more, if you are able to assist.

Kind regards


Ashley Terwilliger-Pollard

Hi Richard, 

I'm glad that my original link worked for you, and I also loaded it to SCORM Cloud (which is a industry standard testing method for SCORM content) and you can see that version here. 

It behaves normally there for me as well, so you may want to share that with your LMS team so that they can help you determine what is happening on their end. You could also load your own course to SCORM Cloud (the basic set up is free).

Josephine Crimmins

I am getting the same 

Ccuurrrreenntt//ppaasstt meennttaal  hheeaalltth  iissssuueess^4^4AAbbuussee  (ppaasstt//pprreesseenntt))^4^4SSuubbssttaannccee  uussaaggee^4^4RReecceenntt  liiffee  ssttrreessssoorrss^4^4CCuurrrreenntt  prraaccttiiccaall//  eemmoottiioonnall  ssuuppppoorrtt 

Ashley Terwilliger-Pollard

Hi Josephine,

SCORM Cloud is accessible here, and you'll need to create a free account to load up your course content. You mentioned you're hosting on a website though - so if you're publishing for web instead of publishing for LMS, you could use one of the web servers below to test your content on the website outside of your CMS:

  • Tempshare: This is a free service provided by Articulate for testing Storyline content. Note: Uploaded files will be deleted after 10 days.
  • Amazon S3: Amazon S3 offers free hosting with generous usage limits. If you go over your limit, you'll be charged a graduated fee.
  • Dropbox: Place your published output in the Public folder in your Dropbox account to share it with others.
  • Google Drive: Change the story.html file to index.html, and set the sharing permissions to PublicHere's how.

Please feel free to keep us posted on how it behaves in one of those environments. 

Josephine Crimmins

Hi Ashley,

I know you don't want to recommend a good LMS. here is  my problem- we are using drupal- and because we must have records of what people are entering into the questions we cannot use the mobile player on ipad. Our clients also need to fill in an evaluation from. We are havng complaints of double letters in the essay type questions when using ipads and the resizing is not working on androids- I am trying to work out a solution to this. 

Should we have another option that says click her if you would like to do the education on the ipad. 

how do I get help with this advice. 

Ashley Terwilliger-Pollard

Hi Josephine,

I don't know enough about the different LMSs and what they offer to provide an educated recommendation, but there are a few community threads where users discuss different options and their benefits/drawbacks. Did you see the double-character entry when testing at SCORM Cloud? I know previously when we tested Richard's file it only occurred in his LMS. 

I have seen other users discuss publishing the course in two formats, one to play on a desktop/laptop or the iPad, so that may be a viable option for you to use. 

Dane Boyington

I just happened across this thread. Actually this is a known bug. It has to do with LMS's that display the content in an iFrame/lightbox on top of the LMS window instead of in a separate browser tab.

See this discussion here:  http://community.articulate.com/forums/t/40826.aspx?PageIndex=1

The good/bad news is that Storyline 2 *almost* fixed it. The double characters are gone, but now for me in a fill-in-the-blank interaction if you use the Submit button to submit the answer instead of just pressing the screen keyboard Enter key, then the last character of the answer is cut off before it is graded. (You won't see this on the screen, but the feedback will say it is wrong and the TextEntry variable will be one character short.)

Ashley Terwilliger-Pollard

Hi Dane,

I see based on the previous thread, and the QA report that was filed with our team about this that Ronnie reached out to you via email about the double character text entry, and it looks like that was solved with Storyline 2. I see that Ronnie and you were still communicating about the issue with the enter key - and I'll connect this thread to the existing report with our QA team so that when I have additional information to share I'll be able to include here.