Issue: User Identification Not Persisting During Purchase Flow

Problem

User identification is not persisting through the purchase flow, causing purchases to fail. While the initial identification appears successful, subsequent verification fails immediately, preventing the purchase from proceeding.

Evidence from Logs

1. Initial user identification appears successful:

Starting executePurchase for product: month3 and userId: oQGXYVDgo5csdHkfoWu5YVs82mc2
Got Qonversion instance
User re-identified with Qonversion. ID: 4d6aa7ef902341dfbc43846975e73b6d

2. But immediately after, verification shows identification was lost:

User ID mismatch or not set. Existing: null, Current: oQGXYVDgo5csdHkfoWu5YVs82mc2
User identification verification failed

3. This causes the purchase to fail:

Error in executePurchase: Exception: Failed to identify user

4. And subsequent checks confirm no identification:

Current CustomUserId: none
No user identified - access denied

Environment

• Platform: Android & iOS
• State: Fresh install
• Login Status: Successfully logged in (Firebase auth successful)
• Store Status: Logged into Play Store & App Store
• Production environment (not sandbox)

Expected Behavior

According to Qonversion documentation, user identification should persist across the purchase flow, allowing the purchase to complete after successful user identification.

Questions

1. Why isn't the user identification persisting after the initial successful identify() call?
2. Is there a timing issue with Qonversion initialization that's affecting user identification persistence?
3. Should the offline cache be preserving the identification state between calls?