Can't open local folder on Android #3789

aadilayub · 2022-01-06T17:26:49Z

Describe the bug
When I grant storage permissions and try to add an empty folder, nothing happens.

To Reproduce
Steps to reproduce the behavior:

Install latest nightly version of Logseq on Android
Click on 'Grant permission' and add an empty folder as a new graph

Expected behavior
Adding an empty folder generates a new graph.

Smartphone:

Device: Realme 5i
OS: Android 10
Browser: Chrome
Version: Android Nightly Release 20220106

koan-github · 2022-01-07T11:05:46Z

I am experiencing the same issue.

Device: Mi 10T
OS: Android 11 with MIUI 12
Version: latest nightly, but also experienced this issue with previous releases

Philogicatician · 2022-01-07T23:10:24Z

Same here.

Device: Samsung, Galaxy J7 Star
OS: Android 9
Version: Nightly Release 20220107

vivew · 2022-01-22T10:05:03Z

Same here.

Device: Huawei P30
OS: Android 10 with EMUI 11.0.0
Version: both in 0.5.9 and Nightly Release 20220121

koan-github · 2022-01-23T17:20:47Z

For me, the issue disappeared after I removed a "#" from the folder name of my notes folder. Maybe some special characters in folders names cause this?

aadilayub · 2022-01-24T04:39:36Z

@koan-github for me it happens when creating a graph from an empty folder too

vivew · 2022-01-24T06:32:07Z

My issue resolved after choosing a file name & path containing no space characters. Thanks for the tip @koan-github

MrModest · 2022-01-29T08:33:49Z

The same issue on my tablet

Mi Pad 4 Plus
Android 8.1.0
MIUI by xiaomi.eu 10.3
Tried versions: 0.5.5 - 0.5.9

Vault path: /storage/emulated/0/Documents/Logseq/logseq-vault/

Stacktrace (the same for all versions):

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
 at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
 at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
 at android.os.Handler.handleCallback(Unknown Source:2)
 at android.os.Handler.dispatchMessage(Unknown Source:4)
 at android.os.Looper.loop(Unknown Source:152)
 at android.os.HandlerThread.run(Unknown Source:28)
Caused by: java.lang.reflect.InvocationTargetException
 at java.lang.reflect.Method.invoke(Native Method)
 at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
 at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
 ... 5 more
Caused by: java.lang.NullPointerException: uriString
 at android.net.Uri$StringUri.<init>(Unknown Source:22)
 at android.net.Uri$StringUri.<init>(Unknown Source:0)
 at android.net.Uri.parse(Unknown Source:3)
 at com.capacitorjs.plugins.filesystem.Filesystem.getFileObject(Filesystem.java:202)
 at com.capacitorjs.plugins.filesystem.Filesystem.readdir(Filesystem.java:77)
 at com.capacitorjs.plugins.filesystem.FilesystemPlugin.readdir(FilesystemPlugin.java:270)
 ... 8 more

This vault opens correctly on my phone (OnePlus 7, Android 11, version 0.5.9)

ketoxime · 2022-03-14T21:27:20Z

Version 0.6.3. crashes when choosing local folder. Granting permission seemed to work.
A downgrade to version 0.6.2 seems to work though. Installed via IzzyOnDroids F-Droid repo.

natrius · 2022-03-21T06:56:33Z

Downloaded the android app 0.6.4 and opened it, got the "Storage access permission" screen and if i choose that, nothing happens.

Reproduce

