关于branch.io中+is_first_session卸载重装后值随机的问题反馈

Hey there, I feel your frustration—dealing with inconsistent behavior after 20+ tests and two support tickets is no fun. Let’s walk through some targeted checks and angles you can pursue to get to the bottom of this +is_first_session issue:

• Persistent local data leftovers: Many platforms retain small bits of app data even after uninstall. For example:
  • On Android, default auto-backup might save Branch’s cache files. Try adding android:allowBackup="false" to your manifest temporarily, or create a backup rule that excludes Branch’s storage directories.
  • On iOS, iCloud backup could be preserving session-related data. Disable the app’s iCloud backup in device settings, delete any existing backups for the app, then reinstall fresh.
• SDK initialization timing: If you’re fetching +is_first_session before the Branch SDK finishes syncing with their servers, you might get premature, incorrect values. Double-check that you’re accessing this parameter only after receiving the successful initialization callback from the SDK.
• Device identifier linking: Branch’s backend might be tying your reinstalled app session to a previous one via persistent device IDs (like IDFA, ADID, or a device UUID that doesn’t reset on uninstall). Ask their support team to pull server logs for your test device’s identifiers—this can show if sessions are being incorrectly associated across reinstalls.
• Clean test environment: Ensure each test is a truly fresh start: restart your device between reinstalls, manually clear any residual app data (if your OS allows), and avoid reusing the same user account across tests if user-specific tracking is enabled.

Since you’ve already submitted support tickets, pushing for deep log analysis from their team is your best bet. They can cross-reference your device’s event history with their backend to spot exactly where the session misclassification is occurring.

内容的提问来源于stack exchange，提问作者Parin Shah