fix: macOS command line app crash

[JohnCaccavale]

This PR Resolves issue #1391 where a macOS Command Line App will crash when the Parse Framework is installed in /Library/Frameworks/

[TomWFox]

Could anyone take a look at this? - @mrmarcsmith @jjmaceda @kennic

[mrmarcsmith]

Thanks @JohnCaccavale for this PR! I know this may be difficult given the nature of this PR but can you think of any way to write a test to ensure current and future functionality?

[JohnCaccavale]

Sorry, I've been very busy lately. Will try to take a look into that when I can get a chance.

[ShawnBaek]

I wonder who is assignees and managing this repo?

[acinader]

@ShawnBaek see https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1356

[parse-github-assistant[bot]]

Thanks for opening this pull request!

• ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

[JohnCaccavale]

@mtrezza I see this PR is still available. Please let me know if you would be able to review and if there's anything else that would be needed from me.

[mtrezza]

@mrmarcsmith could I add you to the team of Parse ObjC SDK reviewers? The group gets a notification when a PR is ready for review.

[JohnCaccavale]

Yeah, I wasn't sure about how to setup a test for this type of scenario when I originally opened up the PR either. But, this fix had addressed my issue, which I've been using in my local branch since the PR was originally opened. Quite some time now. I would be concerned if this fix broke existing tests, which currently I'm seeing one macOS test failing, but not sure if thats a flaky test or not.

Failing tests:
	ParseUnitTests-macOS:
		-[AnonymousUtilsTests testLogInViaBlock]

[mtrezza]

Let's see whether the test passes in rerun, but I think this is good to merge also without test which may be difficult to implement.

[mtrezza]

The same test keeps failing, but I noticed that it also failed before this PR, so I think we are good to merge.

[mtrezza]

I think we can merge this, but the carthage CI is currently failing, so we may have to address this first.

[JohnCaccavale]

@mtrezza Just saw your message, I'm off from work today, let me know if there's anything I can do. I see there was a recently a PR merged with regards to increasing the time out of the carthage CircleCI timeout, I'm hoping that would help address the failure being shown here.

I pulled in your latest changes with regards to that fix that was merged. The tasks are currently running, will keep an eye on that status of them.

[mtrezza]

I just approved the workflow to run, let's see...

[parse-github-assistant[bot]]

I will reformat the title to use the proper commit message syntax.

[mtrezza]

Carthage support has been removed, so if the CI passes, we can merge this finally

[JohnCaccavale]

@mtrezza great! I won't have to keep applying my patch any longer 😂. Hopefully the tests will pass. 🤞

[parse-github-assistant[bot]]

I will reformat the title to use the proper commit message syntax.

[parseplatformorg]

🎉 This change has been released in version 2.0.2