Why does Samsung initConnection return invalid session token?

An invalid-session-token error on initConnection almost always means the SDK was initialised with a different dev ID from the one used to generate the auth…

An invalid-session-token error on initConnection almost always means the SDK was initialised with a different dev ID from the one used to generate the auth token.

Make sure init and your generateAuthToken call use the same dev ID, and pass the raw token exactly as returned by the endpoint.

A generic Unknown Error on Samsung permission requests usually means Samsung Health Developer Mode is not enabled on the test device. To fix it:

1

Open Samsung Health > Settings > About Samsung Health.

2

Tap the version number repeatedly to enable Developer Mode.

3

Confirm Samsung Health is fully updated.

4

Confirm your app package name matches what is registered in the Samsung Developer Portal.

If it persists, capture Logcat filtered on the Samsung store manager tag for the precise error.