Explain localization for permission usage descriptions that are set with config plugins
See original GitHub issueSummary
Some parts of the documentation refers to specifying locales in app.json example:
"locales": {
"en": "./languages/en/translation.json",
"no": "./languages/nb/translation.json"
},
but most of the expo plugins seem to rely on these strings being set by config plugins, but also refer to the PList variable names like “NSUserTrackingUsageDescription” for example expo-tracking-transparency and many others:
{
"expo": {
"plugins": [
[
"expo-tracking-transparency",
{
"userTrackingPermission": "This identifier will be used to deliver personalized ads to you."
}
]
]
}
}
this makes it very unclear if it is even possible to provide localisation for them, and how one should do that.
Reading the source code for the example expo-tracking-transparency package make it seems that it will not care about localisation files at all and just use the default if not set explicitly in the config plugin configuration.
Link to the related docs page
https://docs.expo.dev/versions/latest/sdk/tracking-transparency/
Anything else?
I’ll happily submit pull requests for both fixing underlying issues if the implementation is lacking, and update the documentation if I get some clear explanation/examples for how this should be solved
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (8 by maintainers)
Still there my friend
Regarding this, I can’t understand why we have to provide both times the same text. If you check here: https://docs.expo.dev/versions/latest/sdk/tracking-transparency/ you could see that it ask you to provide the text here:
But then at the end we can see it again here, where it ask to add the key inside the
infoPlist
object:Not sure if any of both is deprecated, or both are working, of if I should provide only 1, or what. Confusing.