And then I try to add ?dev=true to the url (https://mydomain.freshservice.com/helpdesk/tickets/1?dev=true) but after loading the page the “?dev=true” disappearing from the url and the app is not appearing at all.
Shared details like fdk version, node version & chrome version are almost similar to mine & looks valid. Templated app using freshworks cli should work without issues. Can you share us the app zip or HAR file to understand this better?
Thank you for your reply.
Not sure HAR is, but about the app zip - its the simple “fdk create” quickstart, “your_first_app” that the fdk privodes (Quick Start)
“your_first_app” template is working fine. HAR format is a JSON-formatted archive file that records all network interaction between a web browser and site.
Not sure which app location you’re trying & manifest contents - that’s the reason I’ve asked the app zip. I’m also attaching the zip that’s scaffolded the same way & working fine for me below just to cross verify with yours (if any).
Hey @mariappan
I tried using the file you sent, I updated the node version to 14.19.3 like yours, still not working.
When I append the dev=true, it just dissapearing after the page finish to loading
The HAR file is to big to upload here (45.5m)
This is the file I tried to run:
.fresh.rar (4.4 KB)
I have also noticed this to be an issue when trying to test applications locally while using Freshservice’s Modern Ticket UI. Tickets are appending “?current_tab=details” to the ticket properties page.
This is causing interference with our current documentation. I can confirm that how @Roy managed to solve the issue does in fact work. My questions are should the product team fix the url endpoint to end in just the ticket id? Is this going to interfere with API calls? And should the documentation for both the FDK and the additional logging when using the FDK reflect the new url while using the Modern UI?
If we are going to need to simply combine “dev=true” in with the current appended query string, then we should be sure to make an announcement to the Developer Community to save our developers time in search for a solution.
Thanks @Roy for going through and finding a solution. I am glad I stumbled across your post, or I would have been pulling my hair out looking for a solution lol.