Compatibility should be assessed across the complete stack, not only the app’s version number. The following values describe the source inspected for this documentation; they are not a completed test certification.
| Component | Declared configuration | What it establishes |
| Flutter app | 2.0.0+6 | App version and build in pubspec.yaml |
| Customer API module | 2.0.0 | Module header version |
| Perfex CRM | Module declares 3.0.* minimum | Declared prerequisite, not all-version coverage |
| Dart | ^3.12.2 | Package SDK constraint |
| Flutter | Exact tested version not recorded here | Must be validated for the release |
| Android Gradle Plugin | 9.0.1 | Build configuration |
| Gradle wrapper | 9.1.0 | Wrapper configuration |
| Java/JVM source target | 17 | App compile target |
| Kotlin plugin declaration | 2.3.20 | Settings declaration |
| iOS deployment target | 13.0 in project settings | Must also satisfy resolved native dependencies |
| PHP, database, Xcode | Tested versions not established here | Check release validation before deployment |
Before upgrading
Confirm the tested versions for the release you are installing. Ask about your exact combination if it is not listed. Keep the mobile app and module aligned with the same API contract.
A successful debug build or a module’s minimum-version header does not prove production compatibility. Validate a signed Android release, an iOS archive, and the customer workflows against the intended Perfex/PHP environment before updating production.