Search Issue Tracker

Fixed in 5.3.8



Found in


Issue ID




[iOS] Audio with 'Streaming' Load Type does not play on some devices running iOS 10



If an Audio Clip has its Load Type set to 'Streaming' it does not play on some older devices running iOS 10.

Steps to reproduce:
1) Open the attached project (streamingTest_832578).
2) Build for iOS.
3) Run on a device via Xcode.
4) When the app launches, press any of the UI buttons on the screen.

A sound should be played, however it does not. An error message is displayed in the Xcode's console:
Error: Cannot create FMOD::Sound instance for resource resources.resource, (An error occured that wasn't supposed to. Contact support. )

It does not occur if the Load Type is set to 'Decompress On Load' or 'Compressed In Memory'. This only happens with iOS 10.
It seems that only older devices (like iPhone 5, iPad 4) are affected.

Reproduced on:
5.5.0b4, 5.4.1p1, 5.3.6p5, 5.3.5p6

Did not reproduce:

I was able to reproduce it on iPhone 5, running iOS 10.0.1
Devices running iOS 10 that did not reproduce:
iPhone 6, iPhone 6 Plus, iPad Mini 2, iPhone SE.
Other users reported that this is also reproducible on iPad 4th gen and iPhone 5C.

Comments (49)

  1. firtina

    Dec 12, 2016 14:40

    QA has confirmed that it was indeed fixed in 5.5 as well as the other versions.

  2. firtina

    Dec 03, 2016 21:55

    Looks like it may have been missed from the release notes, I will be notifying the team to get it added in there after confirming myself that it's in

  3. firtina

    Dec 03, 2016 21:44

    It should have been fixed in 5.5 as well as the latest patches for 5.3 and 5.4

  4. jkqs

    Dec 01, 2016 02:16

    The latest 5.5.0f3 version of the release notes, or did not mention repair the bug, 5.3.8 version is not on-line, this bug to my project continued delay

  5. Devil_Inside

    Nov 30, 2016 15:33

    Since I can't find a mention of this fix in the newly released 5.5.0f3 public release, is it safe to assume that the issue is already fixed in that release? Or should I wait for it to come in one of the 5.5 patches later?

  6. grit

    Nov 24, 2016 14:48

    Yay, thank you! :)

  7. firtina

    Nov 24, 2016 13:12

    @GRIT When a bug is marked as "Fixed in Unity 5.3.8" it means it is expected to be in that version, and any version that will be released after it. So in this case, that includes 5.4.4, 5.5.x, 5.6.x, and so on.

    That does not mean it cannot land before! For example in this case; the fix has just arrived in Patch 5.4.3p1 - out now! For 5.3, 5.3.7p2 is the next patch.

    @MATTHEWDOMINEY We do not provide exact dates for patches (various reasons) but we try to keep a consistent schedule. There is a history of the ones that have been released: .

    You can find more information about patch releases on these posts: and

    There will be more blog posts regarding patch releases which should help to clarify things further.

  8. grit

    Nov 24, 2016 10:32

    Sorry, I don't mean to bother.
    But I wonder why this issue is flagged as fixed anyway (and thus voting disabled). I can't find a version 5.3.8 anywhere.
    Maybe because the patch is on the way?
    It would be helpful to know, when it is expected to be available, though, because our current app in the store suffers from this issue. We would like to upload a fixed build as soon as possible and I am not sure if downgrading to Unity 5.3.5 (even possible from 5.4.2?) or finding a workaround instead of waiting for the patch is advisable, because I don't know if the available solution is a matter of days or weeks.
    Thanks in advance.

  9. grit

    Nov 22, 2016 16:54

    Having this problem in version 5.4.2f2.
    Hoping to see the announced patch 5.4.3p1 soon, because I guess the lower available patches (e.g. 5.4.2p4) didn't fix this?

  10. matthew_carnegie

    Nov 22, 2016 14:00

    @FIRTINA when can we expect these patch releases to be available?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.