>> Is it an https/http error?
No, this is a simple tcp socket intended to send and receive plain text.
>> Yes, you would create a new test target and add all the GUI stuff as a
>> member of the test target...
I have created a dummy GUI app, and I made the TcpClient a property of the
Yes, you would create a new test target and add all the GUI stuff as a member
of the test target. Of course, you will want to exclude them from other
targets. You shouldn’t need to do any library linking since it is a common
codebase. Simply include the classes and put the glue code in the App
Is it an https/http error?
On iOS, we have to add an exception in the info.plist for ATS (Application
Transport Security) to allow http traffic.
Is there anything similar on the Mac?
Sent from my iPhone
> On Dec 12, 2019, at 12:58 PM, Jens Alfke via Cocoa-dev
> wrote:
>
>
>
>> On Dec
Thanks - I just finished doing that. I stubbed out a simple main that has
enough smarts to use this TcpClient the way it will be used in the real app,
and I was able to connect to an instance of the server to which the command
line tool needs to connect. This server is running on another
I would first test to see if you can access networking at all—i.e. connect to a
public HTTP server and see if it works. If it doesn’t, then you are probably
running against the entitlements issue. I suspect that the “dummy target”
indicated is simply a GUI app wrapper built just for testing but
The errno is 13 (which I think is just a generic Permission Denied).
I am connecting to localhost.
I did find this post in the Apple Developer Forums
(https://forums.developer.apple.com/thread/52211):
How do I unittest a command line application? |Apple Developer
So I did - and it did pass the MAS review. Thanks.
On Thu, Dec 12, 2019 at 12:35 PM Shane Stanley
wrote:
> On 12 Dec 2019, at 12:52 am, Torsten Curdt via Cocoa-dev <
> cocoa-dev@lists.apple.com> wrote:
> >
> > I am not sure - is there a better place to ask questions about
> codesigning
> > and