Open Logseq
"Grant permission"
Choose random folder or new created one (does not show existing ones"
Press "Allow access to 'Logseq'"
Allow again
Back into "Storage access permission" screen in the app.

The same for "Add a graph".

Mobile Info
Device: Xiaomi Mi 9
Android: 10
Logseq: 0.6.4 (F-Droid through IzzySoft Repository)

Additional
Usally i get an android-window for asking the permission to store files on the device - this window does not appear at all. But "android settings > apps > permissions" -> "Access and change files on internal storage" is granted with "Always allow" as well, so i might have allowed this the first time i opened the app.

joebroesel · 2022-03-28T08:08:20Z

Can report the same problem when trying to open a synced Nextcloud folder. Folder access is granted, but, I end up on the start page again after selecting the folder.
The path is "/Android/media/com.nextcloud.client/nexcloud/user@server.de%2Fnextcloud/
Opening a folder path without special characters works. Could it be the "@" or URL-encoded "/" in the path?

Device: Xiaomi Mi 8 lite
Android: 11 (lineageOS)
Logseq: 0.6.5 (Google Playstore)

aadilayub · 2022-04-24T17:47:08Z

There are lots of reports mentioning this issue. It would be good to centralise them here.

#4936
#5038
#4628
#4993
#3972

aadilayub · 2022-04-24T17:53:57Z

I have now experienced this issue on multiple phones, on Android 10, 11, and 12, across multiple versions of Logseq from 0.6.2 up to the latest nightly. Am currently experiencing it on a Google Pixel 5, where adding a graph worked initially but mysteriously stopped working after a reinstall. It takes place with empty graphs, and with large graphs, and after removing special characters from file names. It also takes place with graphs placed in the Android home folder and in subdirectories.

I made an attempt at fishing out the error message from the crash through logcat. It appears to be the same as the one shared by @MrModest

FATAL EXCEPTION: CapacitorPlugins
Process: com.logseq.app, PID: 7908
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
	at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
	at android.os.Handler.handleCallback(Handler.java:938)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
	... 6 more
Caused by: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT_TREE cat=[android.intent.category.DEFAULT] }
	at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2117)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1762)
	at android.app.Activity.startActivityForResult(Activity.java:5407)
	at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:584)
	at androidx.core.app.ActivityCompat.startActivityForResult(ActivityCompat.java:234)
	at androidx.activity.ComponentActivity$2.onLaunch(ComponentActivity.java:218)
	at androidx.activity.result.ActivityResultRegistry$2.launch(ActivityResultRegistry.java:162)
	at androidx.activity.result.ActivityResultLauncher.launch(ActivityResultLauncher.java:47)
	at com.getcapacitor.Plugin.startActivityForResult(Plugin.java:181)
	at com.logseq.app.FolderPicker.pickFolder(FolderPicker.java:40)
	... 9 more

natrius · 2022-04-24T18:25:05Z

I manged to get it working btw. - when i press "Grant permissions" it does not show anything in that folder, even if i create a logseq folder (but, it exists, i checked).
What i noticed, if i press "phone" on the left side in the file-browser and manually navigate to "Download" again, i can see all the folders and i can see the "Logseq"-Folder as well. If i choose the folder now - it works for me.

aadilayub · 2022-04-25T07:22:52Z

I manged to get it working btw. - when i press "Grant permissions" it does not show anything in that folder, even if i create a logseq folder (but, it exists, i checked).
What i noticed, if i press "phone" on the left side in the file-browser and manually navigate to "Download" again, i can see all the folders and i can see the "Logseq"-Folder as well. If i choose the folder now - it works for me.

It doesn't get that far for me. After I grant file access permission, and click choose folder, it immediately crashes.

Here's a screen recording: https://photos.app.goo.gl/ZXjWMQUZHy5pKtGw9

natrius · 2022-04-25T07:27:54Z

This issue is about, and i quote your initial comment "When I grant storage permissions and try to add an empty folder, nothing happens." and not "the app crashes".

These are two different issues in my opinion.

SkyLull · 2022-04-25T14:35:55Z

I got a similar issue.

Reproduce

1. Install a brand new LogSeq / Clear all app user data and cache
2. Choose a folder for my graph
3. Allow the permission request
4. Navigate to my storage root first then browse and select a previously created / newly created folder as the target.
5. Starting to load. ("Parsing file" on the top left will appear for a brief moment)
6. Freeze, then "Logseq has stopped working" pops up.

and there is an alternative result if, in the 4th step, I choose as the file exploring app default (it will be located at the exact folder I chose last time before current data clear&reset )

4. Select the default (right as last open) folder without navigating out first
5. Nothing happened, nothing loaded (the "choose a folder" UI is still there.)

The folder I use was all under "Downloads" or "Pictures" default folder created by the system, might have something to do with this?

Device Info:

App Version: 0.6.6 on Android.
Android Version: 8.0.0
Device: ASUS_X00PD
Installed via direct downloaded .apk file from GitHub release.
I've done some tests and found such problems don't exist in 0.5.9, 0.6.2, and started to appear in 0.6.3.

aadilayub · 2022-04-26T17:20:14Z

This issue is about, and i quote your initial comment "When I grant storage permissions and try to add an empty folder, nothing happens." and not "the app crashes".

These are two different issues in my opinion.

