-
-
Notifications
You must be signed in to change notification settings - Fork 875
fix: MacOS command line app crashes if Parse framework is installed in /Library/Frameworks/
#1395
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
fix: MacOS command line app crashes if Parse framework is installed in /Library/Frameworks/
#1395
Conversation
…uld crash if the Parse Framework is installed in /Library/Frameworks, which results in the framework accidentally being filtered out and thus not having its subclasses properly registered.
Could anyone take a look at this? - @mrmarcsmith @jjmaceda @kennic |
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? |
Sorry, I've been very busy lately. Will try to take a look into that when I can get a chance. |
I wonder who is assignees and managing this repo? |
@ShawnBaek see #1356 |
This reverts commit 68a39d1.
Thanks for opening this pull request!
|
@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. |
@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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I can king of would be a test, if that is possible at all for this kind of change?
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] |
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. |
The same test keeps failing, but I noticed that it also failed before this PR, so I think we are good to merge. |
I think we can merge this, but the carthage CI is currently failing, so we may have to address this first. |
@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. |
I just approved the workflow to run, let's see... |
I will reformat the title to use the proper commit message syntax. |
Carthage support has been removed, so if the CI passes, we can merge this finally |
@mtrezza great! I won't have to keep applying my patch any longer 😂. Hopefully the tests will pass. 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! The failing macOS test is a flaky one.
Parse/Parse/Internal/Object/Subclassing/PFObjectSubclassingController.m
Outdated
Show resolved
Hide resolved
19b9ce1
/Library/Frameworks/
I will reformat the title to use the proper commit message syntax. |
/Library/Frameworks/
/Library/Frameworks/
## [2.0.2](2.0.1...2.0.2) (2023-01-30) ### Bug Fixes * MacOS command line app crashes if Parse framework is installed in `/Library/Frameworks/` ([#1395](#1395)) ([54bc6f3](54bc6f3))
🎉 This change has been released in version 2.0.2 |
This PR Resolves issue #1391 where a macOS Command Line App will crash when the Parse Framework is installed in
/Library/Frameworks/