diff --git a/docs/app-extensions.md b/docs/app-extensions.md index 8ef194ef75a..29e90ff6abe 100644 --- a/docs/app-extensions.md +++ b/docs/app-extensions.md @@ -3,7 +3,7 @@ id: app-extensions title: App Extensions --- -App extensions let you provide custom functionality and content outside of your main app. There are different types of app extensions on iOS, and they are all covered in the [App Extension Programming Guide](https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/index.html#//apple_ref/doc/uid/TP40014214-CH20-SW1). In this guide, we'll briefly cover how you may take advantage of app extensions on iOS. +App extensions let you provide custom functionality and content outside of your main app. There are different types of app extensions on iOS, and they are all covered in the [App Extension Programming Guide](https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/index.html). In this guide, we'll briefly cover how you may take advantage of app extensions on iOS. ## Memory use in extensions @@ -15,7 +15,7 @@ The memory limit of a Today widget is 16 MB. As it happens, Today widget impleme ![](/docs/assets/TodayWidgetUnableToLoad.jpg) -Always make sure to test your app extensions in a real device, but be aware that this may not be sufficient, especially when dealing with Today widgets. Debug-configured builds are more likely to exceed the memory limits, while release-configured builds don't fail right away. We highly recommend that you use [Xcode's Instruments](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html) to analyze your real world memory usage, as it's very likely that your release-configured build is very close to the 16 MB limit. In situations like these, you can quickly go over the 16 MB limit by performing common operations, such as fetching data from an API. +Always make sure to test your app extensions in a real device, but be aware that this may not be sufficient, especially when dealing with Today widgets. Debug-configured builds are more likely to exceed the memory limits, while release-configured builds don't fail right away. We highly recommend that you use [Xcode's Instruments](https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html) to analyze your real world memory usage, as it's very likely that your release-configured build is very close to the 16 MB limit. In situations like these, you can quickly go over the 16 MB limit by performing common operations, such as fetching data from an API. To experiment with the limits of React Native Today widget implementations, try extending the example project in [react-native-today-widget](https://github.com/matejkriz/react-native-today-widget/). diff --git a/docs/running-on-device.md b/docs/running-on-device.md index a7569e13b3e..f57e35ff6cb 100644 --- a/docs/running-on-device.md +++ b/docs/running-on-device.md @@ -393,7 +393,7 @@ If everything is set up correctly, your device will be listed as the build targe ![](/docs/assets/RunningOnDeviceReady.png) :::note -If you run into any issues, please take a look at Apple's [Launching Your App on a Device](https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/LaunchingYourApponDevices/LaunchingYourApponDevices.html#//apple_ref/doc/uid/TP40012582-CH27-SW4) docs. +If you run into any issues, please take a look at Apple's [Launching Your App on a Device](https://help.apple.com/xcode/mac/current/#/dev60b6fbbc7) docs. :::

Connecting to the development server