I think there might have been some confusion regarding terminology, sorry.
Firebase lets you create a project, which can contain multiple applications (Android, iOS, web, etc.). Currently, resources (such as Storage and the Database) are project wide--all applications access the same database and storage bucket (as configured in the GoogleServices-Info.plist). In order to get multiple databases, you'll need multiple projects (this is also something we're actively working on). It also means that since we're currently
Given the you can create two Firebase Projects, each with a database, and use the code above to connect to those databases within the same iOS or OSX application, it sounds to me like this is what the OP asked for (though this may have been conflated with the question of: "can you put two database URLs in the same plist (thus the same project) and reference them both," to which the answer would be no).
It's also worth noting that we haven't deprecated the 2.x OSX libraries--they'll work fine with the existing Realtime Database and Auth system. You can have an iOS app on the 3.x SDK and an OSX app on 2.x. You can still use the
FirebaseOSX pod with the old configuration and things will still work moving forward. While it's true that you won't get access to the latest features yet, it won't break existing apps and it's even fine for new development (even though I agree that there is uncertainty with this route).
Sorry for the confusion, hopefully this helps clear things up. I'll add some comments to the other thread on
Thanks,
--Mike