iOS App crashes when saving image


#1

With the current build of Cryptomator (1.3.0 528) I can’t save images to my photoroll. The app crashes immediately. I can save to the iOS files app but not direct into photoroll. Latest iOS (1.3.0) on iPhone 7


#2

Im using the same iOS App and cannot reproduce it.
(iPhone 7 plus and OneDrive)
Question: did you use a desktop app to encrypt the photos? If yes, which version?
Which storage provider do you use?


#3

I’ve used the desktop version (1.3.2 ) to encrypt the image.

The storage is iCloud Drive (in Cryptomator folder).


#4

I’ve tried also to soft reset the iPhone, de-install Cryptomator, install again and still have the same issue.

I’ve tried with both .png and .jpg.

Currently I save images to the files app first as a workaround.


#5

Can you try desktop version 1.3.3 or newer?
I use 1.3.3


#6

Will do tomorrow and let you know. Thanks so far!!


#7

Ok. I tested it also with iCloud. Same result. No problems.


#8

You can find the crash log by following the guide “Getting Crash Logs Directly From a Device Without Xcode” at: https://developer.apple.com/library/content/qa/qa1747/_index.html

  • Open Settings app
  • Go to Privacy, then Diagnostics & Usage
  • Select Diagnostics & Usage Data
  • Locate the log for Cryptomator. The logs will be named in the format: Cryptomator_<DateTime>_<DeviceName>
  • Select the desired log. Then, using the text selection UI select the entire text of the log. Once the text is selected, tap Copy
  • Paste the copied text to Mail and send to support@cryptomator.org

#9

It seems I’m using the latest macOS version already (1.3.2). There is no download for 1.3.4 available on macOS.

However, just downloaded the desktop version again, uploaded a png image into a desktop-created folder, opened the image on iOS and the app crashes when saving to camera roll.

I’ve sent a log file to support this morning.


#10

Thank you for the crash report, it helped us identifying the issue. Saving to the photo library requires something new from us since iOS 11. We’ll fix it in the next version and release it as soon as possible.


#11

Even I was facing this problem but it was intermittent. After a few attempts of the same action, the problem resolved itself.