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
Originally posted by Tiepbm December 15, 2023 Describe the bug
e: file:///Users/tiepbm/Desktop/TiepBM/PVI/PVI247/node_modules/react-native-image-marker/android/src/main/java/com/jimmydaddy/imagemarker/ImageLoader.kt:140:34 Type mismatch: inferred type is ImagePipelineExperiments but ImagePipelineConfig? was expected
Devlopment environment(please complete the following information):
OS: Mac M1
nodejs: 21.2.0
react-native: 0.73.0
react-native-image-marker : 1.1.10
Smartphone (please complete the following information):
Device:SamSung S22
OS: Android 12
thanks!
Originally posted by JimmyDaddy December 19, 2023
I have found the real cause of this problem, RN <= 0.73.0 uses fresco version is 2.xx.x But 0.73.0 uses 3.1.3.
It seems ImagePipelineConfig.newBuilder(context).experiment().setMaxBitmapSize(int).build() return ImagePipelineExperiments instead of ImagePipelineConfig now.
Sorry for that, I'll update a fix ASAP to adapt the 0.73.x
The text was updated successfully, but these errors were encountered:
Discussed in #175
Originally posted by Tiepbm December 15, 2023
Describe the bug
e: file:///Users/tiepbm/Desktop/TiepBM/PVI/PVI247/node_modules/react-native-image-marker/android/src/main/java/com/jimmydaddy/imagemarker/ImageLoader.kt:140:34 Type mismatch: inferred type is ImagePipelineExperiments but ImagePipelineConfig? was expected
Devlopment environment(please complete the following information):
Smartphone (please complete the following information):
thanks!
Originally posted by JimmyDaddy December 19, 2023
I have found the real cause of this problem, RN <= 0.73.0 uses fresco version is 2.xx.x
But 0.73.0 uses 3.1.3.
It seems ImagePipelineConfig.newBuilder(context).experiment().setMaxBitmapSize(int).build() return ImagePipelineExperiments instead of ImagePipelineConfig now.
Sorry for that, I'll update a fix ASAP to adapt the 0.73.x
The text was updated successfully, but these errors were encountered: