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
Hello, My team has been using your library for different features and it is very useful to us, thank you !
We've recently come across the necessity to fetch a video with Authorization headers containing an authentication token and realized this was once possible for both android and iOS using the headers props but is no longer supported now.
The reason, as I understood, is the used API is private and it could cause the app to be rejected upon submission to the store. (see this issue)
Why it is needed
My team and I would very much like this feature implemented or any hint on a workaround in the meantime as it delivers a lot of value for our product.
Possible implementation
We have, unfortunately no idea whatsoever on a possible implementation.
Thank you for your time !
The text was updated successfully, but these errors were encountered:
Archigog
pushed a commit
to Archigog/react-native-video
that referenced
this issue
May 19, 2020
I feel we should add back AVURLAssetHTTPHeaderFieldsKey as this is not a private function and thus shouldn't lead to rejection. Expo are using this in their code as well. We've been setting AVURLAssetHTTPHeaderFieldsKey in our app and not got rejected. I will raise a PR for it.
Feature Request
Hello, My team has been using your library for different features and it is very useful to us, thank you !
We've recently come across the necessity to fetch a video with Authorization headers containing an authentication token and realized this was once possible for both android and iOS using the headers props but is no longer supported now.
The reason, as I understood, is the used API is private and it could cause the app to be rejected upon submission to the store. (see this issue)
Why it is needed
My team and I would very much like this feature implemented or any hint on a workaround in the meantime as it delivers a lot of value for our product.
Possible implementation
We have, unfortunately no idea whatsoever on a possible implementation.
Thank you for your time !
The text was updated successfully, but these errors were encountered: