--- title: Introducing multi-location updates and more | daily.dev description: New releases of Firebase's Android (2.4.0), iOS (2.4.0), and JavaScript (2.3.0) SDKs add atomic multi-location writes, letting developers update completely... canonical: https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Introducing multi-location updates and more | daily.dev og:description: New releases of Firebase's Android (2.4.0), iOS (2.4.0), and JavaScript (2.3.0) SDKs add atomic multi-location writes, letting developers update completely... og:url: https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr og:image: https://api.daily.dev/og/posts/vFlTdPiSR.png og:image:alt: Introducing multi-location updates and more og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Introducing multi-location updates and more **[Firebase](https://daily.dev/sources/firebase-blog)** · 7 min read · 0 upvotes · 0 comments ## Summary New releases of Firebase's Android (2.4.0), iOS (2.4.0), and JavaScript (2.3.0) SDKs add atomic multi-location writes, letting developers update completely separate database paths in a single atomic operation instead of requiring multiple writes with manual rollback logic. Queries can now also be ordered by deep, nested child paths rather than only direct children. The iOS client adds bitcode support for iOS 9, enabling Apple to re-optimize app binaries and support app thinning. Various bug fixes for memory leaks, cache inconsistencies, and crashes are also included. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I update data in two different locations of the Firebase Realtime Database atomically? As of the Android 2.4.0, iOS 2.4.0, and JavaScript 2.3.0 client releases, Firebase supports atomic multi-location updates by passing an object whose keys are full paths (e.g. 'posts/newPostKey' and 'user/posts/newPostKey') to the update/updateChildValues method on the root reference. Previously this was only possible for direct children of a single node, requiring separate writes with manual rollback logic for cross-location updates. _daily.dev surfaces database release notes like this for developers denormalizing data across services._ ### Can I order a Firebase Realtime Database query by a nested child property instead of a direct child? Yes, starting with Firebase's Android 2.4.0, iOS 2.4.0, and JavaScript 2.3.0 clients, orderByChild (or queryOrderedByChild) accepts a slash-separated deep path such as 'dimensions/height', letting you sort nodes by properties nested several levels down. Previously ordering was limited to direct children only. _Developers restructuring nested data models can track database query capabilities like this on daily.dev._ ### What does bitcode support mean for iOS apps using Firebase? The Firebase iOS client compiled with bitcode support, an iOS 9 feature, lets Apple re-optimize an app's binary in the future without requiring a new App Store submission. This enables smaller app downloads through app thinning and reduces work needed to support future device platforms. _iOS developers weighing SDK upgrades can follow platform-level changes like this via daily.dev._ --- Tags: [#javascript](https://daily.dev/tags/javascript), [#infrastructure](https://daily.dev/tags/infrastructure), [#backend](https://daily.dev/tags/backend), [#ios](https://daily.dev/tags/ios), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Introducing multi-location updates and more","url":"https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr"},"datePublished":"2026-08-23T12:18:14.870Z","dateModified":"2026-08-23T12:32:51.129Z","description":"New releases of Firebase's Android (2.4.0), iOS (2.4.0), and JavaScript (2.3.0) SDKs add atomic multi-location writes, letting developers update completely...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,infrastructure,backend,ios,firebase","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Introducing multi-location updates and more"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-multi-location-updates-and-more-vfltdpisr#faq","mainEntity":[{"@type":"Question","name":"How do I update data in two different locations of the Firebase Realtime Database atomically?","acceptedAnswer":{"@type":"Answer","text":"As of the Android 2.4.0, iOS 2.4.0, and JavaScript 2.3.0 client releases, Firebase supports atomic multi-location updates by passing an object whose keys are full paths (e.g. 'posts/newPostKey' and 'user/posts/newPostKey') to the update/updateChildValues method on the root reference. Previously this was only possible for direct children of a single node, requiring separate writes with manual rollback logic for cross-location updates. daily.dev surfaces database release notes like this for developers denormalizing data across services."}},{"@type":"Question","name":"Can I order a Firebase Realtime Database query by a nested child property instead of a direct child?","acceptedAnswer":{"@type":"Answer","text":"Yes, starting with Firebase's Android 2.4.0, iOS 2.4.0, and JavaScript 2.3.0 clients, orderByChild (or queryOrderedByChild) accepts a slash-separated deep path such as 'dimensions/height', letting you sort nodes by properties nested several levels down. Previously ordering was limited to direct children only. Developers restructuring nested data models can track database query capabilities like this on daily.dev."}},{"@type":"Question","name":"What does bitcode support mean for iOS apps using Firebase?","acceptedAnswer":{"@type":"Answer","text":"The Firebase iOS client compiled with bitcode support, an iOS 9 feature, lets Apple re-optimize an app's binary in the future without requiring a new App Store submission. This enables smaller app downloads through app thinning and reduces work needed to support future device platforms. iOS developers weighing SDK upgrades can follow platform-level changes like this via daily.dev."}}]} ```