You might be right. However, because both issues are giving the same stack trace, they may have the same underlying cause.

aadilayub · 2022-04-26T17:23:43Z

I have now experienced this issue on multiple phones, on Android 10, 11, and 12, across multiple versions of Logseq from 0.6.2 up to the latest nightly. Am currently experiencing it on a Google Pixel 5, where adding a graph worked initially but mysteriously stopped working after a reinstall. It takes place with empty graphs, and with large graphs, and after removing special characters from file names. It also takes place with graphs placed in the Android home folder and in subdirectories.

I made an attempt at fishing out the error message from the crash through logcat. It appears to be the same as the one shared by @MrModest

FATAL EXCEPTION: CapacitorPlugins
Process: com.logseq.app, PID: 7908
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
	at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
	at android.os.Handler.handleCallback(Handler.java:938)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
	... 6 more
Caused by: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT_TREE cat=[android.intent.category.DEFAULT] }
	at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2117)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1762)
	at android.app.Activity.startActivityForResult(Activity.java:5407)
	at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:584)
	at androidx.core.app.ActivityCompat.startActivityForResult(ActivityCompat.java:234)
	at androidx.activity.ComponentActivity$2.onLaunch(ComponentActivity.java:218)
	at androidx.activity.result.ActivityResultRegistry$2.launch(ActivityResultRegistry.java:162)
	at androidx.activity.result.ActivityResultLauncher.launch(ActivityResultLauncher.java:47)
	at com.getcapacitor.Plugin.startActivityForResult(Plugin.java:181)
	at com.logseq.app.FolderPicker.pickFolder(FolderPicker.java:40)
	... 9 more

Update: I figured out what was causing this. On both my phones, I'd uninstalled the stock file manager app and replaced it with a third party file manager. The intent probably only plugins into the stock file manager, and when it isn't present, gives an error. After I reset my phone to factory settings, I was able to add a folder and use logseq.

It's possible that the reason for this crash on other phones is that the manufacturer OS doesn't ship the AOSP file manager/file picker that is required by this intent.

MrModest · 2022-04-26T18:35:07Z

I made an attempt at fishing out the error message from the crash through logcat. It appears to be the same as the one shared by @MrModest

Sorry, but my exception is quite different, and I get it when I choose the folder. And I choose it via system file manager, not third party.

My exception is

java.lang.NullPointerException: uriString

but your is

android.content.ActivityNotFoundException: No Activity found to handle Intent

MrModest · 2022-04-26T18:48:29Z

It's interesting.
When I tried to choose folder like /storage/emulated/0/Logseq (or Download folder), I got a new stacktrace:

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
	at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
	at android.os.Handler.handleCallback(Unknown Source:2)
	at android.os.Handler.dispatchMessage(Unknown Source:4)
	at android.os.Looper.loop(Unknown Source:152)
	at android.os.HandlerThread.run(Unknown Source:28)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
	... 5 more
Caused by: java.lang.NoSuchMethodError: No direct method <init>(Ljava/io/File;I)V in class Landroid/os/FileObserver; or its super classes (declaration of 'android.os.FileObserver' appears in /system/framework/framework.jar)
	at com.logseq.app.FsWatcher$SingleFileObserver.<init>(FsWatcher.java:203)
	at com.logseq.app.FsWatcher.watch(FsWatcher.java:60)
	... 8 more

But for /storage/emulated/0/Documents folder error still the previous one

bbigras · 2022-08-10T03:24:10Z

I've posted a fix, the test android app can be downloaded from:

https://nightly.link/logseq/logseq/actions/runs/2829456996

It still crashes when I try to open my populated logseq folder on my fire hd 8 tablet.

andelf · 2022-08-10T03:42:36Z

@bbigras Is it on external SD card?
What's the version of the Android OS?

efade · 2022-08-10T03:47:06Z

I've posted a fix, the test android app can be downloaded from:

https://nightly.link/logseq/logseq/actions/runs/2829456996

It works! At least for me. Updated straight from 0.61, without clearing data or cache. I then cleared the cache and data to try the initial set up, it worked without problem. Previously, Logseq crashes when selecting the graph folder. Now that problem is gone.

Device: Samsung S8 Exynos
OS : Stock Samsung Android 9 with One UI.

andelf · 2022-08-10T03:48:52Z

@efade Thanks for your report.
This fix will be included in the next release.

andelf · 2022-08-10T03:50:54Z

