---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/684adfed58640777cd76d50aeb0c1087/screenshot/689a48fc-2bfb-4d97-b23d-c1b909ddd99b.png"
url: "https://jam.dev/c/052563b2-515c-4026-9589-2d75ca10a87e"
capturedOn: "https://981258cc-d018-4f8a-a191-20ab1d5d3f7a.weweb-preview.io/login/?_source=/"
type: "video"
browser: "Chrome 125.0.6422.142"
os: "Mac OS (arm) 10.15.7"
screen: "1511x819"
country: "US"
timezone: "America/Denver"
author: "Allison Nokes"
date: "2024-06-14T23:14:18.033Z"
---

## Signals

1 console error · 9 interactions

## Comments

**Allison Nokes** · 2024-06-14T23:19:48.046Z · at 0:00

This video shows successful login using Xano Auth and demonstrates the issue with trying to "Login with Google" using the Xano Login Provider workflow.

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).
