Use java package name for loading BuildConfig #751
Merged
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.
Platforms affected
Android
Motivation and Context
Resolving
BuildConfig
using android package name (Context.getPackageName
) will only work when java and android package names are the same.Android package name is effectively its
applicationId
which does not have to match java package name.A common practice is to use different android package names for different built variants/flavours, ie:
Now the applicationId (and android package name) might be something like
com.example.debug
, butBuildConfig
will still resolve bycom.example.BuildConfig
instead ofcom.example.debug.ClassName
This pull request resolves issue #513.
Description
Now using
java.lang.Class.getPackage()
instead ofandroid.content.Context.getPackageName()
Testing
Tested with and without
applicationIdSuffix
with single Android 9 device.Checklist
(platform)
if this change only applies to one platform (e.g.(android)
)