Mixing
Downside to calling FirebaseApp.initializeApp more than once?
Just a simple question today. Is there a downside to calling FirebaseApp.initializeApp twice?
We use the urban airship sdk which handles the init but we noticed some crashes coming in from background services because FirebaseApp.initializeApp was not called.
My solution is to put FirebaseApp.initializeApp in our application class. Just want to make sure this won't cause any issues with an SDK making the same call.
Thanks in advance!
android firebase urbanairship.com asked Jan 2 at 20:11
Psest328Psest328
3,14953363
add a comment |
Just a simple question today. Is there a downside to calling FirebaseApp.initializeApp twice?
We use the urban airship sdk which handles the init but we noticed some crashes coming in from background services because FirebaseApp.initializeApp was not called.
My solution is to put FirebaseApp.initializeApp in our application class. Just want to make sure this won't cause any issues with an SDK making the same call.
Thanks in advance!
android firebase urbanairship.com asked Jan 2 at 20:11
Psest328Psest328
3,14953363
add a comment |
Just a simple question today. Is there a downside to calling FirebaseApp.initializeApp twice?
We use the urban airship sdk which handles the init but we noticed some crashes coming in from background services because FirebaseApp.initializeApp was not called.
My solution is to put FirebaseApp.initializeApp in our application class. Just want to make sure this won't cause any issues with an SDK making the same call.
Thanks in advance!
android firebase urbanairship.com asked Jan 2 at 20:11
Psest328Psest328
3,14953363
Just a simple question today. Is there a downside to calling FirebaseApp.initializeApp twice?
We use the urban airship sdk which handles the init but we noticed some crashes coming in from background services because FirebaseApp.initializeApp was not called.
My solution is to put FirebaseApp.initializeApp in our application class. Just want to make sure this won't cause any issues with an SDK making the same call.
Thanks in advance!
android firebase urbanairship.com android firebase urbanairship.com asked Jan 2 at 20:11
Psest328Psest328
3,14953363
asked Jan 2 at 20:11
Psest328Psest328
3,14953363
asked Jan 2 at 20:11
Psest328Psest328
3,14953363
asked Jan 2 at 20:11
Psest328Psest328
3,14953363
asked Jan 2 at 20:11
Psest328Psest328
3,14953363
3,14953363
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can see what FirebaseApp.initializeApp does by command- or control-clicking into its implementation in Android Studio:
public static FirebaseApp initializeApp(Context context) {
Object var1 = LOCK;
synchronized(LOCK) {
if (INSTANCES.containsKey("[DEFAULT]")) {
return getInstance();
} else {
FirebaseOptions firebaseOptions = FirebaseOptions.fromResource(context);
if (firebaseOptions == null) {
Log.d("FirebaseApp", "Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.");
return null;
} else {
return initializeApp(context, firebaseOptions);
}
}
}
}
As you can see, if the default app was previously initialized, its instance is returned, and nothing else happens. So, if there is a downside, it's that you've just done unnecessary work.
But you shouldn't ever have to call it manually if you performed the standard integration, as it will be invoked automatically a startup via a ContentProvider that will initialize before any other Activity or Service. You can read more about that in this blog.
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
add a comment |
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54012556%2fdownside-to-calling-firebaseapp-initializeapp-more-than-once%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can see what FirebaseApp.initializeApp does by command- or control-clicking into its implementation in Android Studio:
public static FirebaseApp initializeApp(Context context) {
Object var1 = LOCK;
synchronized(LOCK) {
if (INSTANCES.containsKey("[DEFAULT]")) {
return getInstance();
} else {
FirebaseOptions firebaseOptions = FirebaseOptions.fromResource(context);
if (firebaseOptions == null) {
Log.d("FirebaseApp", "Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.");
return null;
} else {
return initializeApp(context, firebaseOptions);
}
}
}
}
As you can see, if the default app was previously initialized, its instance is returned, and nothing else happens. So, if there is a downside, it's that you've just done unnecessary work.
But you shouldn't ever have to call it manually if you performed the standard integration, as it will be invoked automatically a startup via a ContentProvider that will initialize before any other Activity or Service. You can read more about that in this blog.
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
add a comment |
You can see what FirebaseApp.initializeApp does by command- or control-clicking into its implementation in Android Studio:
public static FirebaseApp initializeApp(Context context) {
Object var1 = LOCK;
synchronized(LOCK) {
if (INSTANCES.containsKey("[DEFAULT]")) {
return getInstance();
} else {
FirebaseOptions firebaseOptions = FirebaseOptions.fromResource(context);
if (firebaseOptions == null) {
Log.d("FirebaseApp", "Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.");
return null;
} else {
return initializeApp(context, firebaseOptions);
}
}
}
}
As you can see, if the default app was previously initialized, its instance is returned, and nothing else happens. So, if there is a downside, it's that you've just done unnecessary work.
But you shouldn't ever have to call it manually if you performed the standard integration, as it will be invoked automatically a startup via a ContentProvider that will initialize before any other Activity or Service. You can read more about that in this blog.
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
add a comment |
You can see what FirebaseApp.initializeApp does by command- or control-clicking into its implementation in Android Studio:
public static FirebaseApp initializeApp(Context context) {
Object var1 = LOCK;
synchronized(LOCK) {
if (INSTANCES.containsKey("[DEFAULT]")) {
return getInstance();
} else {
FirebaseOptions firebaseOptions = FirebaseOptions.fromResource(context);
if (firebaseOptions == null) {
Log.d("FirebaseApp", "Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.");
return null;
} else {
return initializeApp(context, firebaseOptions);
}
}
}
}
As you can see, if the default app was previously initialized, its instance is returned, and nothing else happens. So, if there is a downside, it's that you've just done unnecessary work.
But you shouldn't ever have to call it manually if you performed the standard integration, as it will be invoked automatically a startup via a ContentProvider that will initialize before any other Activity or Service. You can read more about that in this blog.
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
You can see what FirebaseApp.initializeApp does by command- or control-clicking into its implementation in Android Studio:
public static FirebaseApp initializeApp(Context context) {
Object var1 = LOCK;
synchronized(LOCK) {
if (INSTANCES.containsKey("[DEFAULT]")) {
return getInstance();
} else {
FirebaseOptions firebaseOptions = FirebaseOptions.fromResource(context);
if (firebaseOptions == null) {
Log.d("FirebaseApp", "Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.");
return null;
} else {
return initializeApp(context, firebaseOptions);
}
}
}
}
As you can see, if the default app was previously initialized, its instance is returned, and nothing else happens. So, if there is a downside, it's that you've just done unnecessary work.
But you shouldn't ever have to call it manually if you performed the standard integration, as it will be invoked automatically a startup via a ContentProvider that will initialize before any other Activity or Service. You can read more about that in this blog.
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
answered Jan 2 at 20:36
Doug StevensonDoug Stevenson
83k1099117
83k1099117
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54012556%2fdownside-to-calling-firebaseapp-initializeapp-more-than-once%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
