The following section provides answers to Frequently Asked Questions (FAQs) related to Screens as a Cloud Service project.
AEM as a Cloud Service changes the long cache keys with every deployment. AEM Screens generates the offline caches when the content is modified, rather than when the Cloud Manager runs the deployment. These long cache keys in the manifests are invalid, so the player fails to download these clientlibs.
longCacheKey="none" in your
clientlib folder removes the long cache keys altogether for these clientlibs.
Offline caches are generated using bulk-offline-update-screens-service service user. Certain paths, not accessible by
bulk-offline-update-screens-service, lead to missing content in offline manifests.
In your code, that is,
ui.config or ui.apps, create an OSGi configuration in configuration folder, with the following content, and title the file name as
scripts=[ " set principal ACL for bulk-offline-update-screens-service allow jcr:read on /content/mysite allow jcr:read on /apps/my-resources end "]
It is recommended to use images in the format
.jpeg in an AEM Screens as a Cloud Service channel, for the best digital signage experience.
The images in the format
*.tif (Tag Image File format) are not supported in AEM Screens as a Cloud Service. In case, if a channel has this format of image, then, on the player side, the image will not be rendered.