Customer not recognized as review owner - Reply/Update Rating features unavailable

Resolved 💬 2 comments Opened Dec 17, 2025 by brucer42 Closed Dec 17, 2025

Summary

When a customer views their own review on a business detail page, they are shown as "Anonymous Customer" instead of "✨ Your Review". This prevents access to the conversational review features:

  • "Reply to Business" button
  • "Update Rating" button

Expected Behavior

  • Customer's own reviews should display "✨ Your Review" marker
  • "Reply to Business" button should appear after business responds
  • "Update Rating" button should be available on own reviews

Actual Behavior

  • All reviews show as "Anonymous Customer"
  • No Reply or Update Rating buttons visible
  • isOwnReview check fails because review.customer_id !== userProfile?.id

Root Cause

The isOwnReview check in WebBusinessDetailScreen.js compares:

const isOwnReview = review.customer_id === userProfile?.id;

This fails because either:

  1. userProfile.id isn't being passed/loaded correctly to the component
  2. The review's customer_id doesn't match the logged-in user's profile ID
  3. Reviews may be created with a different/null customer_id

Steps to Reproduce

  1. Login as customer (e.g., toddd@123.com)
  2. Navigate to a business and submit a review
  3. View the business detail page again
  4. Observe: Review shows "Anonymous Customer" instead of "✨ Your Review"

Files to Investigate

  • src/screens/WebBusinessDetailScreen.js - isOwnReview logic (around line 970)
  • src/App.js - userProfile prop passing to WebBusinessDetailScreen
  • Review submission logic - ensure customer_id is set correctly

Impact

  • Customers cannot reply to business responses
  • Customers cannot update their rating after business interaction
  • Conversational review feature is effectively broken for web users

Discovered During

E2E Playwright test for review conversation flow (testing/generated/review-conversation.spec.js)

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