Can you check if autoPlayGifs setting is enabled?
There is currently a bug with our image viewer that it seems to use imageloader that is set on the application level (which is controlled by that setting) instead of the one that is passed into it(which has it always enabled).
There is a bug with our toolkit and our image display dependency
This is a bug in our toolkit. But it has been fixed already. When the release lands we will update our dependency.
settings > about > crash logs
can you post the stacktrace here or on github or in my dms
Gifs never worked in comments. Could never get it to work. But imageviewer should always auto play gifs regardless of the setting autoPlayGifs. So that's a bug I'll look into.
The setting is for controlling previews and icons/avatars.
Alright, looked into it. There was indeed a bug where it did the initial posts request by page and the subsequent by page_cursor. But this has been there for a while. Pre 67 we used to deduplicate every post returned by Lemmy. So it was masking that bug. I didn't think the deduplication was still necessary with page_cursor, so it was removed. If it still frequently happens after this fix. I'll add it back.
I have managed to reproduce this on Android 8. It seems to be android 8 specific. This is a problem with our toolkit. You seem to the first to experience this because I can't find anything on this yet. The only thing you can do is to downgrade to Jerboa 0.0.66
Error
[java.lang.NoSuchMethodError: No virtual method setAmbientShadowColor(I)Z in class Landroid/view/RenderNode; or its super classes (declaration of 'android.view.RenderNode' appears in /system/framework/framework.jar:classes2.dex)
at androidx.compose.ui.graphics.layer.GraphicsLayerV23.setAmbientShadowColor-8_81llA(GraphicsLayerV23.android.kt:212)
at androidx.compose.ui.graphics.layer.GraphicsLayer.setAmbientShadowColor-8_81llA(AndroidGraphicsLayer.android.kt:807)
at androidx.compose.ui.platform.GraphicsLayerOwnerLayer.updateLayerProperties(GraphicsLayerOwnerLayer.android.kt:119)
at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters(NodeCoordinator.kt:545)
at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters$default(NodeCoordinator.kt:524))]( java.lang.NoSuchMethodError: No virtual method setAmbientShadowColor(I)Z in class Landroid/view/RenderNode; or its super classes (declaration of 'android.view.RenderNode' appears in /system/framework/framework.jar:classes2.dex)
at androidx.compose.ui.graphics.layer.GraphicsLayerV23.setAmbientShadowColor-8_81llA(GraphicsLayerV23.android.kt:212)
at androidx.compose.ui.graphics.layer.GraphicsLayer.setAmbientShadowColor-8_81llA(AndroidGraphicsLayer.android.kt:807)
at androidx.compose.ui.platform.GraphicsLayerOwnerLayer.updateLayerProperties(GraphicsLayerOwnerLayer.android.kt:119)
at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters(NodeCoordinator.kt:545)
at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters$default(NodeCoordinator.kt:524)
at androidx.compose.ui.node.NodeCoordinator.updateLayerBlock(NodeCoordinator.kt:503)
at androidx.compose.ui.node.NodeCoordinator.updateLayerBlock$default(NodeCoordinator.kt:480)
at androidx.compose.ui.node.NodeCoordinator.placeSelf-MLgxB_4(NodeCoordinator.kt:384)
at androidx.compose.ui.node.NodeCoordinator.placeAt-f8xVGno(NodeCoordinator.kt:332)
at androidx.compose.ui.node.InnerNodeCoordinator.placeAt-f8xVGno(InnerNodeCoordinator.kt:168)
at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35)
at androidx.compose.ui.layout.Placeable$PlacementScope.placeWithLayer(Placeable.kt:646)
at androidx.compose.ui.layout.Placeable$PlacementScope.placeWithLayer$default(Placeable.kt:327)
at androidx.compose.ui.graphics.BlockGraphicsLayerModifier$measure$1.invoke(GraphicsLayerModifier.kt:580)
at androidx.compose.ui.graphics.BlockGraphicsLayerModifier$measure$1.invoke(GraphicsLayerModifier.kt:579)
at androidx.compose.ui.node.LookaheadCapablePlaceable$layout$1.placeChildren(LookaheadDelegate.kt:223)
at androidx.compose.ui.node.LayoutModifierNodeCoordinator.onAfterPlaceAt(LayoutModifierNodeCoordinator.kt:270)
at androidx.compose.ui.node.LayoutModifierNodeCoordinator.placeAt-f8xVGno(LayoutModifierNodeCoordinator.kt:247)
at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35)
at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50(Placeable.kt:621)
at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate$placeOuterCoordinatorBlock$1.invoke(LayoutNodeLayoutDelegate.kt:561)
at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate$placeOuterCoordinatorBlock$1.invoke(LayoutNodeLayoutDelegate.kt:548)
at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:503)
at androidx.compose.runtime.snapshots.SnapshotStateObserver$ObservedScopeMap.observe(SnapshotStateObserver.kt:502)
at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:258)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:133)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeLayoutModifierSnapshotReads$ui_release(OwnerSnapshotObserver.kt:98)
at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeOuterCoordinator-MLgxB_4(LayoutNodeLayoutDelegate.kt:867)
at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeSelf-MLgxB_4(LayoutNodeLayoutDelegate.kt:835)
at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeAt-f8xVGno(LayoutNodeLayoutDelegate.kt:761)
at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35)
at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50(Placeable.kt:621)
at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50$default(Placeable.kt:259)
at androidx.compose.foundation.layout.BoxKt.placeInBox(Box.kt:223)
at androidx.compose.foundation.layout.BoxKt.access$placeInBox(Box.kt:1)
at androidx.compose.foundation.layout.BoxMeasurePolicy$measure$5.invoke(Box.kt:203))
In Lemmy 0.19.4, scores were reworked. So that you could individually pick which score you like to see (upvote, downvote, total, ratio)
Before this this option its behaviour was to disable every score type. Now it just hides the "total". With Lemmy 0.19.4 they did a poll to see which scores are the most popular and should be the default. Upvotes + Downvotes won. So show_scores is now by default false.
Currently our setting division ('Account settings' vs 'look and feel') doesn't make much sense. But 'look and feel' is all the settings that are stored on the device. Thus apply to all accounts. Account settings are settings we retrieve from Lemmy and are different per account.
So that brings us to the listingviewmode. That shows the total_scores but since its disabled, it is hidden. I'll probably rework it so that it shows the upvotes if 'shows_scores' is disabled.
Make sure you have 'show scores' enabled in the settings.
Preferably you report this on the issue tracker. But here is fine too.
Which version of Jerboa do you use? settings > about
And on which screen (Home , community, inbox, ...) do you have this? And do you have it as soon as you press the sort by icon? or when you select a sort? And if so which sort?
What Android version?
I have not been able to reproduce this problem.
We are aware, it has not made it into this release yet.
Overview of the changes, can't open this one yet in Jerboa
Added 3 modes for the post action bar
Long form
Short lefthand form
Short righthand form
Where do you suggest we should place it?