I’m facing an issue while testing a Freshservice app (Platform version 3.1) that uses OAuth for authentication (account-level access).
The app follows the official documentation for Platform 3.x apps and is being tested as a custom app.
Observed Issues
-
App stuck after successful OAuth
-
The OAuth flow starts and authentication completes successfully.
-
The redirect URI is correctly set to:
https://oauth.freshdev.io/auth/callback -
After successful authentication, the app hangs — it seems to be stuck waiting for the handshake to complete.
-
In the network tab, requests remain pending indefinitely after redirection.
-
-
Page doesn’t load in Incognito mode
- When testing the same flow in an Incognito window, the app page fails to load entirely.
Configuration Details
manifest.json
{
"platform-version": "3.1",
"modules": {
"service_ticket": {
"location": {
"ticket_background": {
"url": "index.html"
}
}
}
},
"engines": {
"node": "18.20.8",
"fdk": "9.6.0"
}
}
oauth_config.json
{
"integrations": {
"freshservice": {
"display_name": "Freshservice app",
"client_id": "fw_ext_8xxxxxx2",
"client_secret": "ixxxxxxxxy",
"authorize_url": "https://<%= oauth_iparams.domain %>/org/oauth/v2/authorize",
"token_url": "https://<%= oauth_iparams.domain %>/org/oauth/v2/token",
"options": {
"scope": "freshservice.tickets.view"
},
"token_type": "account",
"oauth_iparams": {
"domain": {
"display_name": "Organization URL",
"description": "Enter your Freshworks organization URL",
"type": "text",
"required": true
}
}
}
}
}
Additional Notes
-
Tested in both regular and incognito modes.
-
Using FDK 9.6.0 and Node 18.20.8.
-
No explicit console errors — only pending network requests post-authentication.
Has anyone else encountered similar OAuth behavior on Platform 3.1?
Any suggestions or debugging pointers would be appreciated.
