Skip to content

Source Code, Environment, and API Configuration ​

The mobile client covered by the V3 documentation uses UniApp X, Vue 3, UTS, and .uvue pages. Obtain the fastbee-app source that matches the backend from the deployment owner, configure service endpoints, and test each target. Do not reuse the old env.config.js or Vue 2 project layout.

1. Before You Start ​

ItemDetails
Entry pointOpen the mobile source directory in HBuilderX, not the documentation repository
PermissionsSource access, a test account, and access to the test API and MQTT service
Version checksRecord the source commit, HBuilderX version, target platform, and backend build; follow tool requirements for the delivered version

2. Find Configuration and Source Files ​

File or directoryPurposeWhat to check
env.config.utsEnvironment values such as API_URL, MQTT_URL, BASE_URL, and OS_URLAPI and MQTT belong to the same target environment, and policy pages can be opened
manifest.json, platformConfig.jsonTargets, application identifiers, versions, permissions, and build settingsThe target platform and AppId or application ID match the delivery record
pages.json, pages/, pagesA/, pagesB/Main package, subpackages, bottom navigation, and feature pagesChanged pages belong to the right package, and protected routes still require login
apis/modules/, utils/request.utsAPI modules, authentication, and request handlingNew APIs use the shared request wrapper rather than hard-coded service URLs
common/mqttTool.uts, utils/bleCompat.utsPlatform adapters for live communication and BLEVerify the connection and permissions for each target. H5 results do not prove physical device support

3. Run and Test the Integration ​

  1. Install dependencies using the mobile repository's lockfile. When it ships with package-lock.json, run npm ci in the mobile source directory. This is not the documentation site's build command.
  2. Configure the test API and MQTT endpoints and select the target in HBuilderX. Use a browser to check startup, login, and lists. Import the Mini Program into WeChat DevTools and use the relevant debug base app and physical device for native capabilities.
  3. View a device and a known report with an authorized account. If login works but readings do not update, check the API request, live connection, device reports, and property scope separately.

3.1. Trace Page Requests to the Actual Environment ​

  1. HTTP requests. In the H5 browser's Network panel, watch the login, device list, and device detail requests in sequence. Confirm which environment receives each request. Check the HTTP status and the API's business result separately. A page response or successful HTTP status does not establish that the operation succeeded.
  2. Live connection. Once the device list loads, verify that the target client connects and receives a new report from the intended device. In the browser, inspect the WebSocket connection and messages. On other platforms, use platform debugging tools or server logs. An established connection alone does not prove the subscription scope is correct.
  3. Resources and policy pages. When login and the live connection work, check resources and policy pages loaded separately. If only this content fails, trace the failed URL back to BASE_URL, OS_URL, and the deployment entry point instead of treating it as a general API failure.

Isolate Environments

Do not include real tokens, keys, signing files, or internal endpoints in docs, screenshots, or logs. Verify secure API and live connections on HTTPS pages. Do not disable security checks as a delivery workaround.

4. Verify the Result ​

SituationWhat to check first
The page opens but login or list requests failAPI address, proxy, account environment, authentication, and browser cross-origin rules
The list loads but readings do not updateMQTT connection, subscriptions, recent device reports, and property mapping
H5 works but the native app or WeChat failsConditional compilation, application ID, permissions, service domains, and the device build

See the official uni-app x documentation for general framework and platform information. Next: App Build, Signing, and Release or Configuration, Review, and Release.