Check the exact tasks you need before relying on an app in a gym with limited connectivity.
Test your usual workflow
On your installed version, check starting a routine, entering a set and reopening history without a connection. A successful test of one task does not establish every feature’s behavior.
Separate local tasks from services
Purchases, restoration of entitlements, support and other connected services may need a connection. Do not infer offline behavior from a minimalist interface.
Keep a fallback record
If reliable logging is essential, have a way to note your completed sets until you can confirm they are saved. This article does not promise complete offline support or automatic synchronization in Weights.
Test the exact disconnected workflow
Before depending on an app in a gym with poor reception, use a disposable sample session to check exercise access, recording, saving and reopening without connectivity. Afterwards, reconnect and inspect the record again. Keep purchases, downloads and account-dependent features separate from the core logging test. A successful launch screen in airplane mode does not establish that every later step works offline. This is a test checklist, not a report of a completed Weights device test.
Protect the only copy of your workout
If you cannot confirm a save, retain a temporary note of the completed sets until you can verify the record. Do not repeatedly reinstall the app to troubleshoot while it may contain the only copy of your history. Export availability and automatic synchronization need their own checks. The current evidence does not promise complete offline support for Weights; confirm the behavior on the version and device you intend to use.