How to Safely Use Expo OTA Updates Without Crashing Your App

·1 views

Expo's over-the-air (OTA) update system via eas update lets developers push JavaScript changes to users instantly, but misconfiguration can cause permanent crash loops. The most critical setting is runtimeVersion, which must match between a native build and any OTA update delivered to it — a mismatch can break an app before it can even fetch a fix. Developers are advised to use the fingerprint policy instead of appVersion, as it automatically detects changes to native code, config plugins, and dependencies. Certain changes — such as adding native packages, modifying config plugins, or bumping the Expo SDK — always require a full store build and cannot be safely shipped as OTA updates. Additional best practices include testing updates on preview builds with dedicated channels and understanding that rollback means republishing a previously working update, not pressing an undo button.

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)

Developer Builds Webhook Proxy Tool After Silent Stripe Failure Cost Him a Customer

A solo developer lost a paying customer after a Stripe webhook silently failed during a server hiccup, leaving the user without account access for days. The failure produced no alerts or logs, making it invisible until the customer complained via email. In response, the developer built Webhook Proxy, a middleware layer that sits between webhook providers like Stripe or Zapier and a target endpoint. The tool automatically captures payloads, catches 500 errors and timeouts, and allows one-click manual retries from a dashboard without requiring any code changes or SDK installation. A free tier offering 5,000 webhooks per month is available, aimed at indie developers who need a lightweight safety net rather than a full Redis and queue-based infrastructure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Stripe Acquires AI Gateway OpenRouter in Deal Valued Between $7B and $8B

Stripe agreed to acquire OpenRouter on August 19, 2026, in a deal reported to be worth between $7 billion and $8 billion, paid largely in stock. The acquisition comes just three months after OpenRouter raised $113 million at a $1.3 billion valuation. The deal raises practical concerns for developers who rely on AI gateways, as acquisitions can lead to changes in model identifiers, base URLs, or response structures that break existing integrations silently. Developers are advised to audit their gateway dependencies by checking whether base URLs resolve correctly, whether model catalogues are accessible without authentication, and how the service handles over-tier requests or upstream provider failures. A separate AI gateway company, Helicone, also changed ownership this year and has since entered maintenance mode, underscoring the instability in this infrastructure layer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Trading Experiment Day 35: High-Confidence Bet Placed on Already-Rising Market

An AI trading agent called Afu logged its highest-ever confidence score of 0.70 on Day 35 of a 30-day experiment, predicting the Taiwan Weighted Index would close higher within a range of 48,000 to 48,500. The market had already risen 1.3% when the prediction was recorded at 9:28 a.m., meaning the directional call carried little informational value. The index closed at 47,940, confirming the bullish direction but missing the predicted range by about 60 points. Two prior predictions on ETF 00919 that had already expired remained unreviewed in the trading journal, raising questions about whether the agent's self-scoring mechanism is being consistently applied. The account holds 36 shares of 00919 and 1,089 TWD in cash, with total assets of 2,236 TWD reflecting an 11.8% gain on the original 2,000 TWD principal, with zero trades executed for the second consecutive day.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Object-Oriented Programming Was Born and Shaped Modern Software

Object-oriented programming (OOP) emerged in the 1960s to solve the chaos of large programs where any function could alter any shared data, making bugs difficult to trace and code hard to reuse. Norwegian researchers Ole-Johan Dahl and Kristen Nygaard developed Simula 67 between 1962 and 1967, introducing foundational concepts like classes, objects, inheritance, and virtual methods. Alan Kay later coined the term 'object-oriented' and led the creation of Smalltalk at Xerox PARC, advancing the idea that everything should be an object communicating via messages. Bjarne Stroustrup brought these ideas to mainstream industry with C++ in 1983, while Java in 1995 made class-based OOP the standard for enterprise software. Both Dahl, Nygaard, and Kay were eventually recognised with Turing Awards, cementing OOP as a foundational concept in computer science.

0 comments Read more at DEV Community