KimiChiu

How about using a custom draw to scale down the `imageView` display size, so we are still painting on the full size. I found a implementation here. https://stackoverflow.com/questions/12169905/zoom-and-panning-imageview-android

> > How about using a custom draw to scale down the `imageView` display size, so we are still painting on the full size. > > I found a implementation...

I think it's because `SubsamplingScaleImageView.this.doubleTapZoomScale` is always 1. So this line in the `doubleTapZoom` will always zoom to 1. `float doubleTapZoomScale = Math.min(maxScale, SubsamplingScaleImageView.this.doubleTapZoomScale);` Because this value will be set...

I tried, it worked the same as UIImage. Both of them need to remove .backgroundDecode.

> If the database file is growing too large is usually a Realm version pinning issue, a Realm instance is not closed properly, or it is instantiated in a non-looper...

I don't know why you can't just create that table. At least you should tell us which table in the error messages.

Hi, I have the same problem too. In Glide 3, we fix this problem by this way. builder.setDiskCacheService(new FifoPriorityThreadPoolExecutor(4)); builder.setResizeService(new FifoPriorityThreadPoolExecutor(4)); But we can't found these APIs in Glide 4.

I tried this, ``` builder.setAnimationExecutor( GlideExecutor.newAnimationExecutor(4, GlideExecutor.UncaughtThrowableStrategy.DEFAULT) ); builder.setDiskCacheExecutor( GlideExecutor.newDiskCacheExecutor(4, "glideDiskCacheExecutor", GlideExecutor.UncaughtThrowableStrategy.DEFAULT) ); builder.setSourceExecutor( GlideExecutor.newSourceExecutor(4, "glideSourceExecutor", GlideExecutor.UncaughtThrowableStrategy.DEFAULT) ); ``` But it still plays in slow motion in RecyclerView. The ViewPager...

Same here. Just update realm version from 10.7.4 to 10.17.0 because of XCode 13 compatibility. The logs are just showing like this. ``` No such table exists Exception backtrace: 0...

@dianaafanador3 Sorry, I can't. I don't know which part of our codes can reproduce this issue. There's no clue in the stack trace. All I did was changing the version...