feat: Add Native Firebase Remote Config Support (Android & iOS)#37
Closed
egiray wants to merge 13 commits into
Closed
feat: Add Native Firebase Remote Config Support (Android & iOS)#37egiray wants to merge 13 commits into
egiray wants to merge 13 commits into
Conversation
- FirebaseRemoteConfigPlugin.kt: fetch_and_activate, typed getters (string/int/float/bool/dictionary), set_defaults, throttle detection, real-time listener via addOnConfigUpdateListener - export_plugin.gd: enable_remote_config option + AAR bundling - Full Gradle build setup mirroring existing module structure
task.result on Android returns a Boolean: true means new values were fetched from the server, false means cached values were returned. Map this to FETCH_CACHED (1) instead of treating both as FETCH_SUCCESS (0). Updated enum to match iOS FIRRemoteConfigFetchAndActivateStatus: SUCCESS=0, CACHED=1, FAILURE=2, THROTTLED=3
…nfig plugin - Add initialize() method matching upstream plugin pattern; Remote Config now requires explicit init after FirebaseCore, preventing crashes when google-services.json is missing or misconfigured - Store ConfigUpdateListenerRegistration and expose remove_config_update_listener() - Fix get_string to use VALUE_SOURCE_STATIC check like all other getters - Add remote_config_initialized signal
…sons Missing error signal meant GDScript had no way to know why initialize() failed or when the real-time listener died. Now emits error codes matching the pattern used by Analytics and Messaging plugins.
…heck This signal is iOS-only (APN = Apple Push Notifications). Connecting it unconditionally on Android throws a script error that halts plugin initialization for all subsequent plugins in the same function.
Crashlytics requires the com.google.firebase.crashlytics Gradle plugin to be applied at build time so it can inject a build UUID into the APK. Without it the app crashes at launch with 'The Crashlytics build ID is missing'. The export plugin now patches settings.gradle and build.gradle automatically when firebase/enable_crashlytics is true, so users do not have to edit the Android build template manually.
…aging, and Crashlytics infrastructure
…ng native success signals
Contributor
|
When you finish, add a message here The gradle |
|
Sounds good. This fix #32 |
Contributor
Author
|
I am closing this PR. Since I've updated and made a bigger PR: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements native Firebase Remote Config support for both Android and iOS. This is a key milestone in our modernization roadmap for the
godotx-firebaseextension, focusing on providing a production-grade, feature-complete native SDK for Godot 4.6+.Key Features
addOnConfigUpdateListener(Android) andaddOnConfigUpdateListener(iOS) to react to config changes without polling.get_dictionary().Implementation Details
RemoteConfigViewto the Test Harness for real-time verification of fetch/activate cycles.Dependencies & Context
Important
This PR is part of a layered contribution stack. It is built on top of:
It is recommended to merge #34 and #36 sequentially before this PR, as this branch includes the necessary infrastructure from both.
Full Roadmap
This contribution is structured in five modular phases:
datapayload dictionary.Testing Performed