Screens as a Cloud Service FAQs

The following section provides answers to Frequently Asked Questions (FAQs) related to Screens as a Cloud Service project.

What should I do if AEM Screens player pointing to Screens as a Cloud Service does not pick the custom clientlibs with /etc.clientlibs/xxx/clientlibs/ format?

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.

Using longCacheKey="none" in your clientlib folder removes the long cache keys altogether for these clientlibs.

What should we do if offline manifest does not include all resources as intended?

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

        set principal ACL for bulk-offline-update-screens-service
                allow jcr:read on /content/mysite
                allow jcr:read on /apps/my-resources

What image formats are recommended for seamless rendition of images in an AEM Screens as a Cloud Service channels?

It is recommended to use images in the format .png and .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.

On this page