Forum Discussion
Android tablet won't play back triggers and text entries correctly.
Hi everyone,
I am creating a storyline course with 8 modules. It requires a large amount of text entry values, with triggers. I've been able to get it to work on a few devices. Lenovo Windows 10 pro, iPhone 13 pro, and an older iPad. While testing to see if it will work on a older Android tablet, a few of my data values and triggers are not working as they should. I am just calling it misfiring and misreading. I have buttons that will stall, text entries that won't jump to the next layer after the text entry is the correct value, and etc. The odd thing is they work fine on all the other devices I tested on. I guess the question(s) I need help with are: What devices won't support exported scorm1.2 files, specifically with text entry fields? What are the system requirements for devices to play back correctly?
I found the reason for these misfires. Text entry fields in my course can't be clicked out of on an android tablet. This has been messing up my triggers. Does anyone know a work around this?
To work around the issue of text entry fields not being clickable on Android tablets, consider implementing a "Next" or "Submit" button alongside the text entry field. This way, users can input their text and then click the button to trigger the action, allowing the course to proceed as intended.
Thank you Wali, I may have to go this route with a "Submit" button workaround.
which Android version?
what happend if you create a new .story file and add some text entry fields with your trigger?
Which Android version you are talking about.
Thank you Jürgen. Not sure if I am allowed to say which tablet it is, because it's a project for a company that uses their own custom tablets. I will try testing a new file though for sure. I'll be curious to see what happens.
Unfortunately this "Submit," button won't work, because it's almost counting the cursor as a character in the text entry field. So even if they were to click the submit button it's leaving their cursor inside the text entry field.
Hi Michael,
Thanks for reaching out! I understand you are having trigger issues with an older Android tablet. Articulate supports the latest version of Google Chrome with Android OS 6 or later. Here's an article with more information on that.
Can you confirm the version number of the Android OS you are using? You could find that information in your Settings app.
Looking forward to your response!
I thought it was an older tablet... maybe not. It's a zebra tablet. It has windows 10 on it. Version 1909. We're using chrome, not sure if it's the latest one. Can I send you my file confidentially for your team to look at?
Windows 10 19.09 is VERY old and without Microsoft support - the support ended May 10, 2022
https://learn.microsoft.com/en-us/lifecycle/announcements/windows-10-1909-enterprise-education-eos
which browser are installed on the tablets?
if they are not significantly newer, you should NEVER go on the internet with these devices - it is far too dangerous
on these zebra tablets there seems to be a special version of windows
i don't think storyline was tested on such special devices
Hi Jürgen. It does indeed say enterprise on it. I am going to try updating it, and see where that get's us. I am also going to try using a sister tablet and see if it mirrors the bug. In the meantime I will let my team know that this current OS is a security risk. Hopefully this current playback bug is just an update issue. The perplexing part is, these tablets worked with a previous course, with similar text entries and didn't have the same issues I am having. Similar triggers as well.
I just tried testing it on the sister tablet, and the same bug occurred. There is one difference with this tablet, it has one of the latest updates. 22H2. I am starting to think it may be a corrupt file? BUT why would it work on 3 other devices? I will do a test with similar text entries, if it's this case, it's a lot of work to fix.
>The perplexing part is, these tablets worked with a previous course,
then it will probably be the specific course problem
first you need to isolate the problem - for this it would be useful if you generate a .story file that is created from the problem course
take the course, delete almost all slides, change the images if necessary, replace the text with lorem ipsum text if necessary
if the error still occurs, you can start looking for the real problem - perhaps a fix can be found
