Access to iOS app settings errors and troubleshooting

While accessing app settings to test your iOS app on BrowserStack real devices using App Live, you may see the following common errors:

• App Settings does not display your app name
• App Settings does not display your app name as it is not a supported app
• App Settings fails to launch or crashes

App Settings does not display your app name

When you try to access app settings using iOS Settings on the App Live toolbar, the name of your app is not displayed in the App Settings section, and you see the following message:
This feature is only available on apps with Settings.bundle in their package.

Resolution/Workaround:

1. Stop your ongoing test session on App Live.
2. Ensure that the app you are uploading has a Settings bundle, and upload your app again.
3. Select your device from the device listing to launch your test session.
4. Click iOS Settings on the App Live toolbar to access and modify settings for your app that has a Settings bundle.

App Settings does not display your app name as it is not a supported app

When you try to access app settings using iOS Settings on the App Live toolbar, the name of your app is not displayed in the App Settings section, and you see the following message:
This feature is not compatible with apps installed through App Store or TestFlight.

Resolution/Workaround

• Ensure that the app you want to test is uploaded by you or synced with App Center.
  App Live does not support access to app settings for apps installed via App Store or TestFlight.
• Ensure that the app you are uploading has a Settings bundle.

App Settings fails to launch or crashes

After you select your app from App Settings on the iOS Settings prompt, App Settings crashes or fails to launch due to an unspecified reason, and you see the following error:
App Settings launch has failed.

Workaround:

• Check if you have an option named “Settings” in your application settings. This tends to interfere with our implementation. Try renaming this option and attempt to access the setting again. If this does not resolve the issue, contact Support.