LBRYCommunity/lbry-android
1
0
Fork 0
Code Issues 155 Pull requests 6 Projects Releases 84 Packages Wiki Activity

handle remote notification payloads #737

Merged
akinwale merged 3 commits from notification-settings into master 2019-10-30 10:34:58 +01:00
Conversation 1 Commits 3 Files changed 5 +101 -17
akinwale commented 2019-10-24 13:44:25 +02:00 (Migrated from github.com)
Copy link
No description provided.
eukreign (Migrated from github.com) reviewed 2019-10-24 13:44:25 +02:00
tiger5226 (Migrated from github.com) reviewed 2019-10-28 01:23:31 +01:00
tiger5226 (Migrated from github.com) left a comment
Copy link

I took a look. Do you have a format that you are going to be expecting? I see type and url but there is no defined structure for this. Its app based outside of the standard notification.

I took a look. Do you have a format that you are going to be expecting? I see type and url but there is no defined structure for this. Its app based outside of the standard notification.
akinwale commented 2019-10-28 16:54:06 +01:00 (Migrated from github.com)
Copy link

@tiger5226 You can send data payloads along with the notification title and message. The payload is essentially a map of string keys/values.

https://stackoverflow.com/a/39179456/61385 explains the different possible message types.

@tiger5226 You can send data payloads along with the notification title and message. The payload is essentially a map of string keys/values. https://stackoverflow.com/a/39179456/61385 explains the different possible message types.
Sign in to join this conversation.
Reviewers
No reviewers
eukreign
Labels
Clear labels   
android: closed alpha

   
android: open beta

   
app-parity

   
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
area: proposal

Work is part of a proposal

  
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
creator

   
Epic

   
good first issue

   
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

   
icebox

Long-term storage

  
Invalid

   
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
on hold

Temporarily paused

  
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
product review

   
resilience

   
Tom's Wishlist

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-android#737
No description provided.
Delete branch "notification-settings"

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?