@efade I've added an external storage fix.
Could you help to try https://nightly.link/logseq/logseq/actions/runs/2829884048

bbigras · 2022-08-10T04:03:25Z

@bbigras Is it on external SD card?
What's the version of the Android OS?

No, internal. In documents/logseq.

Fire HD 8 (10th gen)
Android 9, API Level 28 (according to https://developer.amazon.com/docs/fire-tablets/ft-identifying-tablet-devices.html#fire-tablet-features)

bbigras · 2022-08-10T04:09:02Z

Note that with https://nightly.link/logseq/logseq/actions/runs/2829884048 , I get this error message before the crash.

andelf · 2022-08-10T12:44:54Z

@bbigras Thanks. The error message box is just added to help debug.
This is a really complicated bug. I need to figure out how Fire HD 8 handles storage.

MrModest · 2022-08-10T20:09:47Z

Device:

Xiaomi Mi Pad 4 Plus
Android 8.1.0
MIUI by xiaomi.eu 10.3

Logseq path: /storage/emulated/0/Documents/Logseq/logseq-vault/ (Internal storage)

https://nightly.link/logseq/logseq/actions/runs/2829456996

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
	at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
	at android.os.Handler.handleCallback(Unknown Source:2)
	at android.os.Handler.dispatchMessage(Unknown Source:4)
	at android.os.Looper.loop(Unknown Source:152)
	at android.os.HandlerThread.run(Unknown Source:28)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
	... 5 more
Caused by: java.lang.NullPointerException: uriString
	at android.net.Uri$StringUri.<init>(Unknown Source:22)
	at android.net.Uri$StringUri.<init>(Unknown Source:0)
	at android.net.Uri.parse(Unknown Source:3)
	at com.capacitorjs.plugins.filesystem.Filesystem.getFileObject(Filesystem.java:202)
	at com.capacitorjs.plugins.filesystem.Filesystem.readdir(Filesystem.java:77)
	at com.capacitorjs.plugins.filesystem.FilesystemPlugin.readdir(FilesystemPlugin.java:270)
	... 8 more

https://nightly.link/logseq/logseq/actions/runs/2829884048

Error popup:

and stacktrace then:

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:601)
	at com.getcapacitor.-$$Lambda$Bridge$25SFHybyAQk7zS27hTVXh2p8tmw.run(Unknown Source:8)
	at android.os.Handler.handleCallback(Unknown Source:2)
	at android.os.Handler.dispatchMessage(Unknown Source:4)
	at android.os.Looper.loop(Unknown Source:152)
	at android.os.HandlerThread.run(Unknown Source:28)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at com.getcapacitor.PluginHandle.invoke(PluginHandle.java:121)
	at com.getcapacitor.Bridge.lambda$callPluginMethod$0$Bridge(Bridge.java:592)
	... 5 more
Caused by: java.lang.NullPointerException: uriString
	at android.net.Uri$StringUri.<init>(Unknown Source:22)
	at android.net.Uri$StringUri.<init>(Unknown Source:0)
	at android.net.Uri.parse(Unknown Source:3)
	at com.capacitorjs.plugins.filesystem.Filesystem.getFileObject(Filesystem.java:202)
	at com.capacitorjs.plugins.filesystem.Filesystem.readdir(Filesystem.java:77)
	at com.capacitorjs.plugins.filesystem.FilesystemPlugin.readdir(FilesystemPlugin.java:270)
	... 8 more

MrModest · 2022-08-10T20:21:41Z

Now tried with external SdCard and it works! o_0
Path: /storage/0042-A040/Documents/logseq/

And works not just empty, but my full folder which I pulled from git

andelf · 2022-08-11T01:37:56Z

@MrModest Thanks.
I'm trying to figure out how to handle tree/home paths.

efade · 2022-08-11T03:08:47Z

@efade I've added an external storage fix.
Could you help to try https://nightly.link/logseq/logseq/actions/runs/2829884048

Hi @andelf. I can confirm it worked. Same device as before:
Samsung S8
Stock Samsung Android 9 with One UI.

I forgot to say it before, but thank you so much for the fix.

andelf · 2022-08-11T03:10:52Z

@efade Thanks. The fix is already included in the nightly release.😁

andelf · 2022-08-11T03:15:01Z

@MrModest @bbigras

I've just added a tree/home style path fix at #6328

