# Troubleshooting Initialization

Troubleshoot common initialization issues and apply solutions.

When following steps in [Getting Started](https://www.airship.com/docs/developer/sdk-integration/flutter/installation/getting-started/) or [Advanced Configuration](https://www.airship.com/docs/developer/sdk-integration/flutter/installation/advanced-configuration/), if you don't see a channel ID in the logs or encounter errors during initialization, review the following common problems and solutions.

## Installation Errors

If you encounter errors during installation:

- Verify that you're using a compatible version of Flutter. See [Requirements](https://www.airship.com/docs/developer/sdk-integration/flutter/installation/getting-started/#requirements) in *Getting Started*.
- Ensure all native dependencies are properly linked.
- Run `flutter clean` and `flutter pub get` to refresh dependencies.
- For iOS, run `pod install` in the `ios` directory.
- Check that your iOS and Android projects are correctly configured.

## Initialization Errors

If you encounter errors during SDK initialization:

- Verify your credentials in the Airship dashboard. The credentials used by `takeOff` are your Airship project's [App Key](https://www.airship.com/docs/reference/glossary/#app_key) and [App Secret](https://www.airship.com/docs/reference/glossary/#app_secret). To find them, select the dropdown menu () next to your project name, and then **Project details**.
- Ensure `WidgetsFlutterBinding.ensureInitialized()` runs first in `main()`, then `Airship.takeOff`, then `runApp()`.
- Ensure `site` in your `AirshipConfig` is `Site.us` for US cloud projects or `Site.eu` for EU cloud projects.