-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Crash preventation #4661
Crash preventation #4661
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
BOOL contentsOfProcessingPathRemoved = [self removeContentsOfProcessingPath]; | ||
BOOL contentsOfPendingPathRemoved = [self removeContentsOfPendingPath]; | ||
BOOL contentsOfDirectoryAtPreparedPathRemoved = | ||
[self removeContentsOfDirectoryAtPath:self.preparedPath]; | ||
BOOL contentsOfDirectoryAtActivePathRemoved = | ||
[self removeContentsOfDirectoryAtPath:self.activePath]; | ||
success = contentsOfProcessingPathRemoved && contentsOfPendingPathRemoved && | ||
contentsOfDirectoryAtPreparedPathRemoved && contentsOfDirectoryAtActivePathRemoved; |
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.
Here might be this type of form if you wish:
return [self removeContentsOfProcessingPath] & [self removeContentsOfPendingPath] & ... etc
But the above case is more friendly for debug imo =)
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.
We can declare success at the time we check for all the criteria:
BOOL success = contentsOfProcessingPathRemoved && contentsOfPendingPathRemoved &&
contentsOfDirectoryAtPreparedPathRemoved && contentsOfDirectoryAtActivePathRemoved;
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.
We can declare success at the time we check for all the criteria:
BOOL success = contentsOfProcessingPathRemoved && contentsOfPendingPathRemoved &&
contentsOfDirectoryAtPreparedPathRemoved && contentsOfDirectoryAtActivePathRemoved;
You are definitely right :)
Thanks!
@GUserx Thanks for the suggestions. We'd appreciate if you'd send separate PRs for different pods. In this case, a separate PR for the Installations versus Crashylytics would help with the review process. For the Installations change, please investigate the subsequent CI failure in https://travis-ci.org/firebase/firebase-ios-sdk/jobs/635952938
|
@paulb777 Thanks for your comment. |
Thanks. Note that CI did not run for Crashlytics because of the issue fixed by #4663 |
@GUserx thanks for the PR! We're going to run through some validation and review this PR later in the week after we've gone through with the first release |
Got it. Thank you for info. |
Fixes #4659