Could you help to test the demo App(😅All my Android devices can not reproduce this kind of path):
https://nightly.link/logseq/logseq/actions/runs/2837086413

bbigras · 2022-08-11T03:18:46Z

It works!! 🎉

bbigras · 2022-08-11T13:43:59Z

Thank you very much for the fix @andelf

MrModest · 2022-08-11T20:41:41Z

Could you help to test the demo App(😅All my Android devices can not reproduce this kind of path): https://nightly.link/logseq/logseq/actions/runs/2837086413

Now it works in both cases: external and internal storage. Thanks!

ramboe · 2022-08-14T11:15:45Z

I'm sorry but I just installed the nightly 0.8.0 and I still get the old behavior: chose a folder, nothing happens.

XPERIA 1 IV

Jael-Tactaquin · 2022-08-14T17:50:35Z

Hi it is helpful to fix it by adding a folder on the storage instead of under termux storage by using cd ~/storage/{name of folder} , it fixed everything. App only crashes when using directory of termux itself, or under within any other app directory

deGrasi · 2022-08-15T11:26:24Z

Hello,
for me the nightly 0.8.0 does not work yet with NextCloud (is on my web server). Even if I create a new folder inside NextCloud, that is an empty folder, it does not work. The app gives an error message and closes.

On the internal storage of my Pixel 6 with Android 12 it works fine.

Data, memory and cache has already been cleared, all permissions granted.

Android 12
Pixel 6
Logseq nightly 0.8.0

ramboe · 2022-08-16T13:24:24Z

Hi it is helpful to fix it by adding a folder on the storage instead of under termux storage by using cd ~/storage/{name of folder} , it fixed everything. App only crashes when using directory of termux itself, or under within any other app directory

I am a bit noobie when it comes to android. Can you please give me some instructions on how to provide you with the necessary information? thank you very much!

Jael-Tactaquin · 2022-08-17T08:16:52Z

Hi it is helpful to fix it by adding a folder on the storage instead of under termux storage by using cd ~/storage/{name of folder} , it fixed everything. App only crashes when using directory of termux itself, or under within any other app directory

I am a bit noobie when it comes to android. Can you please give me some instructions on how to provide you with the necessary information? thank you very much!

I also used Android and GitHub as my repo. So I use termux to be able to clone my GitHub but on internal storage.
For my experience Logseq will crash if I will use a folder within termux directory as to where to clone my git. So I created outside termux directory, and inside my internal storage (~/downloads/jael-logseq-android) I created a new folder then git clone there.

I then open logseq to choose that folder inside downloads and it did not crash.

ramboe · 2022-08-20T10:02:59Z

also used Android and GitHub as my repo. So I use termux to be able to clone my GitHub but on internal storage. For my experience Logseq will crash if I will use a folder within termux directory as to where to clone my git. So I created outside termux directory, and inside my internal storage (~/downloads/jael-logseq-android) I created a new folder then git clone there.

I then open logseq to choose that folder inside downloads and it did not crash.

thank you for your reply. the thing is that my current setup employs nextcloud for for md file sync. and it worked like a charm on my oneplus 8 pro. Would be lovely if we could fix that somehow. also for the other uses who have "unsupported" phones along with nextcloud.

thank you!

cnrpman · 2022-08-20T12:54:02Z

@ramboe @Jael-Tactaquin @deGrasi
So all of you are using nextCloud with paths in shape of /Android/media/com.nextcloud.client/nexcloud/user@server.de%2Fnextcloud/ ?
We are doing overhaul on the special character handling. Hopefully would be fixed after that.

Tamriel · 2022-08-20T17:49:14Z

@ramboe @Jael-Tactaquin @deGrasi So all of you are using nextCloud with paths in shape of /Android/media/com.nextcloud.client/nexcloud/user@server.de%2Fnextcloud/ ? We are doing overhaul on the special character handling. Hopefully would be fixed after that.

Yes. Only when I move my Logseq folder out of that folder it works (using Logseq 0.8.1).

icksky · 2022-08-23T10:27:45Z

/Android/media/com.nextcloud.client/nexcloud/user@server.de%2Fnextcloud/

maybe the subfolder of Android has private permissions? I have try 0.8.1, not crashed, but nothing happened too.

rsudev · 2022-08-30T12:56:25Z

