Environment
- Device: Garmin Instinct 3 Solar 50 mm
- Mobile platform: Apple iPhone / iOS
- Application: Garmin Connect IQ Store
- Affected section: My Watch Faces → Uninstalled
Issue Description
The Connect IQ Store application on iOS does not consistently persist the deletion of previously uninstalled watch faces from the “Uninstalled” list.
When a previously uninstalled watch face is removed from this list, it disappears immediately. However, after the Connect IQ Store application is completely closed and reopened, the same watch face may reappear.
This behavior was reproduced multiple times and involved different watch faces.
Initial Issue – Vega Watch Face
The issue was initially observed with a watch face named “Vega”.
- Opened Connect IQ Store.
- Navigated to My Watch Faces → Uninstalled.
- Deleted the Vega entry.
- Confirmed that Vega disappeared from the list.
- Completely closed the Connect IQ Store application.
- Reopened the application.
Actual result: Vega reappeared in the Uninstalled list.
The same behavior occurred repeatedly.
Additional testing was performed with internet connectivity disabled. Vega was still visible after restarting the application, although this test alone does not establish whether the underlying cause is local caching or previously synchronized data.
Further Investigation – Application Reinstallation
The Connect IQ Store application was completely deleted from the iPhone and reinstalled.
After signing in again, an unexpected result was observed:
- Vega was no longer present.
- Two other watch faces that had been deleted much earlier appeared in the Uninstalled list:
- Minimalistic Watch (LaurentiuRaducu)
- 7 Segments Simple (PermanentWave)
These two watch faces had not appeared during the previous tests.
Both entries were then deleted from the Uninstalled list.
After completely closing and reopening Connect IQ Store, both entries reappeared.
This suggests that the issue is not specific to an individual watch face.
Successful Workaround
The following sequence was subsequently tested:
- Deleted the unwanted watch-face entries from the Uninstalled list.
- Performed a Garmin device synchronization.
- Completely closed the Connect IQ Store application.
- Deleted the Connect IQ Store application from the iPhone.
- Reinstalled the application from the App Store.
- Signed in again and checked My Watch Faces → Uninstalled.
Result: Both previously recurring entries were no longer present. The original Vega entry was also absent.
All three affected watch faces had therefore been successfully removed from the list during the final verification.
Technical Assessment
Based on the observed behavior, there may be an inconsistency between the locally stored application state and the watch-face records associated with the device or Garmin account.
The fact that reinstalling the application caused different previously deleted watch faces to appear suggests that the list may be reconstructed from multiple sources or from previously persisted records.
Additionally, the successful workaround involved explicitly synchronizing the Garmin device before reinstalling Connect IQ Store.
This may indicate that synchronization order or state persistence is relevant to the issue.
However, these are hypotheses based on observed behavior. The exact root cause has not been confirmed.
Expected Behavior
When a user deletes an uninstalled watch-face entry, the deletion should persist across application restarts, device synchronization, and application reinstallation.
Previously deleted watch-face entries should not unexpectedly reappear.
Actual Behavior
Deleted entries may return after restarting the application. Reinstalling the application may also cause different previously deleted entries to reappear.
Suggested Investigation
Please investigate how Connect IQ Store for iOS maintains and synchronizes its Uninstalled watch-face list, particularly:
- Persistence of deleted entries
- Local cache versus account-associated records
- Device synchronization behavior
- Reconstruction of the list after application reinstallation
The issue was resolved through the documented workaround, but the underlying behavior appears inconsistent and may affect other users.
Thank you.
