SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

How a Mixed Expo SDK 54/55 Package Mismatch Broke an Android Build

0
·7 views

A developer's Android build failed after several Expo packages were individually upgraded to SDK 55-compatible versions while the core Expo SDK remained on version 54. The version mismatch went undetected because TypeScript checks passed and the development server ran normally, only surfacing during the native build step in EAS Build. Expo package version numbers do not directly mirror SDK numbers, making manual inspection of package.json unreliable for confirming compatibility. Running 'npx expo install --check' and 'npx expo-doctor' identified the mismatched packages, allowing the developer to downgrade them to the correct SDK 54-compatible versions. The developer now uses 'npx expo install' when adding managed packages and runs compatibility checks before every EAS Build to prevent similar issues.

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
ProgrammingHacker News ·

BMW Displays Full-Screen Ads on In-Car Dashboard Screens

BMW has begun showing full-screen advertisements on the main dashboard display of its vehicles. The ads have appeared on the central infotainment screen, which drivers typically rely on for navigation and vehicle controls. A Spider-Man promotional ad was among the examples documented and reported via a consumer rights wiki. The practice has drawn attention and criticism from car owners and online communities concerned about distraction and user experience. This raises broader questions about automakers monetising in-car screens through third-party advertising.

0 comments Read more at Hacker News
0
ProgrammingDEV Community ·

DocFence 0.1.0 Brings CI Pipeline Checks to Word Document Reviews

DocFence 0.1.0 is a newly released open-source tool designed to apply continuous integration boundaries to Microsoft Word document reviews. The tool inspects .docx and .docm files by analyzing stored OOXML content rather than Word's rendered output, covering elements such as macros, custom XML, hidden text, and unresolved revisions. Users define review policies through a short YAML configuration file, and the tool exits with a nonzero code when a violation is detected, with SARIF output supported for integration into CI pipelines. DocFence is installable via pip from its GitHub releases page and offers commands for diffing documents and running policy checks. The project is MIT-licensed and publicly available on GitHub.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer shares five hard lessons building a GPU-free, on-premise RAG system for public sector

A developer working on public sector health information systems built a fully on-premise retrieval-augmented generation (RAG) stack that runs on CPU-only Windows Server hardware without Docker or cloud access. The open-source system uses ASP.NET Core 9, Ollama, Qdrant, Mistral 7B, and a Python ingest pipeline to process and query PDF, Word, and Excel documents locally. The project was motivated by strict institutional data-residency requirements common in healthcare and government environments, where modern AI infrastructure assumptions rarely apply. During deployment, the developer encountered five significant issues not covered in standard RAG tutorials, including gRPC incompatibility with HTTP/1.1-only corporate networks, which required bypassing the official Qdrant .NET SDK in favour of direct REST API calls. The field report is intended to help others facing similar legacy enterprise constraints where GPU access and cloud connectivity cannot be taken for granted.

0 comments Read more at DEV Community