Fix nil pointer panic #94
Open
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
|
|
change log message type Co-authored-by: Johnny <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When receiving an update from the Telegram API that is not related to a new message, the app crashes with a nil pointer error. This happens because the code assumes that every update has a non-nil Message field, which is not always the case.
Change Description:
• Added a condition to check if the Message field in the update is nil.
• Logged a message (“memo message is nil”) and safely returned early when the condition is met.
• This prevents the app from crashing due to a nil pointer error when the update is not about a new message.
Impact:
• Ensures the app handles updates without a Message field gracefully.
• Improves the app’s robustness by avoiding unnecessary panics.