03-12-2013 01:48 PM
06-12-2013 09:19 AM - edited 06-12-2013 09:23 AM
I can confirm that this does indeed not properly work which is a bummer I need it... is there any ETA, this is something that at nearly 10.2 should have been working long ago
int week = 7; Recurrence recurrence; recurrence.setFrequency(Frequency::Daily); recurrence.setUntil(current.addDays(week));
And also any suggestions on how I can take control of my calendar once again without wiping my device? Currently i have a spinning circle in the middle which is still there even after restarting the device however
I can also confirm that it does create a recurring task as my yahoo e-mail calendar demonstrates. It's just locking us out of the blackberry calendar
*note even being locked out of the calendar application, by clicking the button i created to make that task it will do it again with no issues appearing in my e-mail only BB cal
06-13-2013 09:43 AM
It sounds like it is working, except you have perhaps run into an issue with the calender app. This isn't really a support channel for BlackBerry apps though, so I'm not sure I can help. That might be a better question for the general Z10 support forums.
You could try deleting the event in your Yahoo calender and see what happens.
06-13-2013 11:14 AM
06-13-2013 01:13 PM
Is there anything wrong with recurrence other than how it may have something to do with the the broken Calender app? It sounds like it was working otherwise, and recurrence certainly works in general. The problems may not even be related.
You could try finding the event progamatically and deleting it that way, or deleting your yahoo account and re-adding it.
12-28-2013 06:47 AM
This problems happens with inifinite recurrence too.
But it seems I found out, why this happens: If you create a Recurrence instance, the interval will be 0 (which is a pretty bad default value IMHO). If you set it to 1, the recurring events will be displayed as they should.
12-28-2013 06:49 AM
12-28-2013 10:12 AM
Thanks that never occured to me, I've now long moved past the idea I was working on this for but now if anyone else runs into the issue it'll be easier for them to figure out why it doesn't seem to act as it should