---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/fb54f2418fed3bfa7b77d239b3a1923f/screenshot/1097dc5a-d186-4ffb-8215-4efac0a3042f.png"
url: "https://jam.dev/c/3bce6734-c313-4b82-a638-4022254bfb7a"
capturedOn: "http://localhost:8081/"
type: "video"
browser: "Mobile Safari 16.6"
os: "iOS 16.6"
author: "kwalsh"
date: "2023-12-05T15:59:33.437Z"
---

If you look at the network tab, you can see that one of the requests 401's because getToken() returns null after the user signs in. It's a race condition that did not exist in 0.10.6 of clerk-expo.

## Comments

**kwalsh** · 2023-12-05T15:59:33.437Z

If you look at the network tab, you can see that one of the requests 401's because getToken() returns null after the user signs in. It's a race condition that did not exist in 0.10.6 of clerk-expo.

## Get the full capture

This page is a summary. The console logs, network requests, video/screenshot, and device info are exposed through the Jam MCP server — connect an agent to `https://mcp.jam.dev/mcp` and start with `getDetails` (setup: https://jam.dev/docs/jam-mcp).

Prefer the terminal? Install the Jam CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).