Comment on page
Frequently asked questions about publishing stories
If your story has been published but users can't see it on the app, check the following:
If you have published a story but are not sure which group(s) it was shared with...
- 1.Open "Analytics and Trends"
- 2.From "Stories", select a story
- 3.On the "Real-time" page, select the filter icon (top menu) to see a list of all the groups that this story has been published to
If you see a message telling you that your device is not compatible, this is because your device does not meet the minimum system requirements.
Operating Systems (Mobile & Tablet) Apple and Android only Browser Requirement (for Desktop/Web) Evergreen browsers (browsers that always receive the latest updates). See here: http://outdatedbrowser.com/en Minimum Device OS: Android Nougat 7.0+, Apple iOS 11 (note that the platform does not support operating systems that have been deprecated by either Android or Apple, and therefore minimum device OS requirements will change accordingly) Minimum Device Memory 512MB Ram Minimum Device Storage 2GB Minimum Available Storage 200MB Access to Connection Device(s) must connect to download stories and sync data/results
In doing so, you indemnify the platform licensor, licensee, sub-licensees, and appointed providers, as well as their employees, directors, and agents against any claim (including any legal costs incurred) that may arise as a result of any infringement of a third party’s intellectual property in the creation and/or development of content, any negligence on your part, either contractually or delictually and whether by act or omission, any violation by you of any laws or regulations.
Every time you update content in the story, you will need to re-publish the story.
If you have multiple apps and want to publish a story to a different app, you will also need to re-publish it and choose the new deployment target (app).
Your users will need to update the story on their app every time you make a change.
When you make changes to a story and then publish an update, the results for users who have already completed the previous story version will not change until they complete the new version. Their previous logs will be archived after the new attempt has been completed.
If you are making drastic changes to a story and want all users to redo it, we recommend archiving the current story and creating a new one.
The deployment target is the app to which you want to publish your story.
Some accounts have access to multiple platform apps and are able to publish to multiple apps/deployment targets.
A story can only be published to one app at a time.
The story listing is the preview that users see before they download a story on the app. It is an essential part of publishing a story.
The story size limit is set at 100MB.
The optimal limit takes into consideration: reducing story load times, limited user bandwidth, and device storage space.
If you have a large story size, e.g. due to many videos in your story, you should consider splitting the story into parts.
If your story is not publishing, check the following:
Yellow. Not published Green. Published Eye. Privately published to groups
Published status iconography
If you are struggling to simulate your story this could be due to the story size. Large stories may take longer to load.
Also, check your connection and try again.
It is recommended to create fewer than 50 pages per chapter and to keep stories below 100MB in size.
Only the simulator logs are cleared. Beta is considered a valid log, and updates when you continue or repeat a live story. As a tester or admin, you will therefore still see your Beta results when you publish to live.