Skip to content

Conversation

@kaushalkapasi
Copy link
Collaborator

@kaushalkapasi kaushalkapasi commented Jun 10, 2025

  • fix: use a cached config (if available), if identify user request fails

@kaushalkapasi kaushalkapasi changed the title fix: try to use cached config (if available) if identify user request fails for any reason fix: use cached config if identify user fails Jun 10, 2025
@kaushalkapasi kaushalkapasi force-pushed the fix-use-cached-config-on-identify-failure branch from ad817d4 to 3498bee Compare June 10, 2025 18:06
@kaushalkapasi kaushalkapasi force-pushed the fix-use-cached-config-on-identify-failure branch from 3498bee to e241997 Compare June 10, 2025 20:55
}
}
} catch {
Log.error("Error calling identifyUser for user_id \(String(describing: user.userId))", tags: ["identify"])
Copy link
Collaborator Author

@kaushalkapasi kaushalkapasi Jun 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jsalaber added this as well, logically I also want to use a cached config here in the event there is an error thrown, however would this be a duplication since its already called within the inner identifyUser?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think it's fine, it tells us the error came from the identifyUser

@kaushalkapasi kaushalkapasi force-pushed the fix-use-cached-config-on-identify-failure branch from e241997 to be8d98a Compare June 11, 2025 13:37
@kaushalkapasi kaushalkapasi merged commit bc8970b into main Jun 11, 2025
8 of 10 checks passed
@kaushalkapasi kaushalkapasi deleted the fix-use-cached-config-on-identify-failure branch June 11, 2025 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants