Troubleshoot common errors while uploading audio files

While uploading audio files to BrowserStack real Android devices using App Live, you might see the following common errors:

• Audio Injection setup failed
• Audio upload failed
• Audio upload failed. File size exceeded
• Failed to launch the selected Audio Injection enabled device

Audio Injection setup failed

After you select your device, the setup fails and the following error is displayed:

Resolution/Workaround

Try launching the session again. If it fails again, contact support.

Audio upload failed

When you are trying to upload an audio file, the upload fails and the following error is displayed:

Resolution/Workaround

1. Check your internet connection.
2. Ensure that the audio file you are trying to upload is of the .aac, .mp3, .ogg, .wav, or .wma formats.
3. Ensure that the file size is not more than 15 MB for .aac, .mp3, .ogg, or .wma files, and 100 MB for .wav files.
4. If you have confirmed steps 1 to 3 and your audio upload still fails, then use the following API to upload the audio file from your command line:

   curl -u "YOUR USERNAME:ACCESS_KEY" \
   -X POST "https://api-cloud.browserstack.com/app-live/upload-media" \
   -F "file=@/path/to/media/file/audio.wav" \
   -F "custom_id=SampleMedia"
   

   In the above API, file refers to the audio file to be uploaded, and custom_id refers to the custom ID for the audio file.
   

If your audio upload still fails after completing steps 1 to 4, contact support.

Audio upload failed. File size exceeded.

When you are trying to upload an audio file that exceeds the supported file size, the upload fails.

Resolution/Workaround

1. Ensure that the size of the audio file that you are uploading does not exceed 15 MB for .aac, .mp3, .ogg, or .wma files, and 100 MB for .wav files.
2. Try uploading the file again.

Failed to launch the selected Audio Injection enabled device

After you select an audio upload enabled device, the device launch fails.

Cause

The audio upload enabled devices are already in use.

Resolution/Workaround

Try launching your test session again after some time.