Skip to content
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

pushOpened event not fired on iOS #6

Closed
Exilz opened this issue Dec 19, 2016 · 10 comments
Closed

pushOpened event not fired on iOS #6

Exilz opened this issue Dec 19, 2016 · 10 comments

Comments

@Exilz
Copy link

Exilz commented Dec 19, 2016

DeviceEventEmitter.addListener('pushOpened', _pushHandler);

works on Android, but I can't get it to work on iOS. I still have to use the deprecated

Pushwoosh.onPushOpen(_pushHandler);

if I want my handler to work. Registering to push still works and tapping the notification properly opens the app.

Thanks for the help.

@DimanAM
Copy link
Collaborator

DimanAM commented Dec 21, 2016

DeviceEventEmitter.addListener('pushOpened', _pushHandler);

Should work on react-native@0.38.0 (used in sample project) and latest 0.39.2 version.

@franverona
Copy link

I'm having the same issue even with the solution proposed by @Exilz :(

@Exilz
Copy link
Author

Exilz commented Jan 9, 2017

@franverona I had to downgrade the plugin, I forgot to say that. 1.2.5 if I recall correctly.
I'm pretty sure the event isn't working properly with the latest version.

@franverona
Copy link

Still not working (on iOS; on Android works). Here is my code (I'm using 1.2.5 because the latest version isn't working either):

import React from 'react';
import { 
  AppRegistry, 
} from 'react-native';

import App from './app';

AppRegistry.registerComponent('MyApp', () => App);

var _pushHandler = function (pushData) {
  console.log(pushData);
};

var Pushwoosh = require('pushwoosh-react-native-plugin');

Pushwoosh.init({ 'pw_appid' : '1234-5678' , 'project_number' : '1234567' });
Pushwoosh.register(
      (token) => {
        console.log('✓ Registered for pushes');,
      (error) => {
        console.error('Failed to register: ' + error);
);

Pushwoosh.onPushOpen(_pushHandler);

@franverona
Copy link

Any news about this?

@franverona
Copy link

Hello Pushwoosh? :(

@wfhm
Copy link
Member

wfhm commented Feb 9, 2017

Small public update: the issue is being investigated via private support channel with @franverona, so as soon as we figure out something we will update this thread.

@franverona
Copy link

After almost two months of emails (15 emails and 4 different people looking for a solution), we decided to change our push notification provider because we weren't seeing any light at the end of the tunnel. In case that someone wants a working alternative using React Native, feel free to contact me for more information. I wish you all the best Pushwoosh.

-Fran

@wfhm
Copy link
Member

wfhm commented Mar 13, 2017

Hi @franverona!
It is sad to hear that you've decided to stop being our customer.
To sum up - the issue wasn’t reproducible on our Sample app. We were trying to investigate further with the code snippets provided but weren’t able to continue without full reproducer and console logs from the actual devices, which were not provided to us upon request.
We have also unsuccessfully tried to reach you on January, 31 and February, 09.
Please feel free to contact us again if you decide to go further with investigation.

@franverona
Copy link

Hi @wfhm,

Yes, you're absolutly right. You reached me on both dates and I honestly didn't answer you guys because we were involved in several projects (not only the one that I'd mentioned on the email). Maybe it was some incompatibility between Pushwoosh and some library, maybe an Android or iOS version, etc. There was so many factors and our client was pushing us so hard that we decided to change our provider.

Nothing personal, of course. Tech support was great, but deadlines were killing us and we needed a quicker solution (our client only wanted push notification, not advanced metrics, so our current provider is just fine for this). Maybe in a future if we need advanced features like you have, we'll switch again.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants