search

Pushwoosh / pushwoosh-appcelerator-titanium

Other
33 stars 16 forks source link

iOS: Push notifications dialog does not show since v5.8.0 #69

Closed tomgiessel closed 5 years ago

tomgiessel commented 5 years ago

Hi there,

I am trying to update my Pushwoosh module from currently v5.5.5 to a newer version. With the current version (v5.5.5) everything works as expected. As soon as I use ANY newer version of the module (v5.8.0 up to v5.13.2), Pushwoosh does not prompt me with the permission dialog. Hence the callbacks for registerForPushNotifications are never called. I was unable to find any hints why this is the case. I even tried the sample app with the same result.

Tested on iPhone 6s with iOS 12.2 using different Titanium versions: 7.5.0, 7.5.2 and 8.0.0

Cheers, Tom

wfhm commented 5 years ago

@tomgiessel Hi,

This is really strange, I've tried reproducing the issue with the latest version and it works just find for me (Titanium SDK 7.5.2GA and 8.0.0). By any chance may I ask you to try our Titanium sample app and let us know if the issue is reproducible with it?

wfhm commented 5 years ago

@tomgiessel any updates?

tomgiessel commented 5 years ago

@wfhm Hi,

I experience the same issues with the Titanium sample app. When I use v5.5.5 of the Pushwoosh module + remove the geozones module it works as expected and I see the dialog. Here is what I see when using the sample app (untouched), no error, no nothing:

Bildschirmfoto 2019-04-23 um 10 54 52

Image from iOS

wfhm commented 5 years ago

Hello @tomgiessel ,

I am sorry for the delay in correspondence. I have just tried the sample and it still works just fine: IMG_1773

Could it be related to some configurations of your app? Could it be that push notifications are not enabled in Apple Developer portal for the App ID you use?

tomgiessel commented 5 years ago

Hi @wfhm,

unfortunately I don't see any configuration issue. As I said, as soon as I revert back to the v5.5.5 of the Pushwoosh module, it all works fine again. I will look more into this once I am working on the mobile app again. For now I have no idea whats causing this.

wfhm commented 5 years ago

@tomgiessel Did you manage to make it work with one of the latest releases? Also, the latest versions of the module now use FCM for Android, so it is strongly recommended to use 5.13.+ versions, otherwise Android might work incorrectly.

wfhm commented 5 years ago

Closed until there is more data to work with.