Tocropviewcontroller: Permission denied portName:'com.apple.iphone.axserver

Created on 20 Jan 2020 · 7Comments · Source: TimOliver/TOCropViewController

Error Code

[AXRuntimeCommon] AX Lookup problem - errorCode:1100 error:Permission denied portName:'com.apple.iphone.axserver' PID:6723 (
0 AXRuntime 0x00000001af41e3a0 539C8041-A10E-3612-AAE6-420FCB339466 + 267168
1 AXRuntime 0x00000001af3e3164 _AXGetPortFromCache + 548
2 AXRuntime 0x00000001af3e459c AXUIElementPerformFencedActionWithValue + 392
3 UIKit 0x00000001dac71720 033842C5-1173-3112-ABCE-25D066CFFADB + 800544
4 libdispatch.dylib 0x0000000105e85e1c _dispatch_call_block_and_release + 32
5 libdispatch.dylib 0x0000000105e8727c _dispatch_client_callout + 20
6 libdispatch.dylib 0x0000000105e89af0 _dispatch_queue_override_invoke + 924
7 libdispatch.dylib 0x0000000105e98aa0 _dispatch_root_queue_drain + 356
8 libdispatch.dylib 0x0000000105e9940c _dispatch_worker_thread2 + 144
9 libsystem_pthread.dylib 0x00000001a49ff690 _pthread_wqthread + 216
10 libsystem_pthread.dylib 0x00000001a4a059e8 start_wqthread + 8
)

which is freezing up the application whenever I call dismiss on the cropper from delegate method func cropViewController(_ cropViewController: CropViewController, didCropToImage image: UIImage, withRect cropRect: CGRect, angle: Int) {

}

No solution found as of yet. Makes the library unusable.

Tested with xCode 11.3.1
And iPhone 11 Pro iOS 13.3

Tested with iPad Pro Simulator 12.2 and the issue does not occur. The library works as intended. Calling dismiss on the cropper view dismisses properly and doesn't freeze up the application

Tested with iPad Pro Simulator 13.3 and the issue does occur. It seems to be related to iOS 13.3

It appears for some reason the transition view isn't being dismissed which overlays the screen and prevents it from being tapped. So although the app isn't technically freezing the drop shadow is preventing any further action and can't be removed
Screen Shot 2020-01-19 at 10 57 19 PM

Architecture/Process -> Navigation Controller -> Root View Controller -> Pushed View Controller -> Presented View Controller -> Presented Native UIImage Picker View Controller -> Got Image and Dismissed Picker -> In Completion of dismiss present Swift based CropViewController -> Crop Image and hit done -> Delegate method didCropToImage called -> Dismiss CropViewController

The next thing that happens is odd. The CropViewController gets dismissed but so does its parent and what is left behind is a transition view which covers the whole screen so no further actions can be taken

UPDATE: It seems to only affect view controllers that are presented "over current context". Presenting on a full screen viewcontroller works fine

bug pr requested

Source

ojseven

😕1

Most helpful comment

Having the same problem while loading the Flutter module screen in iOS app.

lovekeshsaxena on 30 Nov 2020

👍5

All 7 comments

@ojseven Thanks for the extremely thorough bug report! I'm sorry you've been experiencing issues with it.

Hmm, so with that update, did you mean to say you modified the crop controller to change its modal presentation mode to "over current context" or is it the parent view controller in the background with that mode?

Hmm, truth be told, if it's an iOS 13 bug, I'm not sure how easy this is to fix.

TimOliver on 27 Jan 2020

Has anybody found a solution to this problem?

I am getting a similar error:

AX Lookup problem - errorCode:1100 error:Permission denied portName:'com.apple.iphone.axserver' PID:481 (
    0   AXRuntime                           0x00000001b8d363a0 905DC921-AFE6-3398-A0CF-AC3372C35897 + 267168
    1   AXRuntime                           0x00000001b8cfb164 _AXGetPortFromCache + 548
    2   AXRuntime                           0x00000001b8cfc59c AXUIElementPerformFencedActionWithValue + 392
    3   UIKit                               0x00000001e45c96f8 F5079CB4-6E07-3DFE-81CA-B8667B73F64C + 800504
    4   libdispatch.dylib                   0x00000001013ede1c _dispatch_call_block_and_release + 32
    5   libdispatch.dylib                   0x00000001013ef27c _dispatch_client_callout + 20
    6   libdispatch.dylib                   0x00000001013f1af0 _dispatch_queue_override_invoke + 924
    7   libdispatch.dylib                   0x0000000101400aa0 _dispatch_root_queue_drain + 356
    8   libdispatch.dylib                   0x000000010140140c _dispatch_worker_thread2 + 144
    9   libsystem_pthread.dylib             0x00000001ae303690 _pthread_wqthread + 216
    10  libsystem_pthread.dylib             0x00000001ae3099e8 start_wqthread + 8
)

aymather on 7 Jun 2020

Same problem as of 2020/06/11

mannerism on 11 Jun 2020

Thanks for the +1s folks, but unless someone can provide more information (Or ideally, a test app that reproduces this problem), there's not a lot that can be done here.

I've been able to replicate the breaking transition view when setting the presentation context to .overCurrentContext, but considering this view controller is hard coded to be .fullScreen, I'd say that that issue is out of scope. (And if it's not, it should ideally be tracked in a different issue).

I'm not convinced this is an issue that can be solved on the code level of this library. Considering we're on the cusp of iOS 14 now, I'm going to leave this issue as "pr requested", and if no one can reliably recreate the issue in a test app, I'm going to close the issue, and we can revisit it later if it becomes more widespread.

Thanks!

TimOliver on 11 Jun 2020

I'm experiencing the same error when overlaying a view in SwiftUI on Beta 6. App functions just fine though.