fw-app-dev

You can validate your app for Freshworks Platform 3.0 compliance by running /fdk-fix, which checks manifest correctness, request schemas, icon presence, and security rules, and auto-fixes common linting issues before marketplace submission.

The best way to migrate a legacy Platform 2.x app to Platform 3.0 is to use automated checks that guide the upgrade process, enforcing new standards and preventing legacy patterns to ensure your app is ready for the marketplace.

Your Freshworks app fails marketplace validation checks when it does not adhere to Platform 3.0 standards, such as having manifest errors, missing icons, invalid request schemas, or failing security enforcement rules required for submission.

Yes, you can automatically fix manifest and security errors in your Freshworks app by running validation enforcement checks that perform auto-fixes on common linting issues across code, schemas, and configurations to ensure compliance.

Yes, Platform 3.0 app development requires specific request schema validation to ensure strict adherence to marketplace standards, preventing submission delays by enforcing correct data structures and security rules across the app workflow.

You need to run validation checks before submitting your app to the marketplace to ensure it meets Platform 3.0 standards, automatically identifying and fixing manifest, schema, and security issues to avoid rejection delays.