Hrm, that’s unexpected, it’s using the same system to save files as Krita does. I don’t have much an idea for why that could be now.
Did you install Krita through the Play Store and does it maybe work properly if you install it via an APK as well? You should be able to download that from the krita.org website.
Yeah, I know it’s weird. To exclude the krita version issue, I’ve just reinstalled it from play store and installed via apk, both still the same error.
Alright, thanks. I’ll see if I can maybe find some kind of difference between how the two handle it. If not, I’ll just add some more logging to the file saving so that there’s a chance of figuring this out, we need to rebuild the frameworks for other reasons anyway.
Really appreciate your work!
I think I found the problem. Krita checks whether a file is writable before it starts saving and I guess on your device the operating system doesn’t implement this correctly and always says no. Drawpile doesn’t have this check and evidently it can write to the files fine.
Could you check if this APK fixes your problem? https://invent.kde.org/graphics/krita/-/jobs/4091141/artifacts/file/_packaging/krita-arm64-v8a-5.4.0-prealpha-d474343f-debug.apk
I just removed that check on Android, which shouldn’t cause terrible problems. The main difference is that if the file is actually not writable, you now get an error at the end of the save process instead of at the start, but that’s obviously better than not being able to save anything.
Yes, this finally solve the problem. Thank you! (BTW, when would this version be officially released?)
Cool, thanks for testing it. It should be in 5.3.0 Beta 3 and will be fully released with the final release of 5.3.0. That’s supposed to come later this month, if it doesn’t somehow needs to get pushed back.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.
