On my Oculus Go, I am trying to access a file in the persistentDataPath which is typically Android > data > package name (com.name.whatever) > files > whatever file, but when I build from Unity to my Go, my package name does not appear anywhere in my Android File Transfer. I cant seem to find a "Unknown Sources" folder (This is where the apk is apparently being run from) in my Android File Transfer GUI. Any ideas on how I could access that path and add a file there?
We typically deploy white-label apps for on-site installations rather than public distribution through the Oculus Store. In some cases the client machines don't have internet access at all. Our standard procedure has been to sideload APKs, and then store a config file along with some external assets (360 videos etc) in the com.company.application directory. It would be useful to be able to use this same methodology on Go.
We have found that using the Alpha/Beta functionality to deliver the APK does enable this local filestore location. But when sideloading the APK (during debugging for example) it seems to be impossible to access whatever folder is being used to store files.
Just wanted to add that this would be helpful in my use case as well. We have developed an app for a traveling exhibit and in the past using Gear VR we integrated Goggle Analytics (Firebase Analytics now) and sometimes there will be no connectivity for the headsets to upload the analytics data. Supposedly this data is cached using the Firebase SDK and uploaded when connectivity is available but from testing this feature doesn't always seem to work. So I am also writing to a local text file data that mirrors the analytics data so that our client can grab the file easily and compare to the cloud analytics. There are a few other scenarios that access to the app package directory would be helpful but since I am working on this feature now its the first use case I can think of. My solution involves writing to the Download folder on the Go instead of the persistentDataPath.
