I have had the 2.0.0 RC installed from F-Droid. Today, I upgraded to the final. When launching the app, and going through the 2.0-Intro-screens, I did not end up with my accounts but with a blank app, asking me to configure one.
My old, configured accounts (2) should still have been there.
Android version: 4.4.4
Device model: Jolla C
Stock or customized system: Stock (Alien Dalvik)
Nextcloud app version: 2.0.0
Nextcloud server version: 12.0.3
Beta/dev and finals are different apps, so this is expected.
On Thu, 19 Oct 2017 at 11:02, blizzz notifications@github.com wrote:
Actual behaviour
I have had the 2.0.0 beta installed from F-Droid. Today, I upgraded to the
final. When launching the app, and going through the 2.0-Intro-screens, I
did not end up with my accounts but with a blank app, asking me to
configure one.
Expected behaviourMy old, configured accounts (2) should still have been there.
Steps to reproduce
- Have a beta from F-Droid installed (iirc the latest)
- Upgrade to final
- Launch NC app
Environment data
Android version: 4.4.4
Device model: Jolla C
Stock or customized system: Stock (Alien Dalvik)
Nextcloud app version: 2.0.0
Nextcloud server version: 12.0.3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/1691, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWskrChiNlqVZgF6-r_E08kL5wR4FPks5stxALgaJpZM4P-6Xk
.
@mario nope, it was the Beta Version of Nextcloud app, not Nextcloud-beta
Okay, they were Release Candidates, not Betas. Sorry for the confusion. Adjusting description.
Still, they were from Nextcloud Dev channel of F-Droid, were they not?
On Thu, 19 Oct 2017 at 11:11, blizzz notifications@github.com wrote:
Okay, they were Release Candidates, not Betas. Sorry for the confusion.
Adjusting description.—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/1691#issuecomment-337848174,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsrUqknTR0it-mI48qsTbP6UhsK4nks5stxJegaJpZM4P-6Xk
.
@mario no, they weren't. Version 2.0.0RC9 of com.nextcloud.client it was.
Strange then :( sorry then :-/
Thx for the report
On Thu, 19 Oct 2017 at 11:15, blizzz notifications@github.com wrote:
@mario https://github.com/mario no, they weren't. Version 2.0.0RC9 of
com.nextcloud.client it was.—
You are receiving this because you were mentioned.Reply to lthis email directly, view it on GitHub
https://github.com/nextcloud/android/issues/1691#issuecomment-337849128,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsqlR82yKAcpI7a1q_x_5tXT_AGZDks5stxNCgaJpZM4P-6Xk
.
@mario where is the config supposed to be stored?
Account manager. Might be related to one PR by Tobi, will have to check...
On Thu, 19 Oct 2017 at 11:19, blizzz notifications@github.com wrote:
@mario https://github.com/mario where is the config supposed to be
stored?—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/1691#issuecomment-337850008,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsoIgGzfsguyq8uzgWbu4OT8-8Prrks5stxQDgaJpZM4P-6Xk
.
um… and on file system level?
Well, there's a database in the internal data folder of the app, but accounts are not stored there :)
@AndyScherzinger could you please check if one of the latests PRs by Tobi (that handled account removal) could have done something like this?
Hm this wasn't even merged yet, but I think @tobiasKaminsky put it into the 2.0 release if I remember right...
I have already created a 2.0.0 gplay release with this fix.
So, perhaps he didn't add it to F-droid? ðŸ˜
$ ls -a nextcloud/
. .. [email protected] [email protected] tmp
If the data folder should be there, it is not anymore.
Entirely possible since it wasn't merged, it's not in F-Droid, indeed :-/
@AndyScherzinger can we merge (even if it's late) and tag 2.0.1? shrug Doesn't have to be in Gplay at all, just for F-droid...
Can confirm this after update via F-Droid of the regular app. Needed to authenticate again, but the files are still there locally (used SD card as storage).
@ogasser also mentioned this to me so maybe he has more info?
@jancborchardt the cause is an unmerged fix that went into the Google store manually, but not to f-droid.
@mario sure, go ahead. I won’t be near a keyboard for the next couple of hours...
@mario I created a hotfix branch + the changes #1696
solved via #1696 which should get picked up by f-droid tomorrow or the day after (hopefully).