it will have an impact, we modified the CDN link to v2 by ourselves,
can you please confirm, by looking into the app (by inspecting the deployed app) which points to v2 or the latest version?
For your question, yes, the Crayons V3 update affects existing apps as well. Since all the apps pointed to the latest version and v3 was released recently, all the apps by default started pointing to version 3.
So, we have migrated all the existing apps to point to v2 of the crayons version in the CDN URL.
We couldn’t find if your app points to which version in the screenshots that you have posted. Could you inspect the code of the app and check if the CDN URL has “@2” in it?
In the screenshot shared, it shows the whole Freshdesk page’s code. Could you right-click on the app and inspect the app’s code? You can find the HTML code you have used in the app if you do so.
Could you check if the Crayons CDN URL used in the HTML content of the app has “@2” in the imported script’s CDN URL?
It should look like the following script. <script nomodule="" src="https://unpkg.com/@freshworks/crayons@2/dist/crayons/crayons.js"></script>
@Priyadharshini_Ramas I see this app has “@2” in the imported CDN URL for Crayons. The issue is not with the breaking changes introduced in the Crayons v3.
Could you please debug the issues for any changes in the app? Or help us troubleshoot account to access shared with me (firstname.lastname@example.org) and reproducing steps if the app was not changed and introduced issues in the production?
(Kaustav Das Modak)
split this topic
The app already uses crayons@2 URL, as found by inspecting the app’s iframe
The app uses localStorage to store data in the browser. Given that the Platform has disallowed localStorage usage, this was throwing an Unhandled exception due to not handling any error that may result from the localStorage API call.
Suggestion: Use client.db instead.
This is not a Crayons issue, but an issue arising out of using localStorage, whose exception was blocking rendering of some Crayons components that depend on the resulting data. Once the localStorage code is replaced with client.db there may still be other exceptions that will surface.