Notification improvements #1175
No reviewers
Labels
No labels
android: closed alpha
android: open beta
app-parity
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
creator
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
product review
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-android#1175
Loading…
Reference in a new issue
No description provided.
Delete branch "notification-improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number: #1142 DON'T CLOSE
What is the current behavior?
What is the new behavior?
Other information
I used the back stack entry count here because not all the fragments we display are added to the back stack. If you're 100% sure this will still work regardless, then this is ok. Everything else looks good.
That part of the code was giving me problems because after the first time I clicked on a notification and wanted to view some other content, there was a silent IndexOutOfBoundsException. I think that silent exception -I mean, catched, but nothing else- could be related to notification items not working when clicked.
I tested this new code for this bug, but not in other conditions. I will be debugging it for longer and commit and request another review if needed.
Latest commit
96606f5
simplifies getting the fragment which is currently on main activity by querying the OS for it. Main activity is using a frame layout as a parent layout where fragments can be added. That allows app to simply request which fragment is there, instead of travelling the backstack or the list of fragments.Looks good. Thanks.