Skip to content

Conversation

@chungdaniel
Copy link
Contributor

Problem

The underlying Amplitude-Kotlin supports deviceId being passed as a parameter as part of the Configuration object to set deviceId during initialization. The Flutter SDK plugin did not parse the deviceId and pass it through to the Kotlin SDK, so this did not actually occur.

Solution

Grab deviceId in getConfiguration method in AmplitudeFlutterPlugin.kt so that it is correctly passed through to Kotlin SDK.

Testing

Manually tested that deviceId is now reflected in initialization

Jira: https://amplitude.atlassian.net/browse/AMP-141303
Fixes #281

@chungdaniel chungdaniel merged commit 67698ff into main Oct 8, 2025
4 checks passed
@chungdaniel chungdaniel deleted the AMP-141303/android-device-id branch October 8, 2025 22:50
justin-fiedler pushed a commit that referenced this pull request Oct 9, 2025
## [4.3.8](v4.3.7...v4.3.8) (2025-10-09)

### Bug Fixes

* **android:** deviceId now passed as parameter to native Android SDK ([#282](#282)) ([67698ff](67698ff))
@github-actions
Copy link

github-actions bot commented Oct 9, 2025

🎉 This PR is included in version 4.3.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

userId and deviceId in Configuration are ignored

2 participants