Corona, please explain this: native.setProperty( "applicationIconBadgeNumber", 0 )

Solar2D General Questions/Discussion
#1

Hi,

In our config.lua we do NOT specify notifications:

notification =

        {

            iphone =

            {

                types =

                {

                    “badge”, “sound”, “alert”

                }

            }

        }

Please note: We do NOT specify notifications in config.lua.

So far so good - we don’t get that nagging alert box from Apple asking for permissions to send Push Notifications.

However, if we put this little line somewhere in our app:

native.setProperty( “applicationIconBadgeNumber”, 0 )

the alert box asking for permission to send push notifications to the device pops up.

I don’t think that is the correct behaviour. You should respect the config settings where we have chosen not to include the notification section. I wont go into our specific use case, I just want you to fix this so that calling native.setProperty (“applicationIconBadgeNumber”) don’t automatically registers for push notifications.

When can we expect this fixed?

Thanks

#2

As far as I know there is either no bug report on this.  If you feel this is a bug, you will need to assemble a simple project that when run shows the issue at hand and file a bug report using the link at the top of the page.  Without a bug report, they can’t fix it.

Please include all needed assets, config.lua, build.settings, Xcode projects, etc. in a .zip file to include with your submission.

native.setProperty(“applicationIconBadgeNumber”, 0) should work with local notifications which I don’t think should trigger the push notification, but we will need a bug report for engineering to look into it.

Rob

#3

Well, this is a bug I think, but as always when I find bugs in your APIs I write my own Enterprise implementations - much easier than the tedious process of creating bug reports that never gets your attention. The Enterprise support we pay for is not worth the money, that’s for sure.

So, now you know there is a “bug” - or maybe your techs think it is a great feature for all I know, and you can do what you want with it. I wont file a bug report, I’ll write another extension in my plugin that fixes all Corona quirks and poor implementations found during our years of developing with Corona.

#4

I can’t say this any more direct.  Engineering has to track their work.  They do not use the forums for this.  If you want a bug fixed, you can either work around it or file a bug report. 

Engineering clears many bugs in each release.  Each are prioritized on various criteria.  But if it’s not in the bug tracker, it won’t get looked at. 

Rob

#5

This is really easy. I describe a bug, super easy to replicate using your own sample code. In my world, you - Rob Miracle - take 2 minutes to test it and confirm it, and file a bug report. That’s not my job.

#6

You simply got to stop telling your paying customers spending their time setting up test projects to prove bugs to you. You have these forums and should listen carefully when you get customer feedback. If you don’t care more about your product customers than this, well, good luck!

#7

What sample app?  LocalNotifications?  It calls that API call.  It does not generate the push notification alert.  We just tested it (including me personally) as part of the latest public release.   If you have a different sample in mind, I’ll be happy to give it a go. 

You’re the only one experiencing this. You’re the one who can reproduce this.  So you have a choice:

  1. File a bug report.

  2. Wait on others to have the same issue and hope they file a bug report.

  3. Work around the problem.

Rob

#8

Dropped you an email with a one liner main.lua (guess what the one line is) + a standard enterprise ios project.

#9

As far as I know there is either no bug report on this.  If you feel this is a bug, you will need to assemble a simple project that when run shows the issue at hand and file a bug report using the link at the top of the page.  Without a bug report, they can’t fix it.

Please include all needed assets, config.lua, build.settings, Xcode projects, etc. in a .zip file to include with your submission.

native.setProperty(“applicationIconBadgeNumber”, 0) should work with local notifications which I don’t think should trigger the push notification, but we will need a bug report for engineering to look into it.

Rob

#10

Well, this is a bug I think, but as always when I find bugs in your APIs I write my own Enterprise implementations - much easier than the tedious process of creating bug reports that never gets your attention. The Enterprise support we pay for is not worth the money, that’s for sure.

So, now you know there is a “bug” - or maybe your techs think it is a great feature for all I know, and you can do what you want with it. I wont file a bug report, I’ll write another extension in my plugin that fixes all Corona quirks and poor implementations found during our years of developing with Corona.

#11

I can’t say this any more direct.  Engineering has to track their work.  They do not use the forums for this.  If you want a bug fixed, you can either work around it or file a bug report. 

Engineering clears many bugs in each release.  Each are prioritized on various criteria.  But if it’s not in the bug tracker, it won’t get looked at. 

Rob

#12

This is really easy. I describe a bug, super easy to replicate using your own sample code. In my world, you - Rob Miracle - take 2 minutes to test it and confirm it, and file a bug report. That’s not my job.

#13

You simply got to stop telling your paying customers spending their time setting up test projects to prove bugs to you. You have these forums and should listen carefully when you get customer feedback. If you don’t care more about your product customers than this, well, good luck!

#14

What sample app?  LocalNotifications?  It calls that API call.  It does not generate the push notification alert.  We just tested it (including me personally) as part of the latest public release.   If you have a different sample in mind, I’ll be happy to give it a go. 

You’re the only one experiencing this. You’re the one who can reproduce this.  So you have a choice:

  1. File a bug report.

  2. Wait on others to have the same issue and hope they file a bug report.

  3. Work around the problem.

Rob

#15

Dropped you an email with a one liner main.lua (guess what the one line is) + a standard enterprise ios project.