Skip to content

Conversation

levigroker
Copy link
Contributor

Additional safety check related to #1090

It seems the given `bundle` object may not be an NSBundle at times (appears to be capable of being at least an NSString), so we check to ensure the given parameter is of the expected type before we attempt to send a message with a potentially unkown selector.
@levigroker
Copy link
Contributor Author

Thanks!

@levigroker levigroker closed this Mar 9, 2017
@levigroker levigroker reopened this Mar 9, 2017
@flovilmart
Copy link
Contributor

Sorry, I forgot to merge that one because of the travis failures :/

@flovilmart flovilmart merged commit e0e36ca into parse-community:master Mar 31, 2017
@levigroker
Copy link
Contributor Author

No worries. Thanks!

@levigroker levigroker deleted the bundle_check branch March 31, 2017 22:40
tkhoa87 added a commit to notabasement/Parse-SDK-iOS-OSX that referenced this pull request Apr 10, 2017
…1.14.4

* commit 'b5c49540caf930dbaf47a9c0f07cddac6cdd9674':
  Parse 1.14.4 (parse-community#1131)
  Custom File Upload Controller (parse-community#1114)
  transfer code
  Bundle check (parse-community#1119)

# Conflicts:
#	Parse/Internal/Object/Subclassing/PFObjectSubclassingController.m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants