You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open SDKLauncher-Android and be able to view an EPUB
Observed behaviour
Instead, it tells me that it cannot find any EPUBs at a certain location on the local storage (not SD card). I am unable to put files in that location as it is an illegal path.
Steps to reproduce
First, open SDKLauncher-Android
Then notice that it tells you to put EPUBs in /storage/emulated/0/epubtest which is an invalid path (since "0" is not a valid folder name)
Product
Native application (Readium SDK C++)
Official "launcher" sample
Android—many versions; pulled from 'develop', June 10th 2016: version bump to 0.24.0-alpha
Additional information
Here is my original post to the Readium Slack channel
Has anyone gotten SDKLauncher-Android working lately? I’ve tested on a couple of devices and it gives me the toast message:
"/storage/emulated/0/epubtest is empty, copy epub3 test file please.”
However, I cannot create a folder named “0” as that is an illegal filename. And I have tried putting symlinks from within /storage to the SD card but they are apparently not followed. I have also tried changing the path where it looks to absolute paths on the SD card but again, no dice. I also added an intent to AndroidManifest.xml to be able to open EPUB with SDKLauncher-Android but I must’ve done it wrong, as it crashes when I try that.
The text was updated successfully, but these errors were encountered:
EPUBs must be placed within the SD card's "epubtest" folder. On my device, the path is "/sdcard/epubtest" — not "/storage/emulated/0/epubtest" as it was saying.
As soon as I placed EPUBs within the epubtest folder of the SD card, everything worked fine!
I've been bitten by this as well a couple times in the past.
Could the toast text be changed to more accurately specify the folder location? Is it OK to change it to "/sdcard/epubtest" or is that not always correct?
/storage/emulated/0/epubtest vs. /sdcard/epubtest
(same destination, different filesystem mount on some devices)
...the woes of Android FS, symbolic links, Java API etc.
but yes, I agree that the error message needs to help the user / tester fix the problem.
This issue is a Question
Expected Behaviour
Open SDKLauncher-Android and be able to view an EPUB
Observed behaviour
Instead, it tells me that it cannot find any EPUBs at a certain location on the local storage (not SD card). I am unable to put files in that location as it is an illegal path.
Steps to reproduce
Product
Additional information
Here is my original post to the Readium Slack channel
Has anyone gotten SDKLauncher-Android working lately? I’ve tested on a couple of devices and it gives me the toast message:
"/storage/emulated/0/epubtest is empty, copy epub3 test file please.”
However, I cannot create a folder named “0” as that is an illegal filename. And I have tried putting symlinks from within /storage to the SD card but they are apparently not followed. I have also tried changing the path where it looks to absolute paths on the SD card but again, no dice. I also added an intent to AndroidManifest.xml to be able to open EPUB with SDKLauncher-Android but I must’ve done it wrong, as it crashes when I try that.
The text was updated successfully, but these errors were encountered: