You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Jesse MacFadyen (JIRA)" <ji...@apache.org> on 2013/05/22 22:46:20 UTC
[jira] [Resolved] (CB-3282) Subsequent Notification callbacks
returns immediately with zero
[ https://issues.apache.org/jira/browse/CB-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen resolved CB-3282.
---------------------------------
Resolution: Implemented
This has been addressed already in 2.7.0
> Subsequent Notification callbacks returns immediately with zero
> ---------------------------------------------------------------
>
> Key: CB-3282
> URL: https://issues.apache.org/jira/browse/CB-3282
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP7
> Affects Versions: 2.5.0
> Environment: Windows Phone 7.8, Visual Studio 2010.
> Reporter: Ciaran Gallagher
> Assignee: Jesse MacFadyen
> Labels: notification, windows-phone, wp7
>
> The first time notification.confirm is used, it works successfully, returning the correct index after pressing the corresponding button.
> Any subsequent invocation of notification.confirm results in it immediately returning zero.
> Note this doesn't just happen when when invoking notification.confirm on the same page, it occurs any other time I invoke notification.confirm during the lifetime of the application.
> I examined the native notification.cs, and it seems apparent that this is successfully returning the correct index - at least on the native side of things, so I'm not exactly sure where it's going wrong.
> If you require additional information or you would like to see a demonstration of the failure or more information on replicating it please contact me at ciaran036home@hotmail.com.
> I'm sure Windows Phone isn't high on the priority list, but I have a university project deadline coming up it would be nice if things worked :)
> The last time the notification.confirm worked for me by the was was on PhoneGap 2.2. It appeared to stop working when I upgraded to 2.5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira