fix: Sporadic Blockingin loadFile()/loadMem() Methods

[xkos]

Description

Sometimes, Block with loadFile()/loadMem() Methods in IOS

Steps To Reproduce

1. Launch app use flutter run
2. init with loadFile or loadMem
3. Sometimes, only the first log entry is printed while subsequent log entries and all following code executions are halted.
4. When using loadMem(), I have confirmed that the readAsBytesSync is completed, and the log contains the data length output.

code like this:

// final data = cachedFile.file.readAsBytesSync();
logger.debug('[$_cacheKey] load file[${cachedFile.file.absolute.path}]');
// _audioPlayer = await SoLoud.instance.loadMem('${_cacheKey}.${_fileExtension}', data, mode: LoadMode.memory);
_audioPlayer = await SoLoud.instance.loadFile(cachedFile.file.absolute.path, mode: LoadMode.memory);
logger.debug('[$_cacheKey] load player succ');

example data

filepath:
/var/mobile/Containers/Data/Application/BxxxxxxxF-xxxx-xxxx-xxxx-xxxxxxx/Library/Caches/libNextCachedAudioPlayerPlusData/bf264f30-ba34-11f0-bd63-373ffeb5cb05.mp3

Additional Context

IOS, flutter_soloud: ^3.4.0 (I have also encountered this issue sporadically when using 3.3.9)

Both iPhones and iOS simulators have experienced this issue.

Currently unable to reliably reproduce the issue, but observed that when it occurs, the same file exhibits this behavior even after hot reload. The issue resolves completely after exiting and re-running flutter run

[rydmike]

Run into this issue yesterday as well on iOS. I am trying to pre-load a bunch (not so many, like 6 or so) of small sound effects into memory from assets, for quick use during app entire life cycle, during app setup, it started hanging. This on version 3.5.0.

This issue seems to be a blocker for doing this kind of preloading, which is sad because I need those sounds to play quickly on animation effects.

I might have to try another package, need this to work kind os "nowish" or I have to move on to another package. I will try some temp workarounds, this package seem so seemed so nice and promising otherwise.

My "agent" already tore into the repo, and started suggesting fixes, lol. But for that to have any real use I need to fork this repo and create a repro sample and dig in. I probably don't have any time to dig into it right now, but I will see later during next week, or next weekend.

[alnitak]

This is probably fixed with version 4. Feel free to reopen if the problem persists.