When 'favoriting' a folder in nextcloud, it is (at least for me) put into internal storage (in my case into nextcloud/user@server%2Fnextcloud/Documents/logseq)
If I select this item through the nextcloud content provider, I get the error message that 'content:...' urls are not supported. If I select through internal storage, it comes up empty. Looking with the file manager, a folder nextcloud/user@server/nextcloud/Documents/logseq was created and an empty logseq space set up there (using 0.8.2 beta).
Might give a hint what to look for in the code. To me there seems to be even a bug in Android involved, because after selecting the first mentioned item and giving permission, obviously I agreed to creating the second one unknowingly...

My system: Sony H8416, Android 10 (Build 52.1.A.3.92, rooted)

andelf added the mobile:android label Jan 7, 2022

aadilayub mentioned this issue Jan 24, 2022

Android Beta 0.5.9 crashes when granting folder permission #3972

Closed

MrModest mentioned this issue Feb 10, 2022

Android Client Crashed When Grant Permissions #4158

Closed

cannibalox mentioned this issue Apr 19, 2022

[android 0.6.5+] page names with reserved character will cause errors #4972

Closed

aadilayub mentioned this issue Apr 25, 2022

[Android 9] Logseq Android mobile app quits when assigning folder #5038

Closed

andelf mentioned this issue Aug 11, 2022

fix(android): handle home uri when picking folder #6328

Merged

andelf added the fixed-next-release ✅ Fixed, will be in the next release label Aug 11, 2022

andelf closed this as completed in #6328 Aug 11, 2022

Can't open local folder on Android #3789

Can't open local folder on Android #3789

Comments

aadilayub commented Jan 6, 2022 • edited

koan-github commented Jan 7, 2022

Philogicatician commented Jan 7, 2022

vivew commented Jan 22, 2022

koan-github commented Jan 23, 2022

aadilayub commented Jan 24, 2022

vivew commented Jan 24, 2022

MrModest commented Jan 29, 2022 • edited

ketoxime commented Mar 14, 2022

natrius commented Mar 21, 2022 • edited

joebroesel commented Mar 28, 2022 • edited

aadilayub commented Apr 24, 2022 • edited

aadilayub commented Apr 24, 2022 • edited

natrius commented Apr 24, 2022

aadilayub commented Apr 25, 2022

natrius commented Apr 25, 2022

SkyLull commented Apr 25, 2022

Reproduce

Device Info:

aadilayub commented Apr 26, 2022

aadilayub commented Apr 26, 2022 • edited

MrModest commented Apr 26, 2022

MrModest commented Apr 26, 2022 • edited

bbigras commented Aug 10, 2022

andelf commented Aug 10, 2022

efade commented Aug 10, 2022

andelf commented Aug 10, 2022

andelf commented Aug 10, 2022 • edited

bbigras commented Aug 10, 2022

bbigras commented Aug 10, 2022

andelf commented Aug 10, 2022

MrModest commented Aug 10, 2022 • edited

MrModest commented Aug 10, 2022 • edited

andelf commented Aug 11, 2022

efade commented Aug 11, 2022

andelf commented Aug 11, 2022

andelf commented Aug 11, 2022

bbigras commented Aug 11, 2022

bbigras commented Aug 11, 2022

MrModest commented Aug 11, 2022

ramboe commented Aug 14, 2022

Jael-Tactaquin commented Aug 14, 2022

deGrasi commented Aug 15, 2022

ramboe commented Aug 16, 2022

Jael-Tactaquin commented Aug 17, 2022

ramboe commented Aug 20, 2022

cnrpman commented Aug 20, 2022

Tamriel commented Aug 20, 2022 • edited

icksky commented Aug 23, 2022 • edited

rsudev commented Aug 30, 2022 • edited

aadilayub commented Jan 6, 2022 •

edited

MrModest commented Jan 29, 2022 •

edited

natrius commented Mar 21, 2022 •

edited

joebroesel commented Mar 28, 2022 •

edited

aadilayub commented Apr 24, 2022 •

edited

aadilayub commented Apr 24, 2022 •

edited

aadilayub commented Apr 26, 2022 •

edited

MrModest commented Apr 26, 2022 •

edited

andelf commented Aug 10, 2022 •

edited

MrModest commented Aug 10, 2022 •

edited

MrModest commented Aug 10, 2022 •

edited

Tamriel commented Aug 20, 2022 •

edited

icksky commented Aug 23, 2022 •

edited

rsudev commented Aug 30, 2022 •

edited