Hi, I know we’re still 3 months away from iOS 26 release but would be nice to know if the team is prepping to support it, so that we can be guranteed our apps will run on the new iOS when it releases.
Currently app startup fails in getSampleRateFromAudioQueue().
Thx
Juce 7 also no longer starts up on iOS 26, but I’m guessing that’s not going to be patched and we need to move to Juce 8.
Thx
Return code is -50 which seems to be bad parameter error.
I’m running into the same issue with the final version on the latest macOS 26.0 latest juce 8.0.10 with the iOS simulator. Have you found a solution?
It’s not possible to create a iOS app for me at the moment.
Edit: it works when deploying directly to a hardware device. Also commenting out the assert made it work. Probably I had to set a sample rate again in the standalone.
No, no solution as far as I know. No-one from the team responsed.
It looks like sample rate selection fails.
@reuk any ideas?
Thanks, we’ve pushed a fix here:
Hi there, I am seeing the same error on iOS 18.7.9 as well. Returning session.sampleRate instead of using getSampleRateFromAudioQueue() appears to work as a workaround on my end.
Is anyone else seeing this on other iOS versions or devices?
That’s interesting. Can you confirm that you’re on JUCE 8.0.13 or the juce9 preview branch?
Looking at juce_Audio_ios.cpp, it looks like we’re currently using getSampleRateFromAudioQueue() only on iOS 18, and using session.sampleRate on all other iOS versions. I believe this was intentional, there was quite a saga behind this change:
If the bug was fixed in iOS 18.7.9, then maybe we need to restrict the workaround so that it is only used on the buggy point releases of iOS 18. Unfortunately the team is going to be spread a bit thin over the next two weeks due to conference attendance, so we can’t easily verify the affected iOS versions.
If anyone else is able to confirm that the issue is present on iOS 18.7.9, then I can exclude that version from the range of iOS versions that use AudioQueue. When testing, please make sure to use either the juce9 or 8.0.13 branch, and test on a physical device.
Yes, can confirm this behaviour on both the develop and juce9 branches.
We could verify that this bug was fixed at least from 18.7.3 and up, so we adjusted our workaround.
The error happens on iOS 18.7.8 using juce 8.013. On juce 9 the error does not seem to happen. I posted earlier that it does on juce 9 but that was because I had microphone permission turned off. Now it runs a basic plugin from projucer from juce 9 on the iPad. Thanks.
