Skip to content

deviceId() is null after call initialize() #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
viglis opened this issue May 15, 2025 · 0 comments
Open

deviceId() is null after call initialize() #272

viglis opened this issue May 15, 2025 · 0 comments

Comments

@viglis
Copy link

viglis commented May 15, 2025

SDK Version and configuration details

v1.20.7

Expected Behavior

deviceId shouldn't be null or we need to have a callback to know when amplitude is initialized correctly.

Current Behavior

Hi. For integration for other analytics tool(ex. airbridge) I need to know amplitude deviceId. And it is null after Amplitude.initialize(...) call. But If I fetch deviceId after like a second after initialize call then it is non null.

Possible Solution

I don't know how long to take deviceId.

Steps to Reproduce

Amplitude(Configuration)
client.getDeviceId() == null

Environment

  • Galaxy S23 FE(OS15)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant