SShortSingh.
Back to feed

iOS camera briefly reports wrong orientation for ~100ms, masking a longstanding bug

0
·10 views

A developer investigating sideways video recordings on iPhone discovered that the iOS camera temporarily reports incorrect landscape dimensions for roughly 100–150 milliseconds after a track is created, before correcting itself to portrait. This narrow window explains why the bug went undetected: tests that wait for a preview to load before reading track dimensions always land outside the faulty window and pass cleanly. The developer confirmed the timing across multiple runs, observing the flip from 1920x1080 to 1080x1920 occurring between roughly 100 and 150 milliseconds after track creation. The finding has broader implications beyond iOS, highlighting that any value which eventually corrects itself can silently fool well-written tests that wait for things to settle. The developer also found that most major webcam libraries, including react-webcam and react-media-recorder, are largely inactive, with LiveKit being the only one showing consistent recent human contributions.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How SaaS Teams Can Build CSV Exports That Are Actually Useful to Customers

A practical guide published on DEV Community by developer Uriel Bitto outlines best practices for designing CSV exports in SaaS products. The guide emphasizes scoping exports to a specific user job, using clear column headers, and including stable record IDs so files remain useful outside the app. It recommends using established CSV libraries rather than manual string-joining, and testing output in the tools customers actually use, such as spreadsheets. Security concerns like CSV injection are also highlighted, with advice to apply access controls and sanitize untrusted values based on the intended destination. The core benchmark proposed is whether a customer can open the file, understand its contents, and complete their task without needing the app open beside them.

0
ProgrammingDEV Community ·

Developer builds TikTok downloader, shares lessons on streaming and expiring URLs

A developer recently built a web service called FromTik that allows users to download public TikTok videos, slideshows, and audio files. Rather than saving full video files to disk before delivery, the service streams media in chunks directly from TikTok's CDN to the user, reducing disk usage and speeding up downloads. The developer avoided unnecessary re-encoding with FFmpeg, reserving it only for tasks like extracting MP3 audio or converting slideshows into video. A key technical insight was that TikTok CDN URLs are short-lived and signed, making long-term caching of extracted links unreliable. The article outlines how treating media metadata as request-specific rather than permanently stored leads to a more dependable architecture.

0
ProgrammingDEV Community ·

OpenBot enforces audit logging before any bot action executes, not after

OpenBot, an open-source agent framework described as a template rather than a finished product, routes every bot action through a single gateway that evaluates policy and writes an audit record before the action is carried out. The system uses CEL-based rules to inspect tool names, file paths, shell commands, and other parameters, and is designed to fail closed — a missing or broken policy blocks rather than permits. Sensitive data such as secrets are partially obscured in logs, recording only that a request was made and the length of the value, not its contents. Human takeovers during bot sessions — such as handling login walls or two-factor prompts — are also logged, and bot actions are refused rather than queued while a person is in control. The project is currently in alpha, has no hosted version, and is explicitly intended as a starting point for teams to adapt with their own configuration.

0
ProgrammingDEV Community ·

AI Model Jev Completes 60-Second Highway Drive Without a Single Crash

A developer used TypeSafe AI's decision-focused model Jev to control a simulated vehicle on a three-lane highway populated with 30 surrounding vehicles. After early attempts resulted in immediate crashes or the car stopping completely, the system was refined to ask Jev multiple simultaneous questions about lane changes, speed adjustments, and collision risk. The final run covered 1,203.72 metres in 60 seconds at an average speed of 72.3 km/h, with no collisions or full stops recorded. Jev, described by TypeSafe AI as a 'System One' model, returns typed decisions and probability values rather than conversational text, making it suited for real-time agent control. The experiment demonstrated that the model could apply roughly 2.73 driving decisions per second with a median response latency of around 311 milliseconds.