Increase initOrder of content provider #57
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
`android:initOrder` provides the order in which the content provider should be instantiated, relative to other content providers hosted by the same process. When there are dependencies among content providers, setting this attribute for each of them ensures that they are created in the order required by those dependencies. The value is a simple integer, with higher numbers being initialized first. Source https://developer.android.com/guide/topics/manifest/provider-element With Firebase setting [100 as `initOrder`](https://github.com/firebase/firebase-android-sdk/blob/c56a9769b723bb96551ed2aa9fd3731e541ca018/firebase-common/src/main/AndroidManifest.xml#L28), we can use 200 here to run earlier in the process.
oblador
approved these changes
Oct 27, 2021
r0h0gg6
pushed a commit
to r0h0gg6/react-native-performance
that referenced
this pull request
Jul 27, 2025
`android:initOrder` provides the order in which the content provider should be instantiated, relative to other content providers hosted by the same process. When there are dependencies among content providers, setting this attribute for each of them ensures that they are created in the order required by those dependencies. The value is a simple integer, with higher numbers being initialized first. Source https://developer.android.com/guide/topics/manifest/provider-element With Firebase setting [100 as `initOrder`](https://github.com/firebase/firebase-android-sdk/blob/c56a9769b723bb96551ed2aa9fd3731e541ca018/firebase-common/src/main/AndroidManifest.xml#L28), we can use 200 here to run earlier in the process.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
android:initOrderprovides the order in which the content provider should be instantiated, relative to other content providers hosted by the same process. When there are dependencies among content providers, setting this attribute for each of them ensures that they are created in the order required by those dependencies. The value is a simple integer, with higher numbers being initialized first. Source https://developer.android.com/guide/topics/manifest/provider-elementWith Firebase setting 100 as
initOrder, we can use 200 here to run earlier in the process.