obasille

@keith-kurak is this something can be addressed for the next release? This issue breaks loadAsync/loadTextureAsync for loading textures when using production APKs. Thanks!

Hi @EvanBacon, I'm wondering if this issue can be addressed as it prevents expo-three from loading texture when building an Android APK. Please see this expo-three issue: https://github.com/expo/expo-three/issues/225

Note: Using `ExpoTHREE.loadTextureAsync()` directly doesn't throw an error, a texture object is created but it has no data when the code is run from an APK (it's rendered black). ```...

Thanks! It's based on the "rename your files to some other extension so they are not bundled as drawable" workaround. I personally prefer the other work around that I mentioned,...

@uakhundz as described in the title and description, the issue discussed here happens only on Android standalone (.apk files). This is related to how images are packaged on Android APKs.

Please have a look at this issue thank you!

Please don't close this issue, it makes quite difficult to load textures on Android production builds. Thank you.

I don't think the developers intend to continue developing this package. See this issue: https://github.com/GeekyAnts/NativeBase/issues/4302

@tiomun the dependency messages I've reported are warnings, not errors, they are probably unrelated to your issue. I'm currently running without issue on Android with these pacakages (I haven't tested...

Thank you for the update @markrickert! I still get those warnings (which I'm realizing come from browser-polyfill 1.0.1 imported by expo-three) but most importantly it's wonderful news that we can...