# Source Context | Sentry for tvOS

If Sentry has access to your application's source code, it can show snippets of code (*source context*) around the location of stack frames, which helps to quickly pinpoint problematic code.

For example, here's a stack trace from a Swift application. The source context contains the original Swift source code of the application, with the location of the frame highlighted.

[![Screenshot of stack trace showing source context.](https://docs.sentry.io/_next/image/?url=%2Fmdx-images%2Fsource-context-screenshot-SL4JJNKN.png%231141x619\&w=3840\&q=75)](https://docs.sentry.io/mdx-images/source-context-screenshot-SL4JJNKN.png)

### [Source Bundles](https://docs.sentry.io/.md#source-bundles)

Certain SDKs, such as the Python SDK, can resolve this source context automatically, because they have access to unobfuscated source code at runtime. By contrast, to get source context for compiled applications, the source code needs to be uploaded alongside the debug information files. The recommended way to do this is by using `sentry-cli`. See [Creating Source Bundles](https://docs.sentry.io/cli/dif.md#creating-source-bundles) for more information.

To get source context for your Apple project, follow the instructions in the [Uploading Debug Symbols](https://docs.sentry.io/platforms/apple/sourcecontext.md) guide.

After they've been uploaded you can review and manage source bundles the same as any other debug information file. See [Managing Debug Information Files](https://docs.sentry.io/.md#managing-debug-information-files). Source bundles will be tagged with `sources`, and will carry the same filename as the respective debug information file they were created from.
