About bug report Case 42982

Solar2D General Questions/Discussion
#1

I have reported a bug about iOS push notification few days ago and your support team replied me that I need to submit a test project. Since I can only provide a sample code that easily been found on Corona website, or I need to include server code and cert which is too much effort for me, I did not submit a test project. I think the description is enough to tell your team about the problem, so I replied your team with more details about the bug. But your team do not reply me whether the bug will be processed after my reply.

Should your team at least reply me about the status of the bug report?

And about the iOS push notification bug, it is difficult for me to submit a test project. This is because I need to create the provisioning profile and the push cert for your team. I need your team’s device UDID to create the provisioning profile, which is non-sense if you can do in your side. What I can submit is just a corona sample project and the json format of the push data. Then do I still need to provide such “test project” for your team?

#2

Do you have the Case # of the Bug so I can go look?

But I know how busy the team is right now and what we are focused on. The only bugs we are looking at are things that worked in 2646 and don’t in the latest daily build. These are known as “Regression bugs”. We are working towards a new public release and that’s consuming any bug fix time we have. We might be able to look at it afterwards. Then bugs are worked on base on impact. Without me being able to read the bug, I can’t guess where it would be classified.

Now regarding the need of a sample project. If you don’t provide one, you pretty much can be assured it won’t get worked on. Even if it’s sample code that can be found, it’s still not what you’re experiencing. We would have to guess at what your problem is.  We could spend hours or days trying to duplicate your bug. But if you provide us a sample that demonstrates the problem that we can simply apply our ID’s and certificates to and build, and say “Oh, that’s the problem”, then engineering can find the problem and hopefully fix it.

Rob

#3

Thanks for your reply and sorry for the impolite asking in the post, since I have many bad experience from your support team.

The case number is #42982.

I think you can close the case since I will test with the updated daily build and submit a new bug case to your team.

Thanks again.

#4

There are no fixes in the recent daily builds for this.

Any way after reading the exchange in the bug report, I can with certainty say we won’t be able to reproduce your issue and here’s why. We don’t know what you’re using to generate the push notification. Are you using Urban Airship? Pushwoosh? One Signal? Your own server?  This is the first fail point. How do you know the bug isn’t with the push sender?  You have provided no information in the bug report about how you are generating the message.

As far as the sample app, if our sample demonstrates the issue, just zip it up and submit the bug. But in addition to the sample app, part of the instructions is to provide step by step instructions on how to duplicate the issues. This of course includes how you are sending the push? What have you done to see that the payload is incorrect.

When you can, update the bug report with the zip file and instructions on how to make it fail. We can’t look at this until we have this information.

Rob

Rob

#5

Yes, you are right.

I forget to tell your team that I use my own server to send push to Apple server directly. I will include this info to the next submit.

And I will also try to include the php code to your team again.

#6

Do you have the Case # of the Bug so I can go look?

But I know how busy the team is right now and what we are focused on. The only bugs we are looking at are things that worked in 2646 and don’t in the latest daily build. These are known as “Regression bugs”. We are working towards a new public release and that’s consuming any bug fix time we have. We might be able to look at it afterwards. Then bugs are worked on base on impact. Without me being able to read the bug, I can’t guess where it would be classified.

Now regarding the need of a sample project. If you don’t provide one, you pretty much can be assured it won’t get worked on. Even if it’s sample code that can be found, it’s still not what you’re experiencing. We would have to guess at what your problem is.  We could spend hours or days trying to duplicate your bug. But if you provide us a sample that demonstrates the problem that we can simply apply our ID’s and certificates to and build, and say “Oh, that’s the problem”, then engineering can find the problem and hopefully fix it.

Rob

#7

Thanks for your reply and sorry for the impolite asking in the post, since I have many bad experience from your support team.

The case number is #42982.

I think you can close the case since I will test with the updated daily build and submit a new bug case to your team.

Thanks again.

#8

There are no fixes in the recent daily builds for this.

Any way after reading the exchange in the bug report, I can with certainty say we won’t be able to reproduce your issue and here’s why. We don’t know what you’re using to generate the push notification. Are you using Urban Airship? Pushwoosh? One Signal? Your own server?  This is the first fail point. How do you know the bug isn’t with the push sender?  You have provided no information in the bug report about how you are generating the message.

As far as the sample app, if our sample demonstrates the issue, just zip it up and submit the bug. But in addition to the sample app, part of the instructions is to provide step by step instructions on how to duplicate the issues. This of course includes how you are sending the push? What have you done to see that the payload is incorrect.

When you can, update the bug report with the zip file and instructions on how to make it fail. We can’t look at this until we have this information.

Rob

Rob

#9

Yes, you are right.

I forget to tell your team that I use my own server to send push to Apple server directly. I will include this info to the next submit.

And I will also try to include the php code to your team again.