[TIMOB-2481] iOS: Push Notifications Bug

GitHub Issue	n/a
Type	Bug
Priority	Trivial
Status	Closed
Resolution	Invalid
Resolution Date	2011-04-15T03:20:58.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	iOS
Labels	n/a
Reporter	Brice Lechatellier
Assignee	Reggie Seagraves
Created	2011-04-15T03:20:57.000+0000
Updated	2017-03-30T17:30:32.000+0000

Description

Hi,

I've tried the basic example below for push notifications, I get prompted to allow, then nothing happens, no error, no success, it fails silently. Unless I'm doing something wrong, the issue occurs on the latest 1.4 release as well as the latest 1.5 build.

Titanium.Network.registerForPushNotifications({
    types: [
        Titanium.Network.NOTIFICATION_TYPE_BADGE,
        Titanium.Network.NOTIFICATION_TYPE_ALERT,
        Titanium.Network.NOTIFICATION_TYPE_SOUND
    ],
    success:function(e)
    {
      alert(e.deviceToken);
    },
    error:function(e)
    {
        alert(e.error);
    },
    callback:function(e)
    {
        alert("Received a push notification\n\nPayload:\n\n"+JSON.stringify(e.data));
    }
});

Comments

tom quas 2011-04-15
works w/ 1.5.1. ticket can be closed.
Stephen Tramer 2011-04-15
Possibly due to jailbreaking, and Push was tested extensively with 1.6.0GM. Invalidating.
Tim Keir 2013-03-04 I'm receiving this same silent error with no callbacks using the latest 3.0.2 SDK with Alloy. My iPad 3 prompts for permission but clicking accept silently sets the push within Settings/Notifications but returns no error or success callback (and obviously no deviceToken!). What's the resolution? My device is definitely not jailbroken. Furthermore what's the workflow for de-registering the device so that I can prompt for push notifications again? Uninstalling then changing the system clock forward 24 hours doesn't seem to work on iOS 6?
Lee Morris 2017-03-30 Closing ticket as invalid.

JSON Source