[codex] Fix Firebase initialization lifecycle hook#269
Merged
Conversation
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
1 participant
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.
What changed
javax.annotation.PostConstructtojakarta.annotation.PostConstruct.Why
The production container has the Firebase service account mounted correctly and
firebase.service-account.pathconfigured, but scheduled push notifications fail with:This indicates the initializer method is not being invoked before
FirebaseMessaging.getInstance()is used. On Spring Boot 3 / Spring 6, lifecycle annotations should use the Jakarta namespace.Impact
The default Firebase app should be initialized during Spring startup, allowing scheduled Firebase push notifications to send normally.
Validation
./gradlew compileJavapasses.Post-deploy check
Look for this line in container startup logs: