Push "remoteRegistration" not being received after build .2115

Solar2D iOS
#21

Following the steps I wrote earlier I can’t seem to fix it for my other device running iOS 6.x. So that fix perhaps only applies to iOS 7.x or was maybe a one time thing for me.

#22

I have verified that a userbase of thousands of users are experiencing the same issue with several different devices and iOS versions, so I don’t know if it is limited to the device/iOS version or if it is an issue with Corona.

Anderoth did you make any progress recently? I need to get ours resolved ASAP as we have thousands of users now complaining about the issue and need to get a fix for it out asap.

#23

I have not. I just moved back to build .2115. It works as it should. Build .2119 either has a code change or a build configuration change that causes the problem. All I could do was bug report it.

#24

Ah great! Will give it a try as well, thanks.

Edit: Thanks a lot, can confirm .2115 works for me as well. Saved my week =)

#25

Any news on this? The bug report or anyone from Ansca who can shed some light on any progress made? As it would be nice to be able to upgrade to a later Daily Build with functioning push notifications.

Thanks,

#26

Have you filed a bug report on this?  If not, I need you to.

Rob

#27

It has been done already, Anderoth filed one earlier with the id #29616. Any news on it?

#28

Running into this issue now as well on 2152. Confirmed working 2115.  

This should be top priority imho, posted in each daily build summary as a known issue until fixed. 

#29

@Corona, perhaps it is an issue with some push settings cache or something? Not sure how the internals of push notifications work but thousands of our users experienced this bug with the post .2115 builds. I managed to fix it on my own device somehow by resetting the notification settings for the app inside the iOS settings but that fix was only temporary and soon after I rebuilt my app and reinstalled it on my device it broke once again. The fix I wrote in my previous post worked on none of my other devices either and didn’t seem to work for anyone else besides a very lucky few and even then it was only temporary until next reinstall. But using build .2115 or one before that this bug seems to be non existent.

So whatever after .2115 that changed could perhaps have something to do with some setting that gets altered when you change the notification settings of the app inside the iOS Settings app.

Sorry if it sounds confusing, just woke up and am barely functioning as a human but just thought this might help a bit with debugging.

#30

I can’t find that report Anderoth made (Case 29616) on http://bugs.anscamobile.com/ . 

@Miracle: Could the report have failed for some reason?

#31

You can’t look up other people’s bugs.   It’s in there.  Engineering is aware of it and they are trying to track it down.

Rob

#32

Its been over a month since the last post, just hitting this thread to see if this was fixed.  I’m on build .2189 (the latest daily build as of writing this) and remote registration still doesn’t seem to be working.

#33

In my case, Build .2189 solve this issue

Thanks

#34

Its been over a month since the last post, just hitting this thread to see if this was fixed.  I’m on build .2189 (the latest daily build as of writing this) and remote registration still doesn’t seem to be working.

#35

I’m experiencing the same issue on build 2189. Any word from Corona on this as this is holding up releasing our apps.

Regards,

Trent

#36

Trent, this was solved in build 2155 on Jan 25, 2014. 

You could be hitting a different issue, or you may have some local setup issue creating problems.  Without seeing some code, its going to be hard to help. 

#37

Hi Rob,

Here is my code, when testing on my iPhone 4S (v7.1) I don’t get the remoteRegistration event at all, not even an error. This same code works on my Android Galaxy Tab 10.1.

local function onNotification( event )
    if event.type == “remote” then
        print(“we received a push notification!”)
        if event.alert == nil then
            native.showAlert(“visitor id Mobile”, “event.alert was nil!!!”, {“OK”})
        else
            local notificationString = event.alert
            local strLen = notificationString:len()
            vMobileNumber = notificationString:match("%b()")
            local numLen = vMobileNumber:len()
            local alertString = notificationString:sub(1,(strLen - numLen))
            vMobileNumber = vMobileNumber:sub(2,(numLen - 1))
            system.vibrate()
            native.showAlert(“visitor id Mobile”, alertString, {“OK”, “Call”, “SMS”}, onNotificationClick)
        end – if
    elseif ( event.type == “remoteRegistration” ) then
        if event.token ~= nil then
            DT.deviceToken = event.token
            if string.sub( system.getInfo(“model”), 1, 2 ) == “iP” then
                registerVIDDevice()
            end – if
        else
            DT.deviceToken = nil
            native.showAlert(“visitor id Mobile”, “No token returned from remote registration”, {“OK”})
        end – if
    end – if
end – function

Runtime:addEventListener( “notification”, onNotification )

EDIT: Sorry I forgot to mention that my Galaxy tab is running the app on an older version of Corona, not the 2189 build.

Regards,

Trent

#38

In my case, Build .2189 solve this issue

Thanks

#39

Hi Rob,

Any word on this? Is there something wrong with my code?

Regards,

Trent

#40

I don’t see anything immediately wrong.  Push notifications (at least on iOS) are one of the most complex things to setup and test because there are so many pieces that have to be just right.  If there is a glitch in your certificate/keys or the provisioning profile or the iTunes setup it won’t work and there is practically no feedback as to the cause. 

Since it’s working on Android, which is (while still difficult) somewhat easier to deal with than IOS in this matter, I’m less likely to think it’s your code but something in the setup along the way.

Rob