Fixed incorrect AppExitReason documentation #46
Merged
Conversation
This file contains hidden or 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
Sorixelle
requested changes
Aug 18, 2025
Signed-off-by: Joel Crane <[email protected]>
Sorixelle
force-pushed
the
fix-app-exit-reason
branch
from
de635e0 to
be7ddab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
app_exit_reason_set(APP_EXIT_ACTION_PERFORMED_SUCCESSFULLY);does not work.This works (found in the Pebble one click action example):
exit_reason_set(APP_EXIT_ACTION_PERFORMED_SUCCESSFULLY);This updates the erroneous documentation, which is perhaps based on an earlier or unreleased version of the SDK.