[iOS] Uploading a Photo into a Vault from "Photos" causes null filename to be generated about cryptomator-ios HOT 7 CLOSED

regarding a) So the notification for access permission pops up, you cancel it and then... it goes back to the "Vaults list"? And you would expect it to remain in the same screen? If that's the case, it really is a bug and I'll look into it! :) Otherwise could you please elaborate on this?

regarding b) The problem here is that I'm not able to retrieve the original filename. It's technically impossible (at least to my knowledge, I was surprised as well). What I can get is the creation date/time of that photo. Or at least that's what I thought... and that should be there instead of "(null)". So this is also a bug, I guess I'll just use the current date/time for this "null" case.

Thanks for reporting!

from cryptomator-ios.

Nope, I accepted it, but that action didn't result in bring up the "Photos" library, it just took me back to my default vault screen. Its like the hook for "Ok" actually has some issue bringing up the library, or can't find it. However, the second time around it works fine. I'll see if I can do a quick video capture to detail it.

from cryptomator-ios.

Alright! I'll try to reproduce this. Should hopefully be an easy bug to fix. :)

from cryptomator-ios.

Last thoughts: I am unable to reproduce because even if I turn off access to "Photos" via the Settings panel, delete the app and reinstall I'm presented with a different screen-- shows the lock icon and reports that I've disabled access to Photos via settings. I've tried deleting and rebooting, but that preference seems to be persistent in the container. :) I have no idea how to help you reproduce.

from cryptomator-ios.

Haha, hopefully I can reproduce it in the simulator! Still working on other stuff right now, but I'll get back to you, if I know more. :D

from cryptomator-ios.

Unfortunately I can't reproduce it in the simulator. It's going straight into the Photos library. (Don't mind the black screen, it's only in the simulator.) And I can't test it on my devices anymore. I'll keep this issue in mind, when I have the chance to use Cryptomator on a new device! But I think it's not that critical anyway. ;)

The other issue with "(null)" will be fixed in the next update. Stay tuned!

from cryptomator-ios.

Closing this for now, because the "(null)" issue has been fixed a long time ago and the other one remains irreproducible.

from cryptomator-ios.