Skip to main content

 

Why is the SignIn event being triggered? Under what circumstances is the SignIn event reported?

SignIn is not a custom event that I defined. It seems that the SignIn event is reported every time setUserId is called, even when it's called during SDK initialization.

However, this SignIn is not a true sign-in in the app's user flow. How can I avoid this situation, or where should I call setUserId?

Currently, I'm integrating Amplitude into my Android App. I'm initializing Amplitude in the Application's onCreate method, after super.onCreate(), and then calling setUserId. The code is roughly as follows:

super.onCreate()

val configuration =
Configuration(
apiKey = AMPLITUDE_API_KEY,
context = applicationContext,
autocapture =
autocaptureOptions {
+sessions
+appLifecycles
+deepLinks
+screenViews
}
)
amplitude = Amplitude(configuration)

// Update user info if available
if (userInfo.id.isNotBlank()) {
amplitude.setUserId(userInfo.id)
}

Sorry, this is the event that was reported from code my colleague added.


Reply