The Code Kitchen
The Code Kitchen
We also seem to be having an issue that relates to this [Stack Overflow issue](https://stackoverflow.com/questions/5657411/android-getting-a-file-uri-from-a-content-uri) where we are getting a content URI instead of a file URI since changing "dir.String()"...
@andydotxyz perhaps you can provide some background here. It seems like the following snippet from android.c is a candidate for where things went wrong, but I'm curious what is calling...
Actually the function right above it looks even more potentially guilty given the context of UTF-8 characters being improperly decoded... ``` const char* getString(uintptr_t jni_env, uintptr_t ctx, jstring str) {...
> I think the URL-encoded semicolons are a red herring. If you're seeing ErrOperationNotSupported, as I am, that's coming from `internal/driver/mobile/repository.go`. It's returned when you attempt to do a Parent...
> Test such a change. I don't think it will work. "content://" isn't just an annoying scheme sitting on top of "file://" - it is referencing a content media database...