David Solomon Fall
Previously for the Expo project that I am currently upgrading, "expo-svg-uri" worked because it was based on the Svg api package under the umbrello of the Expo mono repo for SDK<=32. This third-party package I imagine had a very similar goal to this previously supported package by Expo that could handle Svg uris at a Component Level as mentioned here: https://expo.canny.io/feature-requests/p/support-svguri
Now since "expo-svg-uri" is not maintained as rigourously as "react-native-svg", it too is not compatible in later Expo SDK versions. Just like "react-native-svg-uri"
This feature request is similar to this one but with more detail:
https://expo.canny.io/feature-requests/p/addition-of-svguri-and-importing-svg-files-as-a-component-or-image
And this feature request is outdated:
https://expo.canny.io/feature-requests/p/upgrade-react-native-svg
"react-native-svg" has added support at the Component level for Uri/Inline/Xml Svg support since v9.7.0 which was just released 5 days ago:
https://github.com/react-native-community/react-native-svg/tree/v9.7.0#use-with-content-loaded-from-uri
There is however support at the File Level through in v9.5.3(supported version for SDK34), for inlined Svgs:
https://github.com/react-native-community/react-native-svg/tree/v9.5.3#use-with-svg-files
Would love to hear from @brent-vatne or another Expo team member on whether or not this increase of the expected version range is possible at this time for "react-native-svg"
Thank you!