testAccount

testAccount , 9 days ago

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.

testAccount , 8 days ago

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))

testAccount , 9 days ago

Make sure you have 'show scores' enabled in the settings.

testAccount , 9 days ago

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.

testAccount , 10 days ago

We are aware, it has not made it into this release yet.

testAccount , 3 months ago

https://reddthat.com/nodeinfo/2.0.json

Reddthat instance doesn't have the correct version set in their nodeinfo.
It is empty, this is important for federation (and for Jerboa to know which API implementation that it needs to use). Now I don't know if this is a Lemmy problem or just a problem with just that instance. But Jerboa behaves as expected

https://lemmy.one/pictrs/image/886cbd2a-cfa6-44ca-bb7a-3ffe9bce2464.png

How it should be
https://lemmy.one/pictrs/image/d2cee1da-27f4-4701-b73b-c552a08cff42.png

testAccount , 3 months ago

np

testAccount , 3 months ago

Yeah the admin should be made aware of this

testAccount , 3 months ago

It should still be there, can you go in the settings disable the show navigation bar setting, and check if it now appears? If so then it hidden behind the navigation bar. Which should be fixed in the next release

testAccount , 3 months ago

Can you expand? The comment/post scores UI changes? Dessalines changed the default for that, it a setting with lots of options, but persistence isn't implemented yet so it isn't exposed.

testAccount , 3 months ago

@dessalines Do 403s from pictrs only come from failed authentication? or does it lump all failed requests under 403 such as bad format, image size?

testAccount , 3 months ago

Pre 0.0.60, the rules for showing the votes in arrows were -> show scores setting enabled + and if there are downvotes

Now with 0.0.60 Dessalines reworked how the votes are displayed.

Modes (all in header):

• Display full -> show score and downvotes
• Display score + upvote ratio
• Display score
• Hidden

They will be configurable once the setting is persisted.

I have proposed to add a Display votes in arrow setting (Old behaviour)

We will see what comes from it.

testAccount , 3 months ago

You mean in card view that it would fully show like a normal image. Hmm, the problem is that most link thumbnails aren't really relevant to the post, for example this post it would show an image of the release page. Which isn't really that relevant as we just want to link to the actual release notes.

testAccount , 3 months ago

The biggest performance changes should be from 0.0.56

Due to a compound of factors:

• Upgrade of Jetpack Compose, the toolkit we use for the app, they have done some optimizations
• Stability config change (Basically we tell Compose these elements are stable)
• More memozation of function calls

Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, "keep the same UI element as before", it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second

In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)

Google does some amazing work, it just takes them a long time.
Once this patch lands we should see more optimizations
https://issuetracker.google.com/issues/241154852

I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i'll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.

testAccount , 3 months ago

What is the actual usecase? Do you want to see the link images in the imageviewer? Cuz i could probably add a option on long click that it would allow you to see the image in the image viewer?

testAccount , 4 months ago

It should have stayed roughly the same, that is also a separate bug. That I'll file

testAccount , 4 months ago

And this was fine in 0.0.55? or were you using a earlier version?

Also which android version are you using? I can't seem to replicate this very well, the part of 29px but it suddenly got smaller with the most recent update.