Garmin Connect does not open since latest app update 5.17.1

[stanwood77]

Affected app
Name: Garmin Connect
Package id: com.garmin.android.apps.connectmobile

Describe the bug
Since latest Garmin Connect update 5.17.1, the app does not open. Instead, the application will simply stay forever on the startup screen (Black screen with “Connect” logo in the middle).

Steps to Reproduce
Open Garmin Connect app, it won't open.

Expected behavior
The app should start normally

Screenshots
See below (end of the ticket)

System
Android Version: 15
Custom ROM: /e/OS 3.1.3-Official

microG
microG Core version: 0.3.8.250932-23 (b32e1cd)
microG Self-Check results: All ticked

Workaround
Temporary workaroud: Open any .gpx file "with Garmin Connect", and the app opens directly in the itinerary. Then use the back up-left arrow twice to go back to the main menu.
This workaround must be used each time we want to open the app...

Additional context
Bug has been confirmed by multiple users, including VollaOS (Micro-G) and LineageOS for Micro-G

A tread is available here:

https://community.e.foundation/t/garmin-connect-fails-to-start-with-latest-update/75199

A ticket is already opened in e-Gitlab: https://gitlab.e.foundation/e/backlog/-/issues/8920

Logs: (from another user)

09-18 18:01:41.103 4638 6139 W SplitInstallService: refusing to perform split installation for com.garmin.android.apps.connectmobile as the service is disabled

Then, the user was able to bypass warning by activating “Installation à la demande composants” option in MicroG, which gives him now:

09-18 18:17:26.422 10199 21676 I PlayCore: UID: [10196]  PID: [10199] SplitInstallService : startInstall([gcm_on_demand_resources],[])
09-18 18:17:26.424 10199 10497 I PlayCore: UID: [10196]  PID: [10199] SplitInstallService : Initiate binding to the service.
09-18 18:17:26.437  4638  4638 D SplitInstallService: onBind: 
09-18 18:17:26.453 10199 10199 I PlayCore: UID: [10196]  PID: [10199] SplitInstallService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com.google.android.finsky.splitinstallservice.SplitInstallService})
09-18 18:17:26.456 10199 10497 I PlayCore: UID: [10196]  PID: [10199] SplitInstallService : linkToDeath
09-18 18:17:26.457  4638  4658 D SplitInstallService: Method <startInstall> Called by package: com.garmin.android.apps.connectmobile
09-18 18:17:26.462  4638  4638 V SplitInstallManager: splitInstallFlow: start
09-18 18:17:26.462  4638  4638 V SplitInstallManager: splitInstallFlow will query for these packages: [gcm_on_demand_resources]
09-18 18:17:26.478  4638  4638 V SplitInstallManager: splitInstallFlow oauthToken: AuthData(email=XXXX, authToken=XXX, gsfId=XXXX, deviceCheckInConsistencyToken=XXXX, deviceConfigToken=, experimentsConfigToken=, dfeCookie=)
09-18 18:17:26.869  4638  4638 V SplitInstallManager: splitInstallFlow requestDownloadUrls returned these components: null
09-18 18:17:26.869  4638  4638 D SplitInstallService: startInstall: installStatus -> false

But still doesn't work.

Here's a summary of ChatGPT concerning this issue, after having fully analyzed all the logs and the complete description of the problem (consider with caution!):

"The logs show that Garmin Connect tries to use PlayCore / SplitInstallService, a Google component used to download and load additional modules ( the famous Dynamic Feature Modules ) on demand.
Without official Google Play Services → the request fails, as Micro-G seems to has only a partial implementation of this.
When the user activates ‘On-demand component installation’ in MicroG, it goes a little further (simulated service connection), but in the end requestDownloadUrls returns null → so the app remains blocked.

In summary:

This is not just a ‘UI’ bug, Garmin Connect really needs a service that MicroG does not yet fully imitate.
The GPX workaround just bypasses the initial phase where the app looks for this module.
So it seems that MicroG would improve its support for SplitInstallService. In the meantime, we either stick with the GPX trick or... downgrade Garmin Connect to a version prior to this dependency."

Thank you for your attention!
stanwood

[pjaap]

Thank you for reporting this. I also face the problem on LineageOS with MicroG.

My "workaround" is to install version 5.16.2 with version code 10077 from Aurora.

[typhoon2099]

In addition to the GPX trick, you can also open a recent activity from the notification.

[bbbxyz]

Same issue with microg version 0.3.9.250932

[pbuyle]

Same issue with LineageOS for microG 22.2-20250823

[MazeWebArchitect]

Same issue with CalxyOS 6.10.20, microG 0.3.7.250932-18 (b12b324)

[Tomoms]

I confirm that 5.17 is the last working version and 5.17.1 is the first broken one. Apart from the workarounds others mentioned, if you use AppManager you can create a shortcut on your homescreen to some internal app activity such as My Device Activity, or Gear Activity, and launch the app from it. With a tap on the back arrow you can then easily get to the main screen.