Maybe this is a weird question, but why did my firebase realtime database changed the interface? Yesterday i still using the same old interface for realtime database, but today the interface changed and become abit laggy. I try searched on internet about this issue but dont have any answers.
Previous database:
Current database interface:
Does anyone know the caused of this issue? and how to solve it? I want to revert back to previous interface
firebaser here
We recently updated the user interface for the Realtime Database in the Firebase console. There is no way to revert it back to the old interface, nor should that be needed. If you find that certain features are missing or bugs have been introduced in the new user interface, please file a file a bug report or feature request or on the firebase-talk mailing list.
You cannot configure the UI in Firebase console. If you have any feedback on the new interface then can share that with Firebase support.
Related
I'm about to make an iOS app for a company that will need to access an already existing database table on SQL Server. All I want to do is make a connection to the already existing database table and compare it to a data item within the app - but I cant figure out how to create this connection using Objective-C. All of the information I've found deals with making a database yourself using sqlite and then importing the table data into the sqlLite database, but I've already got a live database on SQLServer I need to connect to.
this question: ios app: How to efficiently use an existing database was very similar to mine and had no resolution.
this one is also similar: Xcode connect to the MS SQL database it suggests to use a webservice - but I'm using Objective-c - will there be an issue getting my Objective-c code to communicate with the webservice?
I'd really like to do it without a webservice but it doesn't seem like an option.
I keep reading about RESTFULapi's but there is absolutely no documentation that I can found that will explain how to perform anything similar to what I'm talking about (feel free to point me to the resource if you disagree)
Any recommendations would be appreciated
I'd like to build a simple iOS only app that's going to be social. I don't yet have a way to monetize this app, so I'd like to keep this project as cheap as possible. Since it's iOS only, I figured I would use CloudKit because of its very generous free tier. However, if I ever decided to make this a cross platform app, would I be able to migrate my user data somewhere else?
I think you can use CloudKit with Android because of the CloudKit JS implementation. The real problem is, that I think that also the android user needs an iCloud Account do something with that.
So maybe the better way is to use google firebase.
https://firebase.google.com
As of December 2019, there is no simple way to migrate data from CloudKit. The data stored in each user's private data base is not accessible by the developer.
There is always the option to do this inside of the app for each individual user. If the data is not too large and complicated it should be easily done.
But make sure to inform the user and give them a choice to move or don't move the data. Let both services run for some time parallel before removing the cloudkit option for old users completely. Obviously moving data using the app can cause certain issues if the move doesn't go as planned.
I am developing one chat application but some confuse regarding database. I have no idea about how to expand core data module that provided by XMPPFramework(iOS) and in application i need some database changes like message count etc.. so realm database is good option store my all message, rooster ,groups and other chat related setting ?
Current scenario
Used default database that provided by XMPPFramework
Do't find any solution for how to extend XMPPFramework database.
Dev Tools
ejabberd server used in backend.
Xcode 8.3.3(Swift 3.0)
let me know your good suggestion regarding database and other points.
Before I delete an application, I want to be asked for:
Do you want to delete also the application data?
as we know it from other applications. I searched for it but I don't found any clue. It is related to CoreData.
Do you know how I can achieve this?
Thanks for any help!
When your application is deleted, its associated data will be as well.
You can instead offer to persist it to an external resource (Firebase, Azure, etc.). Then, it can be available at a later date. However, you must do this prior to deletion, as there is no way for your app to know it is being deleted & respond to it.
This may be too simple of a question for SO, but for those that have used both Cloudkit/Core Data, do you have to migrate data in Cloudkit similar to Core Data if you make any changes to the database itself?
For example, if you adjust your Core Data model at all, you have to go through a migration process in order to make sure the App still works appropriately. Is Cloudkit the same way?
From my understanding there is no migration process necessary (judging when I make changes and run them in the simulator just fine), but I want to confirm before I upload to the App Store. Thanks for any help!
This is covered in detail in the Deploying the Schema section of the CloudKit Quick Start.
The quick summary is that you do need to push changes to production using the CloudKit Dashboard. But keep in mind that you can only make limited schema changes so plan ahead well. You can add new fields. You can add new record types. You can't delete anything.
Keep in mind that users of your app will be using old versions as well as new versions. The latest version of the app will of course know about any new additions to the schema. Old versions of the app won't know about the new fields and record types.