Open rubenvereecken opened 2 years ago
We can't release new builds until we figure something out for this one. After almost a week, no workarounds have been found.
Edit: This may help the maintainer: https://developer.apple.com/documentation/xcode/diagnosing-memory-thread-and-crash-issues-early
same here
Im having the same problem too
I managed to temporarily work around this by downgrading to XCode 13.2.1.
+1 will downgrade as well...
Same issue too, plus getting other issues with latest Xcode now. Downgrade it will have to be.
I was seeing this on Xcode Cloud builds, but after I applied the segmentation fault fix, it started working again:
https://github.com/zhangao0086/DKImagePickerController/issues/695
+1, How could I fix it?
Found what causes the problem. It is UI_USER_INTERFACE_IDIOM()
should be replaced with UIDevice.current.userInterfaceIdiom
in following files:
I will submit PR and hope that the owner will merge it.
Edit: It is already changed here #696 but is not tagged. @zhangao0086 please release new version with that commit included.
@dneykov Updated: https://cocoapods.org/pods/dkimagepickercontroller. Sorry for the late response to all 😢
is this release live?
We have a compilation issue with
DKImagePickerController
that only started happening since we upgraded to a later MacOS & XCode (which we had to do for adhoc iOS 15+ builds), which we only did to support newer iOS versions better. I know this is in essence a Swift compilation issue, but I read up on it and apparently there are coding patterns that blow up Swift's memory usage during compilation.In short, I'm using
Relevant bits of
Podfile.lock
(we're on the latest):Technically this can be worked around using
-Onone
, but we can't use un-optimised builds for release.