-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined symbol: _GCDAsyncSocketManuallyEvaluateTrust #2255
Comments
Should we even be needing patrol pods and doing build steps for patrol when running the non-test version of our app? I seem to have fixed it anyway. I think i was missing the CocoaAsyncSocket (7.6.5) pod completely, which is a necessary pod for patrol. Something I did added this to the podspec.lock:
I think it was I also needed this in
I already had it in Now my whole pod_install is:
Unrelated but I fixed my having to add |
Hi @BenjiFarquhar |
|
Without additional information, we can't resolve this issue. We're therefore reluctantly going to close it. |
1 similar comment
Without additional information, we can't resolve this issue. We're therefore reluctantly going to close it. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
Steps to reproduce
I can't run my app on iOS anymore (not even just the tests, the actual main app doesn't run).
Actual results
In the debug console:
The full error in Xcode is is for the job "Link Patrol (arm64)". Note that "Link Patrol (x86_64)" works. When i run
pod install
i always have to runarch x86_64 pod install
. Is my pod setup outdated?The pertinent part of the error:
The full error:
If i try to run it in Xcode I get the same errors, but they are under the Patrol folder:
Patrol version
patrol: ^3.9.0
Patrol Doctor output
Patrol Doctor output
Flutter Doctor output
Flutter Doctor output
The text was updated successfully, but these errors were encountered: