Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Files in Android #1989

Closed
area57 opened this issue Jan 17, 2018 · 8 comments · Fixed by #1998
Closed

Missing Files in Android #1989

area57 opened this issue Jan 17, 2018 · 8 comments · Fixed by #1998

Comments

@area57
Copy link

area57 commented Jan 17, 2018

Actual behaviour

  • in NC 3.0.0 RC1 the given save path Changes, so the Client does a complete Resync and nie i have duplicates which does Not Show Up in Pictures for exampel

Expected behaviour

-no Change in save path after Update

Steps to reproduce

Environment data

Android version: 7

Device model: Samsung Galaxy S7edge

Stock or customized system:stock

Nextcloud app version:3.0.0 RC1

Nextcloud server version:13.0.0 Beta 3

Logs

Web server error log

Insert your webserver log here

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

NOTE: Be super sure to remove sensitive data like passwords, note that everybody can look here! You can use the Issue Template application to prefill some of the required information: https://apps.nextcloud.com/apps/issuetemplate

@tobiasKaminsky
Copy link
Member

tobiasKaminsky commented Jan 18, 2018

@mario as you did #1836. Do you have an idea what is going on?
I thought there is no changing of the storage path, but only migration of push keys?

EDIT: #1954 is the right one.

@mario
Copy link
Contributor

mario commented Jan 18, 2018

Well, I've tested it quite a few times after the PR was finished and it didn't change the storage path on its own. You tested it too afaik.

@tobiasKaminsky
Copy link
Member

I suppose this is the problem as we silently use another storage path:
https://github.com/nextcloud/android/pull/1954/files#diff-b0fb3ea404c4520c55c0a642245615dfR117

This then should be reverted, or? Changing the storage path can still be done in preferences.

This should be fine as it is only a fallback:
https://github.com/nextcloud/android/pull/1954/files#diff-cba2b2d836007aea7c192ab85f22c8b4R1020

@mario
Copy link
Contributor

mario commented Jan 18, 2018

This is the default if there's nothing stored in preferences.

@tobiasKaminsky
Copy link
Member

Right, I read it wrong.
Then I do not know what is going on.
I'll try to reproduce it now with a real device.

@tobiasKaminsky
Copy link
Member

I tried it with S5 Neo:

  • installed 2.0.0
  • downloaded some file
  • move storage to external
  • installed 3.0RC1
  • all files are still there

@tobiasKaminsky tobiasKaminsky added the needs info Waiting for info from user(s). Issues with this label will auto-stale. label Jan 18, 2018
@xXSTrikeXx
Copy link
Contributor

Cant reproduce it.

@tobiasKaminsky
Copy link
Member

I can reproduce it with:

  • install 2.0
  • do nothing wrt storage path
  • install 3.0rc
  • storage path is now changed

2.0: /storage/emulated/0
3.0: /data/user/0/com.nextcloud.client/files

This is due to changing the default here:

MainApp.storagePath = appPrefs.getString(Preferences.PreferenceKeys.STORAGE_PATH,
getApplicationContext().getFilesDir().getAbsolutePath());

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants