Skip to content

Commit

Permalink
[docs] add reference to CFBundleAllowMixedLocalizations (#8346)
Browse files Browse the repository at this point in the history
  • Loading branch information
cruzach committed May 19, 2020
1 parent 6d56a66 commit 8b9e3b3
Show file tree
Hide file tree
Showing 7 changed files with 7 additions and 0 deletions.
Expand Up @@ -25,6 +25,7 @@ Beginning with iOS 13, any app that includes third-party authentication options
5. If you chose a different app to be the primary, you'll also need to open up the configuration page for your current app, enable the "Sign In with Apple" capability, click "Edit" and choose the "Group with an existing primary App ID" option. Save this configuration as well.
6. Next, go to the "Keys" page and register a new key. Add the "Sign In with Apple" capability, and make sure to choose the correct primary app on the configuration screen.
7. Finally, when you want to make a standalone build to test with, run `expo build:ios --clear-provisioning-profile --revoke-credentials` so that your provisioning profile is regenerated with the new entitlement.
8. (Optional) If you'd like to localize the button text, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios).

## Usage

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/unversioned/sdk/localization.md
Expand Up @@ -44,6 +44,7 @@ Let's make our app support English and Japanese.

- You may want to refrain from localizing text for certain things, like names. In this case you can define them _once_ in your default language and reuse them with `i18n.fallbacks = true;`.
- When a user changes the device's language, your app will reset. This means you can set the language once, and don't need to update any of your React components to account for the language changes.
- On iOS, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios) so that your app supports the retrieval of localized strings from frameworks.

### Full Demo

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/v35.0.0/sdk/apple-authentication.md
Expand Up @@ -26,6 +26,7 @@ For [managed](../../introduction/managed-vs-bare/#managed-workflow) apps, you'll
5. If you chose a different app to be the primary, you'll also need to open up the configuration page for your current app, enable the "Sign In with Apple" capability, click "Edit" and choose the "Group with an existing primary App ID" option. Save this configuration as well.
6. Next, go to the "Keys" page and register a new key. Add the "Sign In with Apple" capability, and make sure to choose the correct primary app on the configuration screen.
7. Finally, when you want to make a standalone build to test with, run `expo build:ios --clear-provisioning-profile --revoke-credentials` so that your provisioning profile is regenerated with the new entitlement.
8. (Optional) If you'd like to localize the button text, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios).

## Usage

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/v36.0.0/sdk/apple-authentication.md
Expand Up @@ -25,6 +25,7 @@ Beginning with iOS 13, any app that includes third-party authentication options
5. If you chose a different app to be the primary, you'll also need to open up the configuration page for your current app, enable the "Sign In with Apple" capability, click "Edit" and choose the "Group with an existing primary App ID" option. Save this configuration as well.
6. Next, go to the "Keys" page and register a new key. Add the "Sign In with Apple" capability, and make sure to choose the correct primary app on the configuration screen.
7. Finally, when you want to make a standalone build to test with, run `expo build:ios --clear-provisioning-profile --revoke-credentials` so that your provisioning profile is regenerated with the new entitlement.
8. (Optional) If you'd like to localize the button text, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios).

## Usage

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/v36.0.0/sdk/localization.md
Expand Up @@ -44,6 +44,7 @@ Let's make our app support English and Japanese.

- You may want to refrain from localizing text for certain things, like names. In this case you can define them _once_ in your default language and reuse them with `i18n.fallbacks = true;`.
- When a user changes the device's language, your app will reset. This means you can set the language once, and don't need to update any of your React components to account for the language changes.
- On iOS, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios) so that your app supports the retrieval of localized strings from frameworks.

### Full Demo

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/v37.0.0/sdk/apple-authentication.md
Expand Up @@ -25,6 +25,7 @@ Beginning with iOS 13, any app that includes third-party authentication options
5. If you chose a different app to be the primary, you'll also need to open up the configuration page for your current app, enable the "Sign In with Apple" capability, click "Edit" and choose the "Group with an existing primary App ID" option. Save this configuration as well.
6. Next, go to the "Keys" page and register a new key. Add the "Sign In with Apple" capability, and make sure to choose the correct primary app on the configuration screen.
7. Finally, when you want to make a standalone build to test with, run `expo build:ios --clear-provisioning-profile --revoke-credentials` so that your provisioning profile is regenerated with the new entitlement.
8. (Optional) If you'd like to localize the button text, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios).

## Usage

Expand Down
1 change: 1 addition & 0 deletions docs/pages/versions/v37.0.0/sdk/localization.md
Expand Up @@ -44,6 +44,7 @@ Let's make our app support English and Japanese.

- You may want to refrain from localizing text for certain things, like names. In this case you can define them _once_ in your default language and reuse them with `i18n.fallbacks = true;`.
- When a user changes the device's language, your app will reset. This means you can set the language once, and don't need to update any of your React components to account for the language changes.
- On iOS, you can add `"CFBundleAllowMixedLocalizations": true` to your `ios.infoPlist` property [in your app.json](https://docs.expo.io/workflow/configuration/#ios) so that your app supports the retrieval of localized strings from frameworks.

### Full Demo

Expand Down

0 comments on commit 8b9e3b3

Please sign in to comment.