Application not responding when we switch to Android App bundle

[Locke93]

We are using v0.6.0 and seeing a lot of ANRs from Google Play console:

"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x754ebb28 self=0x74d2e14c00
  | sysTid=29962 nice=0 cgrp=default sched=0/0 handle=0x7558887548
  | state=D schedstat=( 979726628 482621237 1056 ) utm=44 stm=53 core=1 HZ=100
  | stack=0x7fc2503000-0x7fc2505000 stackSize=8MB
  | held mutexes=
  #00  pc 000000000006e5fc  /system/lib64/libc.so (fsync+8)
  #01  pc 0000000000003670  /system/lib64/libopenjdkjvm.so (JVM_Sync+20)
  #02  pc 000000000001c494  /system/lib64/libopenjdk.so (FileDescriptor_sync+40)
  at java.io.FileDescriptor.sync (FileDescriptor.java)
  at com.facebook.soloader.SysUtil.fsyncRecursive (SysUtil.java:192)
  at com.facebook.soloader.SysUtil.fsyncRecursive (SysUtil.java:185)
  at com.facebook.soloader.UnpackingSoSource$1.run (UnpackingSoSource.java:362)
  at com.facebook.soloader.UnpackingSoSource.refreshLocked (UnpackingSoSource.java:377)
  at com.facebook.soloader.UnpackingSoSource.prepare (UnpackingSoSource.java:420)
  at com.facebook.soloader.SoLoader.initSoSources (SoLoader.java:304)
  at com.facebook.soloader.SoLoader.init (SoLoader.java:181)
  at com.facebook.soloader.SoLoader.init (SoLoader.java:164)
  at com.facebook.drawee.backends.pipeline.Fresco.initialize (Fresco.java:68)
  at com.facebook.drawee.backends.pipeline.Fresco.initialize (Fresco.java:45)

Interestingly, we found that every time we released a new version, ANRs went up and then went down:

This issue only occurs when we switch to Android App Bundle, is this a compatibility issue？

[grujo]

We are seeing the same thing since releasing our app as an App Bundle. Is this being looked into?

[smacgregor]

We also release our react native app as an App Bundle and are seeing this too.

[Teves-web]

The provided excerpt appears to be a stack trace from a Java/Android application, indicating an issue related to file synchronization (fsync) during the initialization of the Fresco library, used for image loading on Android.

[Teves-web]

The fsync function is associated with synchronizing data to disk, ensuring that modifications to files are reflected in physical storage. However, an error occurred during this operation, as evidenced by the stack trace.

[Teves-web]

Points of investigation include checking the file and directory permissions of the application, ensuring available space on the device, and considering the integrity of the storage. It's also crucial to ensure compatibility between the version of Fresco, the Android version, and other libraries in the project.

[Teves-web]

If the issue persists, it may be helpful to seek specific information about this problem on the Fresco or Android developer forums. Sharing the problem in these communities can provide valuable insights from other developers who may have encountered and resolved similar issues. Additionally, considering library and operating system updates could be an approach to either solve or work around the problem.