-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to differentiate bringing the app to the foreground via a notification tap #39
Comments
@pakoArtal were you ever able to figure this out? |
Hi @DFoxinator, To get notified, Login to jira and press 'Start watching this issue' on https://jira.appcelerator.org/browse/TIMOB-4865 I heard that the more people watching the issue the fastest they solve it .... |
@pakoArtal thanks a bunch, what you're saying makes sense. The way you were trying to do it with newintent listener is what I was trying to do too. I left a comment on the ticket asking about a workaround. This seems like very critical functionality, if in fact you literally can't properly open a Titanium app that's in the background from a push notification with a payload. |
You can do it yourself by using gcm.getLastData(); when you start the app Edit: Actually, couldn't get this to work. Seems there is indeed a need for some way to detect if user clicked on the notification or not. |
Agreed, this is critical functionality. Surprised this isn't included somehow?? |
Hi,
This is be related to the issue App open from PushNotification click without payload where @cjadhav and @DFoxinator ask about getting the payload on clicking on notification.
To differentiate bringing the app to the foreground via a notification tap from just bringing the app to the foreground normally, I have tried the following:
I have tried with no luck:
and
@FokkeZB opened a JIRA ticket :Android newintent event not fired so that could be reason I do not get it.
Do you know another way to do it?
The text was updated successfully, but these errors were encountered: