!tTIucwUZLRtKnXeurb:matrix.org

RiotX

26 Members
Discussion about RiotX matrix client. https://github.com/vector-im/riotX-android/15 Servers

Load older messages


Timestamp Message
17 Jan 2019
22:11:02@krombel:msg-net.dekrombel
In reply to @bubu:bubu1.eu
Can you elaborate?

The current state makes in impossible for the f-droid-app to distinguish two different builds. Each are 1.0 with versionCode 1
At least in the past the app deduplicated on the versionCode so only one build per versionCode was shown - which would lead to only one visible version.
If the builds have different versionCodes you can

  1. distinguish those builds visibly but (more importantly)
  2. the F-Droid-App itself sees, that there is a newer version and can trigger the update-handler
22:25:31@vurpo:hacklab.fivurpo (only partially ontopic) for some reason, F-Droid never notifies me about new development versions of Riot from your repo, and if I look at the "versions" list all the newer dev versions have a "downgrade" button no matter what version I have installed already
22:41:40@krombel:msg-net.dekrombel
In reply to @vurpo:hacklab.fi
(only partially ontopic) for some reason, F-Droid never notifies me about new development versions of Riot from your repo, and if I look at the "versions" list all the newer dev versions have a "downgrade" button no matter what version I have installed already
That is the result of the issue (or more the workaround I implemented because of that) that the versionCode between builds does not change
22:55:20@vurpo:hacklab.fivurpoOh, I thought that message only applied to Riot X
23:01:04@krombel:msg-net.dekrombel
In reply to @vurpo:hacklab.fi
Oh, I thought that message only applied to Riot X
I tried this to be fixed in riot-android a while back but then a different approach then got implemented which only made the build number viewable inside the app. I hope this can be better this time...
18 Jan 2019
06:03:23@arpy212:matrix.org@arpy212:matrix.org joined the room.
06:03:58@arpy212:matrix.org@arpy212:matrix.org left the room.
07:31:14@ganfra:matrix.orgganfraWe'll look into it with Benoit later At the moment version code and name are not handled at all, as it was not supposed to be uploaded on a store 😊
11:20:48@vurpo:hacklab.fivurpoScreenshot_20190118-132020.png
Screenshot_20190118-132020.png
11:21:34@vurpo:hacklab.fivurpo Something is off, the messages before "Thu 17 Jan" are the most recent messages, and those Thursday messages appeared immediately after I sent that rail replacement bus message
11:22:17@vurpo:hacklab.fivurpo I feel like I've seen similar bugs in other clients but I can't quite remember why that was
11:55:32@f0x:lain.hausFoks
In reply to @vurpo:hacklab.fi
I feel like I've seen similar bugs in other clients but I can't quite remember why that was
federation backfill?
11:56:06@vurpo:hacklab.fivurpo Maybe, but those messages can't be coming in over federation just now
11:56:14@vurpo:hacklab.fivurpoBecause I saw them yesterday when they were first sent
11:56:25@f0x:lain.hausFokshmm weird
11:57:00@f0x:lain.hausFoks also what's that room's alias? #watercooler:matrix.org gives me a "Server is banned from this room"
11:57:33@tulir:maunium.nettulirhmm, #watercooler:matrix.org seems to point to the watercooler murdered by maximus
11:58:01@tulir:maunium.nettulir #watercooler:half-shot.uk is the canonical alias
11:58:38@f0x:lain.hausFoksoh it needs an invite
11:59:09@tulir:maunium.nettuliryes
12:46:53@ganfra:matrix.orgganfra
In reply to @vurpo:hacklab.fi
Something is off, the messages before "Thu 17 Jan" are the most recent messages, and those Thursday messages appeared immediately after I sent that rail replacement bus message
Mmmm, that's weird, if you move and come back to the room, the messages stay in this order ?
Never had this issue at the moment
13:26:08@vurpo:hacklab.fivurpoThe app was entirely closed by now, but when I reopened it they were in the correct order
13:30:05@ganfra:matrix.orgganfraOk thanks! There are some issues with the timeline rendering I need to fix, so...
14:11:37@krombel:msg-net.dekrombel
Als Antwort auf @ganfra:matrix.org
We'll look into it with Benoit later At the moment version code and name are not handled at all, as it was not supposed to be uploaded on a store 😊
It would be a separate repo which everyone would have to enable manually. My repo is not the official repo of fdroid
14:13:41@krombel:msg-net.dekrombel/me waves from RiotX
14:14:12@krombel:msg-net.dekrombelEmotes do not seem to be working
14:14:27@andrewm:amorgan.xyzanoaapparently not 😄
14:15:37@bubu:bubu1.euBubu krombel: have you seen my reply in #fdroid:f-droid.org ?
14:16:28@krombel:msg-net.dekrombel
Als Antwort auf @bubu:bubu1.eu
krombel: have you seen my reply in #fdroid:f-droid.org ?
I am just looking through my backlog => will see it in a few moments 😏
18:42:37@_neb_rssbot_=40benoit.marty=3amatrix.org:matrix.orgRSS Bot [@benoit.marty:matrix.org] RiotXAndroidDevelop all builds posted a new article: RiotXAndroidDevelop #7 (stable) ( https://matrix.org/jenkins/view/MatrixView/job/RiotXAndroidDevelop/7/ )

There are no newer messages yet.


Back to Room List