JAVAiOSwithAI YouTube channel episodes – iOS ↔ Backend Spring Micro-service communication flows
Create a backend API endpoint that returns all chapter screenshot URLs stored in MinIO S3, and integrate it into the iOS app to render a thumbnail strip per published story.
What happens when an existing user deletes and reinstalls the app — the iOS conflict recovery mechanism and why it was broken by a wrong HTTP status code on the server side.
Bug fix and architecture update session — adds separate job status tracking for screenshot processing, fixes the re-upload duplicate key issue, and verifies the full delete chain end-to-end.
This documents the Chapter Thumbnail feature — displaying chapter screenshots from MinIO S3 as a horizontal scroll row on published
This documents the Delete Story flow — a synchronous pipeline that deletes screenshots from MinIO S3, then removes the AdventureTubeData
This documents the Chapter Screenshot Service — an async pipeline that extracts screenshots from YouTube videos at each chapter timestamp
This documents the complete request flow when an iOS user publishes a story (geo data) through the AdventureTube microservice architecture.
This page documents all communication flows between the iOS app and the AdventureTube backend microservices and will be posted as
