getApp

public @NonNull FirebaseApp getApp()

Returns the FirebaseApp instance to which this FirebaseDatabase belongs.

goOffline

public void goOffline()

Shuts down our connection to the Firebase Database backend until goOnline is called.

goOnline

public void goOnline()

Resumes our connection to the Firebase Database backend after a previous goOffline call.

purgeOutstandingWrites

public void purgeOutstandingWrites()

The Firebase Database client automatically queues writes and sends them to the server at the earliest opportunity, depending on network connectivity. In some cases (e.g. offline usage) there may be a large number of writes waiting to be sent. Calling this method will purge all outstanding writes so they are abandoned.

All writes will be purged, including transactions and onDisconnect writes. The writes will be rolled back locally, perhaps triggering events for affected event listeners, and the client will not (re-)send them to the Firebase backend.

setLogLevel

synchronized public void setLogLevel(@NonNull Logger.Level logLevel)

By default, this is set to INFO. This includes any internal errors (ERROR) and any security debug messages (INFO) that the client receives. Set to DEBUG to turn on the diagnostic logging, and NONE to disable all logging.

setPersistenceCacheSizeBytes

synchronized public void setPersistenceCacheSizeBytes(long cacheSizeInBytes)

By default Firebase Database will use up to 10MB of disk space to cache data. If the cache grows beyond this size, Firebase Database will start removing data that hasn't been recently used. If you find that your application caches too little or too much data, call this method to change the cache size. This method must be called before creating your first Database reference and only needs to be called once per application.

Note that the specified cache size is only an approximation and the size on disk may temporarily exceed it at times. Cache sizes smaller than 1 MB or greater than 100 MB are not supported.

setPersistenceEnabled

synchronized public void setPersistenceEnabled(boolean isEnabled)

The Firebase Database client will cache synchronized data and keep track of all writes you've initiated while your application is running. It seamlessly handles intermittent network connections and re-sends write operations when the network connection is restored.

However by default your write operations and cached data are only stored in-memory and will be lost when your app restarts. By setting this value to `true`, the data will be persisted to on-device (disk) storage and will thus be available again when the app is restarted (even when there is no network connectivity at that time). Note that this method must be called before creating your first Database reference and only needs to be called once per application.

useEmulator

public void useEmulator(@NonNull String host, int port)

Modifies this FirebaseDatabase instance to communicate with the Realtime Database emulator.

Note: Call this method before using the instance to do any database operations.