EAS 4 KiB file limit forces smarter multi-environment config for Expo apps

·2 views

A developer building CannyCart, a voice-first shopping app using Amplify Gen 2 and Expo, hit a hard 4 KiB ceiling when trying to use EAS environment variables to deliver backend config files to different build profiles. The file in question, amplify_outputs.json, exceeded the limit at 4.5 KB because it embeds a full model_introspection schema that grows with every data model added. Unlike web builds on Amplify Hosting, EAS mobile builds run on Expo's servers without AWS credentials, meaning the config cannot be regenerated at build time and must be committed to the repository in advance. The developer resolved this by committing one amplify_outputs.json per environment and using an eas-build-pre-install hook to copy the correct file into place based on the active build profile. The workaround highlights a structural asymmetry between web and mobile CI pipelines when using Amplify Gen 2 backends.

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)

How a Five-Page Audit Turns Accessibility Scan Results into Actionable Tasks

Automated accessibility scans generate raw data that often mixes repeated component issues with isolated page defects, making remediation planning difficult. A structured five-page triage process helps teams cut through that noise by selecting pages that represent distinct templates and user journeys, such as a home page, a form, a listing page, and an error or support state. Each selected page should be tested with both automated tools and a manual checklist covering keyboard access, focus visibility, form labels, contrast, and dynamic state changes. Findings are then grouped by likely implementation boundary — such as a shared component or page-specific defect — so engineers can fix a root cause once and retest across all affected pages. Issues are prioritized by combining severity with reach, ensuring that a moderate defect in a widely reused component is addressed before an isolated low-impact problem.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

n8n Microsoft Teams Node Enables Automated Messaging, Channel and Task Management

A detailed guide published on DEV Community explains how to use the n8n Microsoft Teams node to automate enterprise communication workflows. The node connects to Microsoft Teams via the Microsoft Graph API, supporting operations such as creating and deleting channels, sending messages, and managing Planner tasks. Authentication is handled through OAuth2, requiring a one-time Azure Active Directory app registration with specific Microsoft Graph permissions. Common use cases outlined include routing Jira tickets to channels, sending Stripe payment failure alerts, and posting scheduled digest reports. The guide also provides free, importable workflow JSON templates to help teams deploy these automations quickly.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Study Identifies Key Factors Behind Software Delivery Inefficiency

A research paper published via ACM Digital Library examines the root causes of inefficiency in software delivery processes. The study explores the various drivers that slow down or hinder how software teams ship and deploy their work. It was shared on Hacker News, where it received limited early engagement. The research aims to help organizations better understand and address bottlenecks in their development pipelines.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How a Model Fallback Chain Rescued an AI Agent From a 3 AM Outage

A developer's OpenClaw AI agent stalled for 33 minutes at 2:44 AM after its primary model, Claude, began returning 503 errors. The agent eventually recovered on its own using a configured fallback chain that sequentially tried GPT-4o and Gemini when the primary provider failed. The prolonged outage was not caused by the fallback mechanism itself, but by misconfigured retry settings — specifically a 5-second retry delay with five retry attempts per model, causing excessive wait times. Adjusting maxRetries to 2 and retryDelayMs to 1000 significantly reduced the detection-to-recovery window. The developer also recommends monitoring fallback log events and setting up alerts to identify when a primary model is becoming unreliable.

0 comments Read more at DEV Community