Frontend-Backend Version Compatibility
Mobile and backend versions are maintained independently. Do not assume arbitrary combinations work because they fall under the FastBee V3 documentation. Record the client build, platform, and service version, and use test results to decide the upgrade order.
1. Before You Start
| Item | Details |
|---|---|
| When to use this guide | Client or backend upgrades, deployment switches, or cross-version troubleshooting |
| What you need | A test environment that can be rolled back, previous and candidate clients, an authorized account, and a test device |
| What to record | Client commit and package version, target platform, backend build, API and MQTT environment, and verification time |
2. Check Compatibility by Workflow
| Check | Expected result |
|---|---|
| Login and permissions | Previous and candidate clients sign in as planned; unauthorized devices cannot be controlled; expired sessions have a clear prompt |
| Device list and history | The account can query the expected devices and history by time and property; empty results are not shown as zero readings |
| Real-time monitoring | The live connection and subsequent reports work, in addition to successful API requests |
| Control and feedback | Verify the command record and feedback or observed state on a test device, not just the client prompt |
| WeChat notifications and native permissions | Verify authorization, template delivery, scanning, and BLE on each relevant physical device; H5 is not a substitute |
3. Choose a Rollout Order
- Start with the last working combination. Test the previous client with the new backend, then the new client with the new backend. For staged rollout or backend rollback, also verify the new client with the previous backend.
- For incompatible fields, authentication, or messages, record affected platforms and symptoms. If older clients are still in use, provide compatibility or explicitly end support before rollout. Passing on one platform does not verify all users.
- Keep the previous package, service configuration, and rollback steps. After rollout, verify login, the device list, live reports, and command feedback before broadening use.
3.1. Version Combinations and Release Criteria
| Version combination | Why test it | If a check fails |
|---|---|---|
| Previous client + previous backend | Establish the baseline and known issues for comparison with the same account and device | Check whether the issue already exists before calling it a regression |
| Previous client + new backend | Confirm that users who have not upgraded can complete critical workflows if the service upgrades first | Do not switch all traffic. Fix compatibility or change the upgrade order |
| New client + new backend | Verify the candidate combination's features and permissions | Do not expand the trial if a critical workflow fails. Record the platform and versions |
| New client + previous backend | Check whether client-first rollout, staged rollout, or backend rollback will work | Record dependencies that prevent independent rollback and return to a verified combination |
For each combination, record Pass, Fail, or Not Verified separately for each delivered platform. An H5-only test leaves the native app and WeChat physical-device checks marked Not Verified.
4. Troubleshoot and Roll Back
First separate wrong environment settings and missing permissions from an actual version mismatch. Record sanitized request times, error codes, reproduction steps, and both versions. If a critical workflow fails, return to the last verified combination and check login, queries, and reports again. Rolling back the client alone may not restore interfaces or settings already changed on the backend.
Before rollback, confirm which client, backend, service configuration, and data changes can be reverted. After rollback, rerun the critical workflows with the same account scope, device, and property as before deployment. If the client still points at the failing environment, restore its environment configuration before rechecking.
See Source Code, Environment, and API Configuration for environment settings, and App Build, Signing, and Release and Configuration, Review, and Release for target-specific release checks.
5. Record a Failure Others Can Retest
| What to record | Example: The list loads, but live data does not refresh |
|---|---|
| Versions and environment | Record the client version or build, target platform, backend build, and environment alias |
| Reproduction steps | Use a test account to open the same test device, switch to the monitor tab, and wait for a known report |
| Expected and actual result | The target property's timestamp should update, but it still shows the time before the report |
| Minimum evidence | Record the time and time zone, sanitized device number, property identifier, and relevant request or live connection state. Do not attach a token or the complete message payload |
| Retest result | Retest with the same account scope, device, and property. Record separately whether the backend received the report and whether the client updated. Mark untested platforms Not Verified |


