Skip to content

Instantly share code, notes, and snippets.

GitHub build failure: implicit framework ref and legacy Web API client

  • Issue: Build failed after merging latest base into feature branch.
  • Symptoms:
    • Warning NETSDK1086 about Microsoft.AspNetCore.App FrameworkReference
    • Errors NU1107 around System.Net.Http version conflicts

Root causes

  • Redundant framework reference
@gpena-js
gpena-js / JSAD-5197-Device-Fingerprint-API.md
Last active September 11, 2025 19:00
JSAD-5197: Device Fingerprint API Integration

JSAD-5197: Device Fingerprint API Integration

Scope: Login and process-payment endpoints only
Version: v4 controllers


Quick Overview

We're adding device fingerprinting to 2 endpoints:

@gpena-js
gpena-js / OOBO_Credit_Card_Display_Bug_Report.md
Last active August 20, 2025 15:35
OOBO Credit Card Display Bug Report

Credit Card Display Bug Report - CORRECTED ANALYSIS

🐛 Issue Summary

Credit card confirmation receipts are displaying "Credit Card ending xxxx" instead of showing the actual last 4 digits of credit cards (e.g., "Credit Card ending xxxx1234") for some orders in the Admin portal.

Reported by: Arielle Cline (Guest Relations Director)
Issue ID: JSAD-5189
Priority: Medium (affects 1.96% of registered user orders)
Affected System: Admin Portal - Order Lookup/Confirmation Receipts

Fixing Swagger Compatibility Issues with .NET 8 and Autofac

Overview

After upgrading from .NET 6 to .NET 8, Swagger stopped working in our ASP.NET Core applications that use Autofac for dependency injection. This document explains the root cause, the solution, and the implementation details.

The Problem

Symptoms

  • OJS.App.Admin: Application failed to start with Autofac dependency resolution exceptions

OJS Pick Up Order Issue - Investigation Report

Executive Summary

Investigation into the "OJS Pick Up Order Northlake" issue revealed two interconnected problems affecting both customer experience and admin operations. The root cause stems from a payment processing flow where order records are created before payment validation.

Issues Identified

Issue #1: Admin Interface Crashes

JIRA: JSAD-5131

Hang Reward Issue - Investigation Summary

Date: August 7, 2025
Investigator: Germán Peña
Issue: Users able to claim the same Hang reward multiple times


🔍 Issue Scope

Current Factor4 Setup Analysis

Database Structure

The factor4_storelocation table currently has only 2 records for store_id = 6:

  1. Store-specific record: id=1, store_id=6, location_id=436227, username=loc436227, terminal_id=99
  2. Corporate record: id=2, store_id=6, location_id=628699, username=corporate, password=corporate, terminal_id=None

Factor4Service Method Usage

Store-Specific Credentials (uses GetFactor4StorelocationByStoreId):

Extract user name from Apple SSO token (2025-07-14 14:21Z)

User

Help me find a way to solve an issue with Apple SSO. Some time ago, we discovered that we can’t get the user’s name from the token Apple sends, so in the backend, we’ve been creating the user with a blank name, and the frontend collects the name later.

Recently, however, we received a notice from Apple saying that our implementation is incorrect (see attached image). We need to make this work properly. It might be possible if we extract the user info from the very first token we receive during signup.

Let’s do a deep-search into the documentation Apple provides: https://developer.apple.com/documentation/authenticationservices

Review integrations for completion (2025-06-25 20:53Z)

User

Please review the attached document. I need to complete the sections marked with (Germán). Could you help me go through them one by one?

Start by analyzing the codebase to gather the necessary technical details for each integration listed under my name. Specifically, I need a few bullet points per item describing:

Where and how the integration is used in the system