Skip to content

Conversation

@pilip-ton
Copy link

@pilip-ton pilip-ton commented Dec 4, 2025

Fixes #51

Problem

When app_name is changed but token remains the same, storage contains mixed valid/invalid events causing batch requests to fail with authorization errors.

Solution

Use token + appName as storage key instead of just token. This ensures separate storage for each app_name, preventing data mixing.

Changes

  • Storage key format: BATCH_KEY + '-' + token + '-' + appName
  • Each token+appName combination has isolated batch storage

@pilip-ton pilip-ton requested a review from sorawalker December 4, 2025 19:19
@pilip-ton pilip-ton marked this pull request as draft December 4, 2025 19:59
@pilip-ton pilip-ton marked this pull request as ready for review December 4, 2025 21:03
@pilip-ton pilip-ton changed the title Сlear storage on invalid app name Separate batches by token+appName Dec 4, 2025
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

Successfully merging this pull request may close these issues.

Error: Invalid app_name is specified

3 participants