Cookie Handling for Twitch Authentication: One of the initial challenges faced was related to Twitch authentication. The cookies required for authentication were not being sent in the headers. After thorough investigation, I identified the root cause and made necessary configuration changes to ensure that cookies were properly included in the headers, resolving the authentication issue.
SSL Requirement for Twitch Subscription Events: To test Twitch subscription events on my local development environment, I needed a URL with SSL. This led to the discovery and implementation of Ngrok, which provided a secure tunnel to my local port.
Data Verification with Twitch: Encountered challenges in verifying that users were authorized to perform certain actions, especially when it came to opening chests using signed typed data. A minor discrepancy, such as a single space, led to hours of debugging to ensure data integrity.
Token Management: Ensuring that access and refresh tokens were securely stored and efficiently retrieved was crucial. Implementing Redis for this purpose provided a robust solution, but it required careful handling to ensure tokens were always up-to-date and valid.
Real-time Updates with SSE: Implementing SSE to provide real-time updates to users presented its own set of challenges, especially when it came to managing multiple clients and ensuring that each client received the correct updates.
API Deprecated: An API endpoint I relied upon for fetching the followers count had been deprecated. This posed a potential setback as the followers count was integral to our platform's user analytics. However, undeterred by this obstacle, I delved into the updated API documentation, identified the new endpoint, and made the necessary modifications to our codebase.

Simulating/Testing Events in Stream Elements