You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API design limits the paths that sound file can be on for IOS. It should allow a full-path to a file. An easy backward-compatible option might be to introduce a BaseFilePath.ROOT.
🎤 Motivation
On IOS, I have extension that is used accept shared .MP3 files with my app. For my extension to write them to access them, I have to use a shared container (both extension and App belong to an App Group). However, as the API does not take a full path, but a filename and a "BasePathType", I don't see how I can play files from this shared container that I can otherwise access.
💡 Alternatives
The only other solution that I can see is that I have to copy all the files from the shared container to the app container which is more complicated and more likely to fail.
The text was updated successfully, but these errors were encountered:
📋 Description
The API design limits the paths that sound file can be on for IOS. It should allow a full-path to a file. An easy backward-compatible option might be to introduce a BaseFilePath.ROOT.
🎤 Motivation
On IOS, I have extension that is used accept shared .MP3 files with my app. For my extension to write them to access them, I have to use a shared container (both extension and App belong to an App Group). However, as the API does not take a full path, but a filename and a "BasePathType", I don't see how I can play files from this shared container that I can otherwise access.
💡 Alternatives
The only other solution that I can see is that I have to copy all the files from the shared container to the app container which is more complicated and more likely to fail.
The text was updated successfully, but these errors were encountered: