question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Explain localization for permission usage descriptions that are set with config plugins

See original GitHub issue

Summary

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:open
  • Created 2 years ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
BrodaNoelcommented, May 23, 2022

Still there my friend

1reaction
BrodaNoelcommented, Feb 22, 2022

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:

{
  "expo": {
    "plugins": [
      [
        "expo-tracking-transparency",
        {
          "userTrackingPermission": "This identifier will be used to deliver personalized ads to you."
        }
      ]
    ]
  }
}

But then at the end we can see it again here, where it ask to add the key inside the infoPlist object:

Screen Shot 2022-02-22 at 16 20 39

Not sure if any of both is deprecated, or both are working, of if I should provide only 1, or what. Confusing.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Explain localization for permission usage descriptions that are set ...
Explain localization for permission usage descriptions that are set with config plugins · Run details · Usage · Workflow file.
Read more >
NSUserTrackingUsageDescription - Apple Developer
NSUserTrackingUsageDescription. A message that informs the user why an app is requesting permission to use data for tracking the user or the device....
Read more >
Configuring iOS | Capacitor Documentation
iOS permissions do not need to be specified explicitly like they are in Android. However, iOS requires "Usage Descriptions" to be defined in...
Read more >
Define a custom app permission - Android Developers
Custom permission recommendations​​ You can define custom permissions for your apps and request custom permissions from other apps by defining <uses-permission> ...
Read more >
iOS 10 and Permissions localization description - Stack Overflow
4 Answers 4 · create a new file named "InfoPlist. · click on your project to open settings (if target is your app,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found