You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup: keep the app open on the results page, but leave it in the background
Issue: Two old notification messages were on my home screen, so clicking them opened the app, but did not direct me to the pages where experiences are available. I'm not sure why that is (whether the link to the incident is broken), or if we tried to just redirect people to the '/' home route
The text was updated successfully, but these errors were encountered:
youralien
changed the title
Push notification does not send me to the home screen
Push notification does not send me to a place where I can participate
Aug 9, 2018
// should be// let route = `apicustom/${iid}/${incident.eid}/${needName}`letroute="apiCustom/"+iid+"/"+needName;notifyForParticipating(newUsersUids,iid,"Event "+experience.name+" is starting!",experience.notificationText,route);
One hack is to route users to the home page. This requires one extra step to participating. However, it always ensures they see participation screens they are assigned to
If we send them to the participate route, but they are no longer assigned, they shouldn't be able to participate. If they were asked to participate, but no longer are assigned, this route could redirect them to a page that apologizes that they missed the opportunity to participate. This is related to Issue User is available, push is sent, user updates location, assignments are cleared, user is not longer available #46. This would reduce the number of "apology notifications", and would only show this apology when they thought they could participate.
Setup: keep the app open on the results page, but leave it in the background
Issue: Two old notification messages were on my home screen, so clicking them opened the app, but did not direct me to the pages where experiences are available. I'm not sure why that is (whether the link to the incident is broken), or if we tried to just redirect people to the '/' home route
The text was updated successfully, but these errors were encountered: