Repository navigation
Integrations and Sync
Project Phoenix includes local-device integrations and Phoenix Portal sync surfaces. Some provider behavior depends on account status, provider availability, and backend support. These instructions are checked against current mobile source and the v1.1.0 tag; additions after that tag are labeled below.
- Open Settings → Cloud Sync → Link Portal Account.
- Sign in to your Phoenix Portal account.
- Use Sync Now and check the result and last-synced time. A partial-success message means some work remains, not that all data is synchronized.
Portal sync supports cross-device training data and server-backed integrations. If the app says Sync paused — subscription required, resolve the account entitlement on the portal; local workout storage is separate from sync status. No specific pricing or deployed backend parity is assumed here.
Switching accounts is not a transfer of all local history. If prompted, choose whether to upload workouts not yet synced or not upload existing data. Previously synchronized data stays associated with its original account. Do not repeatedly retry an ownership refusal as if it were a network error.
Keep full file backups before a device move. Portal sync does not restore everything, notably Polar summaries/traces or device-local integration credentials. Account deletion is managed on the portal, not by deleting workouts in the app.
Open Settings -> Integrations.
Health app support:
- iOS: Apple Health.
- Android: Google Health Connect.
The integration is optional. Grant the platform health permissions before Phoenix can write workouts. If access was denied, use the permission/settings action offered by the card and recheck the status after returning. Optional calorie permissions and platform availability can affect which fields are written.
The Hevy card supports API-key connection, sync, disconnect, and local browsing of imported provider data.
Imported Hevy data can include:
- Workouts.
- Routines.
- Routine folders.
- Exercise templates.
- Body measurements.
Open Integration Data after syncing to browse imported workouts, Hevy routines, and measurements.
Routine detail pages intentionally ask you to review exercise mappings before converting. External weights are preserved as provider information until Phoenix per-cable mapping is confirmed.
The Liftosaur card supports API-key connection, sync, disconnect, and local browsing of imported provider data.
Imported Liftosaur data can include:
- Workout history.
- Programs.
- Current program.
- Program stats.
- Liftoscript text for preview.
Liftosaur program conversion is conservative. Program detail is read-only, with a playground preview flow for scripts when available. Manual Phoenix cycle conversion should happen only after mappings are validated.
The Integrations screen includes Strong / CSV import and export.
CSV support:
- Export Phoenix workout sessions to Strong-compatible CSV.
- Import Strong-format CSV.
- Import Hevy-format CSV.
- Choose kg or lbs for CSV handling.
- Preview import counts, date range, duration, and parse errors before confirming.
CSV imports are stored as external activities rather than rewriting your native Phoenix workout sessions.
The Integration Data hub includes:
- Workouts: imported external activities.
- Hevy Routines: synced routines and folders.
- Liftosaur Programs: synced programs and stats.
- Measurements: imported Hevy measurement records.
Use this hub after syncing providers or importing CSV files.
Polar is a separate Bluetooth sensor connection under Settings → Polar H10 Sensor, not a portal integration.
- Wear and activate the strap, then use the sensor card to scan and Connect to your H10.
- Check the connected state and live measurements before recording. The card offers Reconnect, Disconnect, and Forget for remembered devices as appropriate.
- Enable Save raw ECG only if you want to retain the detailed ECG trace. It is off by default.
- Record the workout. Merely opening the workout screen does not start automatic scanning or ECG/accelerometer streaming. An explicit Disconnect stays effective until you reconnect.
Polar can provide heart rate, R-R intervals, ECG preview, torso movement, and optional five-minute post-workout recovery tracking. A 60- or 300-second recovery value is saved only after that observation window completes. Canceling early leaves unfinished measurements unavailable.
Data limits: Polar summaries and traces stay on this device and in exported file backups, not Phoenix Portal. Backups always preserve summaries; beat samples, ECG, and synchronized metric samples require Include raw telemetry. Raw ECG capture is capped at five minutes per recording; stored traces expire after 30 days and storage is bounded, so old traces can disappear while summaries remain. A previously exported backup is not changed by local expiry.
These measurements describe training, not a clinical risk assessment. The repository retains physical-device release checks, including simultaneous trainer/Polar reconnect on iOS; do not assume every phone/strap combination has been verified.
This is present in current main after the v1.1.0 tag. Do not expect it in every v1.1.0 installation. If Settings → Integrations → Send workouts is present:
- Enter your Intervals.icu Athlete ID and API key.
- Save and Test connection. A successful test leaves sending off.
- Read How sharing works, then choose Turn on sending to opt in.
- Keep Phoenix open with network access to send queued activities, and check the counters for this profile and athlete.
Each newly finished workout is sent as a strength-training activity with set reps and weights, plus average/maximum heart rate when recorded. A strap is not required. Existing history is never backfilled. Later edits and deletions in Phoenix are not propagated. Phoenix sends directly to Intervals.icu, not onward to other services.
- Saved means stored locally; Queued means waiting; Sent means remote delivery was confirmed.
- Pause sending stops sending; workouts finished while paused are not sent later.
- Upload status unknown requires Check upload status, not blind resubmission.
- Disconnect turns sending off and removes the key from this phone. It does not delete activities already sent to Intervals.icu.
- Credentials are device-local secure-storage data, not part of ordinary JSON training backups. Restore also revokes local Intervals sending authorization; set it up and explicitly enable it again afterward. Reconfigure on another device. Background sending is not guaranteed.
- Builds containing this integration disable raw support ZIP exports to avoid exposing credential-bearing database files. Regular JSON training backups remain available.
- Confirm the phone has network access.
- Confirm the provider API key is valid.
- Disconnect and reconnect the provider if token or permission errors persist.
- Check Settings for persistent sync errors.
- For repeated failures, describe the provider, action, app version/build, and exact error. Review any logs before sharing; never post API keys, account tokens, or an unreviewed full backup in a public issue.
Project Phoenix is an independent community rescue app for Vitruvian owners. It is not affiliated with, endorsed by, or sponsored by Vitruvian.