This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Work around crash with no deployment key in config.xml #110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM! |
2 similar comments
|
LGTM! |
|
LGTM! |
|
LGTM |
This was referenced May 4, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The crash itself was coming from attempting to save away some information in an NSDictionary with a nil value.
After some discussion, we decided that at this time, it would be best to no-op the reporting in the case where config.xml deployment key is not set, as this is consistent with the behaviour of the react native plugin, and it unblocks this scenario.
@lostintangent @dlebu @geof90